Remote MCP · Endpoint

geonames-mcp-server MCP server

No. geonames-mcp-server answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://geonames.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/geonames-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search GeoNames places, walk admin hierarchies, reverse geocode, get postal codes and country info.
Listing
From the official MCP registry (active).
Recent checks of geonames-mcp-server
CheckedResultHandshake
43 minutes agoHandshake completed273 ms
3 days agoHandshake completed265 ms
13 days agoHandshake completed259 ms
13 days agoHandshake completed254 ms
15 days agoHandshake completed363 ms
15 days agoHandshake completed271 ms
17 days agoHandshake completed144 ms
18 days agoHandshake completed315 ms
18 days agoHandshake completed262 ms
20 days agoHandshake completed303 ms
22 days agoHandshake completed264 ms
25 days agoHandshake completed276 ms
27 days agoHandshake completed282 ms

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