DaedalMap Reverse Geocoding (coordinates to loc_id)
REMOTE · APP.DAEDALMAP.COM · SCANNED SEP 20
Convert WGS84 coordinates to the latest available administrative loc_id chain.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1927 tokens (~148/item across 13 items; 7 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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, 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-reverse-geocoding 'https://app.daedalmap.com/mcp/reverse-geocoding'
{
"mcpServers": {
"com-daedalmap-reverse-geocoding": {
"url": "https://app.daedalmap.com/mcp/reverse-geocoding"
}
}
} {
"servers": {
"com-daedalmap-reverse-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/reverse-geocoding"
}
}
} [mcp_servers.com-daedalmap-reverse-geocoding] url = "https://app.daedalmap.com/mcp/reverse-geocoding"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-daedalmap-reverse-geocoding": {
"type": "remote",
"url": "https://app.daedalmap.com/mcp/reverse-geocoding",
"enabled": true
}
}
} openclaw mcp add com-daedalmap-reverse-geocoding --url 'https://app.daedalmap.com/mcp/reverse-geocoding' --transport streamable-http
mcp_servers:
com-daedalmap-reverse-geocoding:
url: "https://app.daedalmap.com/mcp/reverse-geocoding" {
"McpServers": {
"com-daedalmap-reverse-geocoding": {
"Transport": "http",
"Url": "https://app.daedalmap.com/mcp/reverse-geocoding"
}
}
} assistant mcp add com-daedalmap-reverse-geocoding -t streamable-http -u 'https://app.daedalmap.com/mcp/reverse-geocoding'
{
"mcpServers": {
"com-daedalmap-reverse-geocoding": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/reverse-geocoding"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “get_pack” added an optional parameter “detail” cosmetic
- 17 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Sept 26 −1
- A breaking change shipped without a version bump: still 1.2.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “resolve_deep_point” rewrote its description, which is the text the model reads security
- Tool “resolve_deep_points” rewrote its description, which is the text the model reads security
- Tool “resolve_point” rewrote its description, which is the text the model reads security
- Tool “resolve_points” rewrote its description, which is the text the model reads security
- “resolve_deep_point” added a required parameter “shallow_loc_id”, so existing callers break ▼ functional
- “resolve_deep_points” added a required parameter “shallow_loc_id”, so existing callers break ▼ functional
- “resolve_deep_point” dropped the required parameter “admin_1_loc_id” ▼ functional
- “resolve_deep_points” dropped the required parameter “admin_1_loc_id” ▼ functional
- “resolve_deep_point” added an optional parameter “family” cosmetic
- “resolve_deep_points” added an optional parameter “family” cosmetic
- “resolve_deep_points” reworded the description of “points” cosmetic
- “resolve_deep_point” dropped the optional parameter “include_marine_context” cosmetic
- “resolve_deep_points” dropped the optional parameter “include_marine_context” cosmetic
- 14 Sept 26 −1
- Stability: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_catalog” 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 “get_tool_help” rewrote its description, which is the text the model reads security
- Tool “resolve_point” rewrote its description, which is the text the model reads security
- Schema quality: 1593 → 1889 ▼ functional
- “resolve_point” made “lat” required, so existing callers break ▼ functional
- “resolve_point” made “lon” required, so existing callers break ▼ functional
- Tool “get_catalog” now declares an output schema ▲ functional
- Tool “get_pack” now declares an output schema ▲ functional
- Tool “get_tool_help” now declares an output schema ▲ functional
- First check of Tool coverage: 43 functional
- Server version: 1.0.4 → 1.2.0 functional
- New tool “resolve_deep_point” functional
- New tool “resolve_deep_points” functional
- New tool “resolve_points” functional
- “resolve_point” reworded the description of “target_admin_level” cosmetic
- “resolve_point” dropped the optional parameter “admin_1_scope” cosmetic
- “resolve_point” dropped the optional parameter “batch_id” cosmetic
- “resolve_point” dropped the optional parameter “bulk_preset” cosmetic
- “resolve_point” dropped the optional parameter “country_hint” cosmetic
- “resolve_point” dropped the optional parameter “country_scope” cosmetic
- “resolve_point” dropped the optional parameter “lookup_mode” cosmetic
- “resolve_point” dropped the optional parameter “points” cosmetic
- Tool “resolve_point” changed its title: Resolve Point to loc_id → Resolve Point (Shallow) cosmetic
- 13 Sept 26 0
- 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
- Schema quality: 141 → 159 ▼ functional
- Schema quality: good → excellent functional
- “resolve_point” added an optional parameter “admin_1_scope” cosmetic
- “resolve_point” added an optional parameter “include_marine_context” cosmetic
- “resolve_point” added an optional parameter “lookup_mode” cosmetic
- “resolve_point” reworded the description of “bulk_preset” cosmetic
- “resolve_point” reworded the description of “country_scope” cosmetic
- “resolve_point” reworded the description of “points” cosmetic
- “resolve_point” reworded the description of “target_admin_level” cosmetic
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 6 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Sept 26 0
- 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
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 20 Sept 2026 · Probed https://app.daedalmap.com/mcp/reverse-geocoding
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.daedalmap.com | CN=YR2,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | RSA 2048 | SHA256-RSA | 51023d45112daf6159a4fae4a177632589f |
| SANs: app.daedalmap.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
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/reverse-geocoding | Verified | 200 | |
| http (plaintext) | http://app.daedalmap.com/mcp/reverse-geocoding | HTTPS enforced | 301 | https://app.daedalmap.com/mcp/reverse-geocoding |
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 →
get_catalog Get Catalog ~33
List the current catalog-published data packs and their access lanes. Start here, then call get_pack for one selected pack.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| catalog_version | string | – | – |
| clarification | object | – | – |
| error | object | – | – |
| generated_at | string|null | – | – |
| guidance | object | – | – |
| next_step | object | – | – |
| pack_count | integer | – | – |
| packs | array | – | – |
| provenance | object | – | – |
| reason | string | – | – |
| request_id | string|null | – | – |
| tool_families | array | – | – |
| warnings | array | – | – |
No examples provided.
get_pack Get Pack ~90
Describe one catalog-published pack, including sources, metrics, coverage, freshness, access, and a first query. Call this before querying an unfamiliar pack.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required. |
| pack_id | string | yes | Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change. |
| Name | Type | Req | Description |
|---|---|---|---|
| clarification | object | – | – |
| error | 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_tool_help Get Tool Help ~51
Describe one tool visible on this facade, including its input contract, access limits, refusals, example, outputs, and recommended next calls.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_name | string | yes | Exact tool name from tools/list. |
| 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.
resolve_deep_point Resolve Point (Deep) ~281
Second-pass resolution for one WGS84 coordinate. Supply a shallow_loc_id returned by resolve_point and one canonical family from read_geometry_catalog. family defaults to administrative; shape-backed families use direct bbox-to-exact-shape lookup without crosswalks. For multiple coordinates use resolve_deep_points. 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 |
|---|---|---|---|
| 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 | yes | Latitude in WGS84 decimal degrees. |
| lon | number | yes | Longitude in WGS84 decimal degrees. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| shallow_loc_id | string | yes | The deepest canonical Admin 1-3 loc_id returned by resolve_point, such as USA-NY-061-009903. |
| target_admin_level | – | – | Optional exact Admin 4-6 level. Omit for the deepest available match. |
No output schema declared.
No examples provided.
resolve_deep_points Resolve Points (Deep Bulk) ~269
Bulk second-pass resolution for one family. Supply a bounded WGS84 point array, one shared shallow_loc_id scope, and one canonical family. family defaults to administrative; other shape-backed families use direct bbox candidates followed by exact containment without crosswalks. 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 |
|---|---|---|---|
| batch_id | string | – | Optional caller-supplied batch id echoed in the result. |
| family | string | – | One canonical family ID for the entire batch. |
| points | array | yes | Points already known to fall within the supplied shallow_loc_id scope. Maximum 100 per call during the initial technical rollout. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| shallow_loc_id | string | yes | A canonical Admin 1-3 loc_id returned by resolve_points. All coordinates in the call must belong to its scope. |
| target_admin_level | – | – | Optional exact Admin 4-6 level. Omit for the deepest available match. |
No output schema declared.
No examples provided.
resolve_point Resolve Point (Shallow) ~251
Compact first-pass reverse geocoding for one WGS84 coordinate. Returns an administrative loc_id chain through Admin 3 without opening deep partitions or side-family shape banks. Use its deepest shallow loc_id with resolve_deep_point for Admin 4-6 or one explicit family. For multiple coordinates use resolve_points. 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 |
|---|---|---|---|
| include_marine_context | boolean | – | Include parallel Marine overlaps for land matches. Defaults to true; set false for fast administrative loc_id previews. Offshore Marine fallback still applies. |
| lat | number | yes | Latitude in WGS84 decimal degrees. |
| lon | number | yes | Longitude in WGS84 decimal degrees. |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| target_admin_level | – | – | Optional exact requested level from Admin 0-3. Omit it to return the deepest available shallow level. |
No output schema declared.
No examples provided.
resolve_points Resolve Points (Shallow Bulk) ~206
Bulk first-pass reverse geocoding through Admin 3. Accepts a bounded cross-country WGS84 point array and never opens deep partitions or side-family shape banks. Group results by shallow scope before calling resolve_deep_points once per scope and family. 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 |
|---|---|---|---|
| batch_id | string | – | Optional caller-supplied batch id echoed in the result. |
| include_marine_context | boolean | – | Include parallel Marine overlaps. Defaults to true. |
| points | array | yes | – |
| request_id | string | – | Optional caller-supplied request id for tracing. |
| target_admin_level | – | – | Optional exact Admin 0-3 level. |
No output schema declared.
No examples provided.
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. Convert WGS84 coordinates to the latest available administrative loc_id chain. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/reverse-geocoding).
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_pack, resolve_point, resolve_points, and 2 more. Their descriptions and schemas cost roughly 1,181 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.