Remote MCP · Endpoint

GeoSpark MCP server

No. GeoSpark answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://geospark.terrascout.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.Maz2580/geospark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
806 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verifiable geospatial tools: distances, topology, isochrones, Overture Maps, with sources.
Listing
From the official MCP registry (active).
Recent checks of GeoSpark
CheckedResultHandshake
20 minutes agoHandshake completed806 ms
3 days agoHandshake completed754 ms
14 days agoHandshake completed776 ms
14 days agoHandshake completed886 ms
15 days agoHandshake completed825 ms
16 days agoHandshake completed1.01 s
18 days agoHandshake completed739 ms
18 days agoHandshake completed850 ms
19 days agoHandshake completed801 ms
21 days agoHandshake completed767 ms
23 days agoHandshake completed733 ms
25 days agoHandshake completed842 ms
28 days agoHandshake completed743 ms

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

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 GeoSpark and makes no claim about it beyond what these checks measured.