Remote MCP · Endpoint

DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server

No. DaedalMap Reverse Geocoding (coordinates to loc_id) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.daedalmap.com/mcp/reverse-geocoding

The last check completed an MCP handshake.

Registry name
com.daedalmap/reverse-geocoding
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
30 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Convert WGS84 coordinates to the latest available administrative loc_id chain.
Website
https://www.daedalmap.com/
Repository
https://github.com/xyver/daedal-map
Listing
From the official MCP registry (active).
Recent checks of DaedalMap Reverse Geocoding (coordinates to loc_id)
CheckedResultHandshake
1 hour agoHandshake completed30 ms
1 day agoHandshake completed21 ms
2 days agoHandshake completed41 ms
3 days agoHandshake completed51 ms
4 days agoHandshake completed29 ms
5 days agoHandshake completed28 ms
6 days agoHandshake completed25 ms
9 days agoHandshake completed30 ms
11 days agoHandshake completed25 ms
14 days agoHandshake completed32 ms
16 days agoHandshake completed23 ms
18 days agoHandshake completed25 ms
20 days agoHandshake completed26 ms
22 days agoHandshake completed20 ms
24 days agoHandshake completed18 ms
26 days agoHandshake completed21 ms
28 days agoHandshake completed46 ms
29 days agoHandshake completed13 ms

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

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with DaedalMap Reverse Geocoding (coordinates to loc_id) and makes no claim about it beyond what these checks measured.