Remote MCP · Endpoint

DaedalMap Administrative Boundaries (loc_id to polygon) MCP server

No. DaedalMap Administrative Boundaries (loc_id to polygon) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.daedalmap.com/mcp/boundaries

The last check completed an MCP handshake.

Registry name
com.daedalmap/boundaries
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
21 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons.
Website
https://www.daedalmap.com/
Repository
https://github.com/xyver/daedal-map
Listing
From the official MCP registry (active).
Recent checks of DaedalMap Administrative Boundaries (loc_id to polygon)
CheckedResultHandshake
1 hour agoHandshake completed21 ms
2 days agoHandshake completed25 ms
4 days agoHandshake completed31 ms
5 days agoHandshake completed28 ms
7 days agoHandshake completed39 ms
8 days agoHandshake completed20 ms
9 days agoHandshake completed24 ms
12 days agoHandshake completed25 ms
13 days agoHandshake completed19 ms
15 days agoHandshake completed19 ms
16 days agoHandshake completed21 ms
17 days agoHandshake completed20 ms
18 days agoHandshake completed20 ms
19 days agoHandshake completed24 ms
20 days agoHandshake completed26 ms
21 days agoHandshake completed43 ms
22 days agoHandshake completed5.16 s

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

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 Administrative Boundaries (loc_id to polygon) and makes no claim about it beyond what these checks measured.