# DaedalMap Administrative Boundaries (loc_id to polygon) (remote · app.daedalmap.com)

Inspect loc_id boundaries, retrieve bounded shapes, and compare places and coverage.

- Trust score: 78/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `app.daedalmap.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2.md), [page](https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2)

## Channel facts

- Endpoint: `https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1928 tokens (~148/item across 13 items; 7 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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?registry=mcpregistry, 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.

### Claude

```bash
claude mcp add --transport http com-daedalmap-boundaries 'https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-daedalmap-boundaries": {
      "url": "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-daedalmap-boundaries": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-daedalmap-boundaries]
url = "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-daedalmap-boundaries": {
      "type": "remote",
      "url": "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-daedalmap-boundaries --url 'https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-daedalmap-boundaries:
    url: "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-daedalmap-boundaries": {
      "Transport": "http",
      "Url": "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-daedalmap-boundaries -t streamable-http -u 'https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry'
```

### Other

```json
{
  "mcpServers": {
    "com-daedalmap-boundaries": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 77, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28

### 2026-11-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 73, 0)

- [security] Tool “get_pack” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 130 → 144
- [cosmetic] “get_pack” added an optional parameter “source_id”
- [cosmetic] “get_pack” added an optional parameter “metrics”
- [cosmetic] “get_pack” added an optional parameter “search”

### 2026-11-13 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 73)

First indexed and scored.

## MCP tools (7)

### `get_tool_help` (~84 tokens)

Get Tool Help

Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.

Input parameters:

- `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.

Output parameters:

- `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)

### `get_catalog` (~125 tokens)

List Published Packs or Geographies

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.

Input parameters:

- `catalog` (string, required): Required directory selector.

Output parameters:

- `catalog` (string)
- `catalog_version` (string)
- `clarification` (object)
- `detail` (string)
- `download_url` (string)
- `error` (object)
- `excluded_count` (integer)
- `families` (array)
- `free_get_data_policy_note` (string)
- `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)

### `get_pack` (~241 tokens)

Inspect One Data Pack

Narrow one data pack before get_data. With only pack_id, lists the pack's sources and their coverage. Add source_id to list that source's metrics (name, unit, years, aggregation) and its filterable and sortable fields; search to match metrics across the pack by name, description, or keyword; or metrics for full detail on up to 10 exact ids.

Input parameters:

- `metrics` (array): Optional. Up to 10 exact metric ids from this pack. Returns full stored detail for each, including description, coverage by era, value statistics, and every source that holds it.
- `pack_id` (string, required): Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
- `search` (string): Optional. Terms matched against metric ids, names, descriptions, and keywords across this pack's sources; every term must match. Returns up to 25 compact metric lines.
- `source_id` (string): Optional. One source_id from this pack's sources list. Returns every metric in that source with name, unit, years, and aggregation, plus the source's filterable fields, sortable fields, and time fiel…

Output parameters:

- `catalog` (string)
- `clarification` (object)
- `detail` (string)
- `download_call` (object)
- `download_url` (string)
- `error` (object)
- `full_call` (object)
- `guidance` (object)
- `match_count` (integer)
- `material_policy` (object)
- `metrics` (array)
- `next_step` (object)
- `pack_id` (string)
- `provenance` (object)
- `query_contract` (object)
- `reason` (string)
- `request_id` (string|null)
- `source` (object)
- `sources` (array)
- `truncated` (boolean)
- `unknown_metrics` (array)
- `warnings` (array)

### `get_geography` (~83 tokens)

Inspect One Geography Family or Scope

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.

Input parameters:

- `family_id` (string)
- `scope_id` (string)
- `year` (integer)

Output parameters:

- `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)

### `get_loc_id_info` (~161 tokens)

Inspect Direct loc_id Connections

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.

Input parameters:

- `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.

Output parameters:

- `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)

### `compare_geographies` (~252 tokens)

Compare Geographic Identities

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.

Input parameters:

- `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.

Output parameters:

- `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)

### `get_shape` (~203 tokens)

Retrieve Shapes for Known loc_ids

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.

Input parameters:

- `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.

Output parameters:

- `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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73
- 2026-11-12: 73

## Common questions

### 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. Inspect loc_id boundaries, retrieve bounded shapes, and compare places and coverage. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry).

### Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server safe to use?

DaedalMap Administrative Boundaries (loc_id to polygon) scores 78 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 1,149 tokens of context every time the server is loaded.

### Does the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server require authentication?

No. We connected to DaedalMap Administrative Boundaries (loc_id to polygon) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server still maintained?

DaedalMap Administrative Boundaries (loc_id to polygon) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server?

VerifyMCP ran 13 checks on DaedalMap Administrative Boundaries (loc_id to polygon), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry
- Repository: https://github.com/xyver/daedal-map
- Website: https://www.daedalmap.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2.json
- HTML version of this page: https://verifymcp.io/servers/com-daedalmap-boundaries/mcp-boundaries-2
