Remote MCP · Endpoint

Overpass MCP server

No. Overpass answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/overpass/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/overpass
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
OpenStreetMap Overpass MCP — programmatic queries against the OSM database
Listing
From the official MCP registry (active).
Recent checks of Overpass
CheckedResultHandshake
1 hour agoHandshake completed69 ms
2 days agoHandshake completed73 ms
4 days agoHandshake completed55 ms
5 days agoHandshake completed64 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed55 ms
9 days agoHandshake completed52 ms
12 days agoHandshake completed48 ms
13 days agoHandshake completed42 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed41 ms
18 days agoHandshake completed41 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed37 ms
21 days agoHandshake completed50 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed57 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 Overpass and makes no claim about it beyond what these checks measured.