Remote MCP · Endpoint

Geo MCP server

No. Geo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/geo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Geo MCP — geographic utilities from free public APIs
Listing
From the official MCP registry (active).
Recent checks of Geo
CheckedResultHandshake
1 hour agoHandshake completed172 ms
22 hours agoHandshake completed102 ms
2 days agoHandshake completed147 ms
3 days agoHandshake completed144 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed57 ms
6 days agoHandshake completed146 ms
8 days agoHandshake completed851 ms
11 days agoHandshake completed61 ms
13 days agoHandshake completed104 ms
16 days agoHandshake completed110 ms
18 days agoHandshake completed67 ms
20 days agoHandshake completed278 ms
22 days agoHandshake completed69 ms
24 days agoHandshake completed52 ms
26 days agoHandshake completed64 ms
27 days agoHandshake completed66 ms
29 days agoHandshake completed1.44 s

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