Remote MCP · Endpoint
CityWalk Plan MCP server
No. CityWalk Plan answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://citywalkplan.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.citywalkplan/planner
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 306 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Free city-walk planner: day-by-day self-guided walking itineraries for 50+ cities. No sign-up.
- Website
- https://citywalkplan.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 306 ms |
| 19 hours ago | Handshake completed | 128 ms |
| 2 days ago | Handshake completed | 121 ms |
| 3 days ago | Handshake completed | 113 ms |
| 4 days ago | Handshake completed | 190 ms |
| 5 days ago | Handshake completed | 129 ms |
| 6 days ago | Handshake completed | 148 ms |
| 8 days ago | Handshake completed | 639 ms |
| 10 days ago | Handshake completed | 122 ms |
| 13 days ago | Handshake completed | 463 ms |
| 15 days ago | Handshake completed | 185 ms |
| 17 days ago | Handshake completed | 99 ms |
| 19 days ago | Handshake completed | 114 ms |
| 21 days ago | Handshake completed | 102 ms |
| 23 days ago | Handshake completed | 559 ms |
| 25 days ago | Handshake completed | 485 ms |
| 27 days ago | Handshake completed | 107 ms |
| 28 days ago | Handshake completed | 555 ms |
| 29 days ago | Handshake completed | 915 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 CityWalk Plan and makes no claim about it beyond what these checks measured.