# DaedalMap Reverse Geocoding (coordinates to loc_id) (remote · app.daedalmap.com)

Resolve WGS84 points and map boxes to available administrative loc_id hierarchies.

- 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-reverse-geocoding/mcp-reverse-geocoding-2.md), [page](https://verifymcp.io/servers/com-daedalmap-reverse-geocoding/mcp-reverse-geocoding-2)

## Channel facts

- Endpoint: `https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.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**: 76/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 2078 tokens (~159/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 Reverse Geocoding (coordinates to loc_id) MCP server?

DaedalMap Reverse Geocoding (coordinates to loc_id) is a hosted endpoint at https://app.daedalmap.com/mcp/reverse-geocoding?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-reverse-geocoding 'https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-daedalmap-reverse-geocoding": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/reverse-geocoding?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-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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
- [security] Tool “resolve_point” rewrote its description, which is the text the model reads
- [security] Tool “resolve_deep_point” rewrote its description, which is the text the model reads
- [security] Tool “resolve_deep_bbox” rewrote its description, which is the text the model reads
- [security] Tool “resolve_bbox” rewrote its description, which is the text the model reads
- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28
- [cosmetic] “resolve_bbox” added an optional parameter “scope_id”
- [cosmetic] “resolve_point” reworded the description of “family”
- [cosmetic] “resolve_deep_point” reworded the description of “shallow_loc_id”
- [cosmetic] “resolve_deep_bbox” reworded the description of “shallow_loc_id”
- [cosmetic] “resolve_point” reworded the description of “scope_id”

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

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

### 2026-11-17 (score 74, +51)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Authorization: unverified → partial
- [security improvement] Transport: fail → pass
- [security improvement] HSTS header: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.17
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100

### 2026-11-16 (score 23, −15)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified

### 2026-11-15 (score 38, −35)

- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-14 (score 73, +1)

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

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

- [functional improvement] Stability: unverified → 0.03

## 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_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)

### `resolve_point` (~348 tokens)

Resolve Point(s) in One Scope

Resolve WGS84 coordinates in one scope and family. Omitted scope_id and family select GLOBAL GeoBoundaries administrative, returning its Admin 0-2 chain. Supply a published ISO3 country to read that country's own Admin 0-3 geometry and loc_ids. MARINE requires one specific jurisdiction family (for example exclusive_economic_zone or high_seas), or water_body with water_kind=named or zone. The broad marine_jurisdiction category has no point route. No call crosses scopes or opens another family's bank. get_tool_help lists country scopes. 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:

- `batch_id` (string): Optional caller-supplied batch id echoed for point arrays.
- `family` (string): One exact family within the selected scope; defaults to administrative.
- `lat` (number): Latitude in WGS84 decimal degrees.
- `lon` (number): Longitude in WGS84 decimal degrees.
- `points` (array): Bounded WGS84 point array. Use top-level lat/lon instead for one point.
- `request_id` (string): Optional caller-supplied request id for tracing.
- `scope_id` (string): GLOBAL (default), MARINE, or one published ISO3 country. No automatic fallback into another scope.
- `water_kind` (string): Required only for MARINE water_body: named seas or water zones.

Output parameters:

- `available_deeper_admin_levels` (array)
- `batch_id` (string|null)
- `clarification` (object)
- `deeper_available` (boolean)
- `deepest_resolved_admin_level` (string|integer|null)
- `deepest_resolved_family` (string|null)
- `deepest_resolved_loc_id` (string|null)
- `error` (object)
- `family` (string)
- `family_result` (object)
- `guidance` (object)
- `join_keys` (object)
- `matched` (object|null)
- `meter_receipt` (object)
- `next_step` (object)
- `ok` (boolean)
- `overlap_families` (array)
- `point`
- `point_count` (integer)
- `reason` (string)
- `request_id` (string|null)
- `resolved_count` (integer)
- `results` (array)
- `settlement_receipt` (object)
- `shallow_loc_id` (string)
- `stack` (array)
- `unresolved_count` (integer)
- `warnings` (array)

### `resolve_bbox` (~157 tokens)

Resolve Map Viewport

Compare one non-wrapping rectangular WGS84 viewport in one scope. Omit scope_id for Global GeoBoundaries Admin 0-2, or supply one published ISO3 country for its own Admin 0-3 geometry and loc_ids. Returns the best equal-area overlap plus nearby matches at each level and their shares of the viewport and loc_id. Large views may require zooming in. get_tool_help lists country scopes.

Input parameters:

- `corners` (array, required): Four distinct corners of one axis-aligned rectangle; no antimeridian crossing.
- `request_id` (string): Optional caller-supplied tracing ID.
- `scope_id` (string): GLOBAL (default) or one published ISO3 country. No automatic cross-scope routing.

Output parameters:

- `admin_1_scope` (string)
- `batch_id` (string|null)
- `bbox` (object)
- `best_match` (object|null)
- `clarification` (object)
- `error` (object)
- `geometry_release` (string)
- `guidance` (object)
- `matches_by_admin_level` (object)
- `meter_receipt` (object)
- `next_step` (object)
- `ok` (boolean)
- `query_layout` (string)
- `ranking` (string)
- `reason` (string)
- `request_id` (string|null)
- `settlement_receipt` (object)
- `shallow_loc_id` (string)
- `warnings` (array)

### `resolve_deep_bbox` (~149 tokens)

Resolve Map Viewport (Deep)

Second-pass rectangle overlap after a country-scoped resolve_bbox call. Supply its deep_scope_loc_id as shallow_loc_id for a direct country-only read. Routes to that country's one Admin 1-owned exact partition and compares its Admin 1-6 spine. Supply the original four WGS84 corners; broad views may require zooming in.

Input parameters:

- `corners` (array, required): Four distinct corners of one axis-aligned rectangle; no antimeridian crossing.
- `request_id` (string): Optional caller-supplied tracing ID.
- `shallow_loc_id` (string, required): Use deep_scope_loc_id from the shallow result for a direct country-only read; its Admin 1 owner selects one deep partition.

Output parameters:

- `admin_1_scope` (string)
- `batch_id` (string|null)
- `bbox` (object)
- `best_match` (object|null)
- `clarification` (object)
- `error` (object)
- `geometry_release` (string)
- `guidance` (object)
- `matches_by_admin_level` (object)
- `meter_receipt` (object)
- `next_step` (object)
- `ok` (boolean)
- `query_layout` (string)
- `ranking` (string)
- `reason` (string)
- `request_id` (string|null)
- `settlement_receipt` (object)
- `shallow_loc_id` (string)
- `warnings` (array)

### `resolve_deep_point` (~334 tokens)

Resolve Point(s) (Deep)

Second-pass containment after a country-scoped resolve_point call. Supply the original WGS84 coordinate or a bounded point array, its returned deep_scope_loc_id as shallow_loc_id, and one canonical family from get_catalog(catalog='geometry'). family defaults to administrative; shape-backed families use direct bbox-to-exact-shape lookup without crosswalks. Single and bulk requests share this scoped contract. 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:

- `batch_id` (string): Optional caller-supplied batch id echoed for point arrays.
- `family` (string): One family selector. Defaults to administrative; use marine for the direct Marine resolver, or a canonical country family such as postal_area, watershed, or land_management_region.
- `lat` (number): Latitude in WGS84 decimal degrees.
- `lon` (number): Longitude in WGS84 decimal degrees.
- `points` (array): Points already known to fall within the supplied shallow_loc_id scope.
- `request_id` (string): Optional caller-supplied request id for tracing.
- `shallow_loc_id` (string, required): Pass deep_scope_loc_id from resolve_point for a direct country-only read, such as USA-NY.
- `target_admin_level`: Optional exact Admin 4-6 level. Omit for the deepest available match.

Output parameters:

- `available_deeper_admin_levels` (array)
- `batch_id` (string|null)
- `clarification` (object)
- `deeper_available` (boolean)
- `deepest_resolved_admin_level` (string|integer|null)
- `deepest_resolved_family` (string|null)
- `deepest_resolved_loc_id` (string|null)
- `error` (object)
- `family` (string)
- `family_result` (object)
- `guidance` (object)
- `join_keys` (object)
- `matched` (object|null)
- `meter_receipt` (object)
- `next_step` (object)
- `ok` (boolean)
- `overlap_families` (array)
- `point`
- `point_count` (integer)
- `reason` (string)
- `request_id` (string|null)
- `resolved_count` (integer)
- `results` (array)
- `settlement_receipt` (object)
- `shallow_loc_id` (string)
- `stack` (array)
- `unresolved_count` (integer)
- `warnings` (array)

## Diagnostics

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

## Score history

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

## Common questions

### What is the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server?

DaedalMap Reverse Geocoding (coordinates to loc_id) is an MCP server listed in the public MCP registry as com.daedalmap/reverse-geocoding. Resolve WGS84 points and map boxes to available administrative loc_id hierarchies. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry).

### Is the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server safe to use?

DaedalMap Reverse Geocoding (coordinates to loc_id) 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 Reverse Geocoding (coordinates to loc_id) MCP server expose?

DaedalMap Reverse Geocoding (coordinates to loc_id) exposes 7 tools: get_tool_help, get_catalog, get_geography, resolve_point, resolve_bbox, and 2 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.

### Does the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server require authentication?

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

### Is the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server still maintained?

DaedalMap Reverse Geocoding (coordinates to loc_id) 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 Reverse Geocoding (coordinates to loc_id) MCP server?

VerifyMCP ran 13 checks on DaedalMap Reverse Geocoding (coordinates to loc_id), 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/reverse-geocoding?registry=mcpregistry
- Repository: https://github.com/xyver/daedal-map
- Website: https://www.daedalmap.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-daedalmap-reverse-geocoding/mcp-reverse-geocoding-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-daedalmap-reverse-geocoding/mcp-reverse-geocoding-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-daedalmap-reverse-geocoding/mcp-reverse-geocoding-2.json
- HTML version of this page: https://verifymcp.io/servers/com-daedalmap-reverse-geocoding/mcp-reverse-geocoding-2
