DaedalMap Administrative Boundaries (loc_id to polygon)
REMOTE · APP.DAEDALMAP.COM
Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons.
Available components
Last scanned (22 hours ago)
Scores higher than 79% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 −4
- Schema quality: 132 → 229 ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 88% → 79% ▼ functional
- “get_geography” added an optional parameter “include_geometry” cosmetic
- “get_geography” added an optional parameter “page” cosmetic
- “get_geography” added an optional parameter “page_size” cosmetic
- Tool “get_geography” changed its title: Inspect One Geography Family or Scope → Discover or Read Geography Coverage cosmetic
- 26 Oct 26 +45
- Stability: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 25 Oct 26 −45
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Oct 26 +6
No change was recorded against any check on this day. Stability & Change Management went from 32 to 75.
- 17 Oct 26 −2
- A breaking change shipped without a version bump: still 1.3.2 ▼ security
- Tool “get_geometry” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_geographies” rewrote its description, which is the text the model reads security
- Tool “get_catalog” rewrote its description, which is the text the model reads security
- Tool “get_loc_id_info” rewrote its description, which is the text the model reads security
- Tool “get_pack” rewrote its description, which is the text the model reads security
- Tool coverage: 98% → 88% ▼ functional
- “get_catalog” made “catalog” required, so existing callers break ▼ functional
- Schema quality: 180 → 130 ▲ functional
- New tool “get_geography” functional
- New tool “get_shape” functional
- “get_catalog” reworded the description of “catalog” cosmetic
- “get_loc_id_info” reworded the description of “loc_ids” cosmetic
- “get_catalog” dropped the optional parameter “country_scope” cosmetic
- “get_catalog” dropped the optional parameter “detail” cosmetic
- “get_catalog” dropped the optional parameter “loc_id” cosmetic
- “get_catalog” dropped the optional parameter “time_range” cosmetic
- “get_loc_id_info” dropped the optional parameter “as_of” cosmetic
- “get_loc_id_info” dropped the optional parameter “include_hierarchy” cosmetic
- “get_loc_id_info” dropped the optional parameter “include_references” cosmetic
- “get_loc_id_info” dropped the optional parameter “iso3” cosmetic
- “get_loc_id_info” dropped the optional parameter “limit_per_system” cosmetic
- “get_loc_id_info” dropped the optional parameter “min_share” cosmetic
- “get_loc_id_info” dropped the optional parameter “systems” cosmetic
- “get_loc_id_info” dropped the optional parameter “target_admin_level” cosmetic
- “get_pack” dropped the optional parameter “catalog” cosmetic
- “get_pack” dropped the optional parameter “country_scope” cosmetic
- “get_pack” dropped the optional parameter “detail” cosmetic
- “get_pack” dropped the optional parameter “release_unit” cosmetic
- Tool “get_catalog” changed its title: List Available Packs and Geometry Families → List Published Packs or Geographies cosmetic
- Tool “get_loc_id_info” changed its title: Inspect Known loc_id Identities → Inspect Direct loc_id Connections cosmetic
- Tool “get_pack” changed its title: Inspect One Selected Pack or Geometry Family → Inspect One Data Pack cosmetic
- 14 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://app.daedalmap.com/mcp/boundaries
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.daedalmap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| daedalmap.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.daedalmap.com/mcp/boundaries | Unreachable | ||
| http (plaintext) | http://app.daedalmap.com/mcp/boundaries | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_geographies Compare Geographic Identities ~252
Compare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove containment; a typed graph edge can prove only the relation it declares. An explicit negative edge returns no_overlap; a missing edge returns unknown. This tool never reads polygons or computes shape intersections. Use an external identifier bridge before this call when the input is not a loc_id. No payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | ISO date or year applied to both identities. |
| batch_id | string | – | Optional caller-supplied batch id for tracing. |
| include_successors | boolean | – | Include direct successors and present-day descendants for maintained historical identities. Default true. |
| items | array | – | Bounded geography pairs to compare in one call. |
| left_as_of | string | – | Optional ISO date or year for the left identity; overrides as_of. |
| left_loc_id | string | – | First DaedalMap loc_id. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| right_as_of | string | – | Optional ISO date or year for the right identity; overrides as_of. |
| right_loc_id | string | – | Second DaedalMap loc_id. |
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string|null | – | – |
| clarification | object | – | – |
| compared_count | integer | – | – |
| error | object | – | – |
| failed_count | integer | – | – |
| geometry_loaded | boolean | – | – |
| graph_evidence | array | – | – |
| guidance | object | – | – |
| item_count | integer | – | – |
| meter_receipt | object | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| reason | string | – | – |
| relationship_basis | string | – | – |
| request_id | string|null | – | – |
| results | array | – | – |
| settlement_receipt | object | – | – |
| spatial_relation | string|object|null | – | – |
| temporal_relation | string|object|null | – | – |
| warnings | array | – | – |
No examples provided.
get_catalog List Published Packs or Geographies ~125
Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | Required directory selector. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | – | – |
| catalog_version | string | – | – |
| clarification | object | – | – |
| detail | string | – | – |
| download_url | string | – | – |
| error | object | – | – |
| excluded_count | integer | – | – |
| families | array | – | – |
| generated_at | string|null | – | – |
| guidance | object | – | – |
| next_step | object | – | – |
| pack_count | integer | – | – |
| packs | array | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| resolved_query | object | – | – |
| result_status | string | – | – |
| scopes | array | – | – |
| tool_families | array | – | – |
| uncertain_count | integer | – | – |
| uncertain_packs | array | – | – |
| warnings | array | – | – |
No examples provided.
get_geography Discover or Read Geography Coverage ~106
Inspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata only. Optional year selects the latest admitted edition no later than that year when the selected catalog has an edition index; an unavailable index is reported explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| family_id | string | – | – |
| include_geometry | boolean | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| scope_id | string | – | – |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| admin_spine | object | – | – |
| catalog | string | – | – |
| clarification | object | – | – |
| coverage | array | – | – |
| error | object | – | – |
| family_id | string|null | – | – |
| guidance | object | – | – |
| next_step | object | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| requested_year | integer|null | – | – |
| scope_id | string|null | – | – |
| warnings | array | – | – |
No examples provided.
get_loc_id_info Inspect Direct loc_id Connections ~161
Look up one known loc_id or a small batch in the selected reference graph. Return its identity and directly recorded loc_id connections, with family, direction, and relationship evidence. Each ID returns at most 50 connections and an explicit has_more flag. This tool does not expand descendants, infer containment, read shapes, search catalogs, or consult external adapters. No payment required.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | – | Optional caller-supplied batch id for tracing. |
| loc_id | string | – | DaedalMap loc_id, e.g. 'USA-CA'. |
| loc_ids | array | – | Up to 10 known loc_ids, including a resolve_point stack. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| Name | Type | Req | Description |
|---|---|---|---|
| admin_level | string|integer|null | – | – |
| batch_id | string|null | – | – |
| clarification | object | – | – |
| connection_count | integer | – | – |
| connection_limit | integer | – | – |
| connections | array | – | – |
| error | object | – | – |
| family | string|null | – | – |
| found_count | integer | – | – |
| guidance | object | – | – |
| has_more | boolean | – | – |
| iso3 | string|null | – | – |
| loc_id | string | – | – |
| loc_id_count | integer | – | – |
| meter_receipt | object | – | – |
| missing_count | integer | – | – |
| name | string|null | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| requested_loc_id | string | – | – |
| results | array | – | – |
| settlement_receipt | object | – | – |
| warnings | array | – | – |
No examples provided.
get_pack Inspect One Data Pack ~52
Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | – | – |
| clarification | object | – | – |
| detail | string | – | – |
| download_call | object | – | – |
| download_url | string | – | – |
| error | object | – | – |
| full_call | object | – | – |
| guidance | object | – | – |
| material_policy | object | – | – |
| next_step | object | – | – |
| pack_id | string | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| sources | array | – | – |
| warnings | array | – | – |
No examples provided.
get_shape Retrieve Shapes for Known loc_ids ~203
Shape lookup for exact existing loc_ids only. The default returns shape availability, centroid, and bounding box; include_polygon=true adds GeoJSON coordinates. Obtain any descendant IDs before this call. Historical geometry is returned first and successors are never substituted automatically. Year selection is not yet supported.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | – | Optional caller-supplied batch id for tracing. |
| include_polygon | boolean | – | When true, include the full GeoJSON geometry. Default false. |
| loc_id | string | – | DaedalMap loc_id, such as USA-CA-037, USA-Z-00601, USA-NWSFZ-AKZ317, EEZ-USA, or IHO1953-240001002. |
| loc_ids | array | – | Exact DaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | integer | – | – |
| batch_id | string|null | – | – |
| clarification | object | – | – |
| error | object | – | – |
| guidance | object | – | – |
| include_polygon | boolean | – | – |
| items | array | – | – |
| meter_receipt | object | – | – |
| missing | integer | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| requested | integer | – | – |
| selection | string | – | – |
| settlement_receipt | object | – | – |
| warnings | array | – | – |
No examples provided.
get_tool_help Get Tool Help ~84
Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | Optional question used only with a topic overview. |
| tool_name | string | – | Exact tool name from tools/list. Do not combine with topic. |
| topic | string | – | Workflow overview. Do not combine with tool_name. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | – | – |
| clarification | object | – | – |
| error | object | – | – |
| examples | array | – | – |
| guidance | object | – | – |
| important_output_fields | array | – | – |
| input_schema | object | – | – |
| next_step | object | – | – |
| ok | boolean | – | – |
| provenance | object | – | – |
| purpose | string | – | – |
| reason | string | – | – |
| recommended_next_calls | array | – | – |
| request_id | string|null | – | – |
| title | string|null | – | – |
| tool_name | string | – | – |
| warnings | array | – | – |
No examples provided.
How do I install the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server?
DaedalMap Administrative Boundaries (loc_id to polygon) is a hosted endpoint at https://app.daedalmap.com/mcp/boundaries, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.daedalmap.com
claude mcp add --transport http com-daedalmap-boundaries 'https://app.daedalmap.com/mcp/boundaries'
What is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server?
DaedalMap Administrative Boundaries (loc_id to polygon) is an MCP server listed in the public MCP registry as com.daedalmap/boundaries. Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/boundaries).
Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server safe to use?
DaedalMap Administrative Boundaries (loc_id to polygon) scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server expose?
DaedalMap Administrative Boundaries (loc_id to polygon) exposes 7 tools: get_tool_help, get_catalog, get_pack, get_geography, get_loc_id_info, and 2 more. Their descriptions and schemas cost roughly 983 tokens of context every time the server is loaded.
Does the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server require authentication?
Its publisher declares no required credentials for DaedalMap Administrative Boundaries (loc_id to polygon). We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server still maintained?
DaedalMap Administrative Boundaries (loc_id to polygon) is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.