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/api/mcp
The last check completed an MCP handshake.
- Registry name
- live.cityalert/cityalert
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 184 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Free live public-safety incident map: global crime, fire, disaster, weather and news feeds
- Website
- https://cityalert.live/
- Repository
- https://github.com/homezloco/cityalert
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 184 ms |
| 1 day ago | Handshake completed | 149 ms |
| 2 days ago | Handshake completed | 179 ms |
| 3 days ago | Failed - the request timed out | — |
| 4 days ago | Handshake completed | 767 ms |
| 5 days ago | Handshake completed | 570 ms |
| 6 days ago | Handshake completed | 640 ms |
| 8 days ago | Handshake completed | 6.14 s |
| 11 days ago | Handshake completed | 1.39 s |
| 13 days ago | Handshake completed | 619 ms |
| 16 days ago | Handshake completed | 228 ms |
| 18 days ago | Handshake completed | 234 ms |
| 20 days ago | Handshake completed | 198 ms |
| 22 days ago | Handshake completed | 168 ms |
| 24 days ago | Handshake completed | 155 ms |
| 26 days ago | Handshake completed | 174 ms |
| 27 days ago | Handshake completed | 613 ms |
| 29 days ago | Handshake completed | 283 ms |
| 30 days ago | Handshake completed | 194 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 29.
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.