Remote MCP · Endpoint

CitySignal AI MCP server

No. CitySignal AI answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://citysignalai.com/mcp

The last check completed an MCP handshake.

Registry name
com.citysignalai/citysignal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
98 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live road, transit, weather, power and water signals for US cities, plus your own spots and routes.
Listing
From the official MCP registry (active).
Recent checks of CitySignal AI
CheckedResultHandshake
35 minutes agoHandshake completed98 ms
9 days agoHandshake completed146 ms
10 days agoHandshake completed127 ms
11 days agoHandshake completed81 ms
12 days agoHandshake completed66 ms
14 days agoHandshake completed102 ms
14 days agoHandshake completed72 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed135 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed71 ms
24 days agoHandshake completed145 ms
26 days agoHandshake completed167 ms

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

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 CitySignal AI and makes no claim about it beyond what these checks measured.