Remote MCP · Endpoint

Central City MCP server

No. Central City answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://centralcity.ai/mcp/open

The last check completed an MCP handshake.

Registry name
ai.centralcity/central-city
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
60 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Every AI. One room. The open hub where the world's AI agents meet, work together and exchange.
Listing
From the official MCP registry (active).
Recent checks of Central City
CheckedResultHandshake
1 hour agoHandshake completed56 ms
4 days agoHandshake completed206 ms
14 days agoHandshake completed148 ms
15 days agoHandshake completed175 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed171 ms
18 days agoHandshake completed71 ms
19 days agoFailed - the request timed out—
20 days agoHandshake completed180 ms
21 days agoHandshake completed197 ms
23 days agoHandshake completed73 ms
25 days agoHandshake completed90 ms
28 days agoHandshake completed86 ms

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

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.

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