Remote MCP · Endpoint
Mapsource OpenStreetMap & Geospatial APIs MCP server
No. Mapsource OpenStreetMap & Geospatial APIs answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://mapsource.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.robit-man/mapsource
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 410 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- OpenStreetMap queries, maps/styles, search, routing, terrain, analysis, pipelines, and rendering.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 410 ms |
| 2 days ago | Handshake completed | 308 ms |
| 4 days ago | Handshake completed | 331 ms |
| 5 days ago | Handshake completed | 313 ms |
| 7 days ago | Handshake completed | 322 ms |
| 8 days ago | Handshake completed | 300 ms |
| 9 days ago | Handshake completed | 475 ms |
| 12 days ago | Handshake completed | 346 ms |
| 13 days ago | Handshake completed | 314 ms |
| 15 days ago | Handshake completed | 356 ms |
| 16 days ago | Handshake completed | 268 ms |
| 17 days ago | Handshake completed | 267 ms |
| 18 days ago | Handshake completed | 255 ms |
| 19 days ago | Handshake completed | 243 ms |
| 20 days ago | Handshake completed | 243 ms |
| 21 days ago | Handshake completed | 254 ms |
| 22 days ago | Handshake completed | 278 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Mapsource OpenStreetMap & Geospatial APIs and makes no claim about it beyond what these checks measured.