Remote MCP · Endpoint

geonames-mcp-server MCP server

No. geonames-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
264 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 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
1 hour agoHandshake completed264 ms
2 days agoHandshake completed276 ms
5 days agoHandshake completed282 ms
7 days agoHandshake completed269 ms
9 days agoHandshake completed173 ms
11 days agoHandshake completed178 ms
13 days agoHandshake completed105 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed91 ms
18 days agoHandshake completed211 ms
20 days agoHandshake completed644 ms
21 days agoHandshake completed101 ms
23 days agoHandshake completed111 ms
25 days agoHandshake completed137 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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.

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.