Remote MCP · Endpoint

Citiwise MCP server

No. Citiwise answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://citiwise.in/mcp

The last check completed an MCP handshake.

Registry name
io.github.tejasdgurav/citiwise
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
455 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UDCPR 2020 (Maharashtra) feasibility for a plot, with the clause behind every number.
Website
https://citiwise.in/
Listing
From the official MCP registry (active).
Recent checks of Citiwise
CheckedResultHandshake
2 hours agoHandshake completed455 ms
1 day agoHandshake completed261 ms
2 days agoHandshake completed1.10 s
2 days agoHandshake completed238 ms
4 days agoHandshake completed277 ms
7 days agoHandshake completed231 ms
9 days agoHandshake completed267 ms
12 days agoHandshake completed1.27 s
14 days agoHandshake completed281 ms
16 days agoHandshake completed1.07 s
18 days agoHandshake completed248 ms
20 days agoHandshake completed243 ms
22 days agoHandshake completed235 ms
24 days agoHandshake completed297 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Citiwise and makes no claim about it beyond what these checks measured.