Remote MCP · Endpoint

Mapsource OpenStreetMap & Geospatial APIs MCP server

No. Mapsource OpenStreetMap & Geospatial APIs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
259 ms
Tools exposed
13 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
OpenStreetMap queries, maps/styles, search, routing, terrain, analysis, pipelines, and rendering.
Website
https://mapsource.io/docs/agents
Listing
From the official MCP registry (active).
Recent checks of Mapsource OpenStreetMap & Geospatial APIs
CheckedResultHandshake
1 hour agoHandshake completed259 ms
2 days agoHandshake completed309 ms
4 days agoFailed - the server returned an HTTP error—
6 days agoHandshake completed264 ms
8 days agoHandshake completed303 ms
10 days agoHandshake completed295 ms
12 days agoHandshake completed373 ms
14 days agoHandshake completed253 ms
15 days agoHandshake completed276 ms
16 days agoHandshake completed530 ms
17 days agoHandshake completed419 ms
20 days agoHandshake completed276 ms
22 days agoHandshake completed279 ms
23 days agoHandshake completed282 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.