Remote MCP · Endpoint

Mapsource OpenStreetMap & Geospatial APIs MCP server

No. Mapsource OpenStreetMap & Geospatial APIs answered an MCP handshake 2 hours ago.

UpLast checked 2 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
399 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
OpenStreetMap queries, maps/styles, search, routing, terrain, analysis, pipelines, and rendering.
Listing
From the official MCP registry (active).
Recent checks of Mapsource OpenStreetMap & Geospatial APIs
CheckedResultHandshake
2 hours agoHandshake completed399 ms
1 day agoHandshake completed797 ms
3 days agoHandshake completed2.21 s
3 days agoHandshake completed1.67 s
4 days agoHandshake completed351 ms
5 days agoHandshake completed395 ms
7 days agoHandshake completed1.03 s
10 days agoHandshake completed298 ms
12 days agoHandshake completed339 ms
15 days agoHandshake completed353 ms
17 days agoHandshake completed383 ms
19 days agoHandshake completed600 ms
21 days agoHandshake completed410 ms
23 days agoHandshake completed308 ms
25 days agoHandshake completed331 ms
26 days agoHandshake completed313 ms
28 days agoHandshake completed322 ms
29 days agoHandshake completed300 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 Mapsource OpenStreetMap & Geospatial APIs and makes no claim about it beyond what these checks measured.