Remote MCP · Endpoint

CityAlert MCP server

No. CityAlert answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cityalert.live/.well-known/mcp

The last check completed an MCP handshake.

Registry name
live.cityalert/cityalert
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
206 ms
Tools exposed
8 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Free live public-safety incident map: global crime, fire, disaster, weather and news feeds
Listing
From the official MCP registry (active).
Recent checks of CityAlert
CheckedResultHandshake
1 hour agoHandshake completed206 ms
1 day agoHandshake completed167 ms
2 days agoHandshake completed439 ms
2 days agoHandshake completed326 ms
4 days agoHandshake completed347 ms
7 days agoHandshake completed181 ms
9 days agoHandshake completed638 ms
12 days agoHandshake completed237 ms
14 days agoHandshake completed220 ms
16 days agoHandshake completed223 ms
18 days agoHandshake completed502 ms
20 days agoHandshake completed399 ms
22 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the request timed out—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 12 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.

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