Remote MCP · Endpoint

Mapsource OpenStreetMap & Geospatial APIs MCP server

No. Mapsource OpenStreetMap & Geospatial APIs answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://api.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
393 ms
Tools exposed
13 tools
Uptime, last 30 days
93.3% from 15 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
6 days agoHandshake completed393 ms
7 days agoHandshake completed2.47 s
7 days agoHandshake completed365 ms
9 days agoHandshake completed2.05 s
10 days agoHandshake completed329 ms
11 days agoHandshake completed3.44 s
12 days agoHandshake completed335 ms
13 days agoHandshake completed362 ms
15 days agoHandshake completed912 ms
17 days agoHandshake completed316 ms
20 days agoHandshake completed259 ms
22 days agoHandshake completed309 ms
25 days agoFailed - the server returned an HTTP error—
26 days agoHandshake completed264 ms
29 days agoHandshake completed303 ms
31 days agoHandshake completed295 ms
32 days agoHandshake completed373 ms
34 days agoHandshake completed253 ms
35 days agoHandshake completed276 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 24.

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.