Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DaedalMap Reverse Geocoding (coordinates to loc_id)

REMOTE · APP.DAEDALMAP.COM

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

+5 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +2
    • 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 security
    • MCP protocol: fail → pass ▲ functional
    • MCP protocol version: 2025-06-18 → 2026-07-28 functional
    • “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” cosmetic
  • 18 Nov 26 +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.

  • 17 Nov 26 +51
    • Injection markers: unverified → pass ▲ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Stability: unverified → 0.17 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 16 Nov 26 −15
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
  • 15 Nov 26 −35
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • 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 functional
  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry

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 16 Nov 2026 14 Feb 2027 RSA 2048 SHA256-RSA 5cde8394eddd0e99a1b20787e389bc54747
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. DS published 19718 13 Verified
daedalmap.com. No DS 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?registry=mcpregistry Verified 200
http (plaintext) http://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry HTTPS enforced 301 https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry
MCP tools · 7 exposed · ~1,280 tokens

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 →

Tool Tokens
get_catalog ~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.

NameTypeReqDescription
catalogstringyesRequired directory selector.
NameTypeReqDescription
catalogstring––
catalog_versionstring––
clarificationobject––
detailstring––
download_urlstring––
errorobject––
excluded_countinteger––
familiesarray––
free_get_data_policy_notestring––
generated_atstring|null––
guidanceobject––
next_stepobject––
pack_countinteger––
packsarray––
provenanceobject––
reasonstring––
request_idstring|null––
resolved_queryobject––
result_statusstring––
scopesarray––
tool_familiesarray––
uncertain_countinteger––
uncertain_packsarray––
warningsarray––

No examples provided.

get_geography ~83

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.

NameTypeReqDescription
family_idstring––
scope_idstring––
yearinteger––
NameTypeReqDescription
admin_spineobject––
catalogstring––
clarificationobject––
coveragearray––
errorobject––
family_idstring|null––
guidanceobject––
next_stepobject––
provenanceobject––
reasonstring––
request_idstring|null––
requested_yearinteger|null––
scope_idstring|null––
warningsarray––

No examples provided.

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.

NameTypeReqDescription
questionstring–Optional question used only with a topic overview.
tool_namestring–Exact tool name from tools/list. Do not combine with topic.
topicstring–Workflow overview. Do not combine with tool_name.
NameTypeReqDescription
accessobject––
clarificationobject––
errorobject––
examplesarray––
guidanceobject––
important_output_fieldsarray––
input_schemaobject––
next_stepobject––
okboolean––
provenanceobject––
purposestring––
reasonstring––
recommended_next_callsarray––
request_idstring|null––
titlestring|null––
tool_namestring––
warningsarray––

No examples provided.

resolve_bbox ~157

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.

NameTypeReqDescription
cornersarrayyesFour distinct corners of one axis-aligned rectangle; no antimeridian crossing.
request_idstring–Optional caller-supplied tracing ID.
scope_idstring–GLOBAL (default) or one published ISO3 country. No automatic cross-scope routing.
NameTypeReqDescription
admin_1_scopestring––
batch_idstring|null––
bboxobject––
best_matchobject|null––
clarificationobject––
errorobject––
geometry_releasestring––
guidanceobject––
matches_by_admin_levelobject––
meter_receiptobject––
next_stepobject––
okboolean––
query_layoutstring––
rankingstring––
reasonstring––
request_idstring|null––
settlement_receiptobject––
shallow_loc_idstring––
warningsarray––

No examples provided.

resolve_deep_bbox ~149

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.

NameTypeReqDescription
cornersarrayyesFour distinct corners of one axis-aligned rectangle; no antimeridian crossing.
request_idstring–Optional caller-supplied tracing ID.
shallow_loc_idstringyesUse deep_scope_loc_id from the shallow result for a direct country-only read; its Admin 1 owner selects one deep partition.
NameTypeReqDescription
admin_1_scopestring––
batch_idstring|null––
bboxobject––
best_matchobject|null––
clarificationobject––
errorobject––
geometry_releasestring––
guidanceobject––
matches_by_admin_levelobject––
meter_receiptobject––
next_stepobject––
okboolean––
query_layoutstring––
rankingstring––
reasonstring––
request_idstring|null––
settlement_receiptobject––
shallow_loc_idstring––
warningsarray––

No examples provided.

resolve_deep_point ~334

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.

NameTypeReqDescription
batch_idstring–Optional caller-supplied batch id echoed for point arrays.
familystring–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.
latnumber–Latitude in WGS84 decimal degrees.
lonnumber–Longitude in WGS84 decimal degrees.
pointsarray–Points already known to fall within the supplied shallow_loc_id scope.
request_idstring–Optional caller-supplied request id for tracing.
shallow_loc_idstringyesPass 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.
NameTypeReqDescription
available_deeper_admin_levelsarray––
batch_idstring|null––
clarificationobject––
deeper_availableboolean––
deepest_resolved_admin_levelstring|integer|null––
deepest_resolved_familystring|null––
deepest_resolved_loc_idstring|null––
errorobject––
familystring––
family_resultobject––
guidanceobject––
join_keysobject––
matchedobject|null––
meter_receiptobject––
next_stepobject––
okboolean––
overlap_familiesarray––
point–––
point_countinteger––
reasonstring––
request_idstring|null––
resolved_countinteger––
resultsarray––
settlement_receiptobject––
shallow_loc_idstring––
stackarray––
unresolved_countinteger––
warningsarray––

No examples provided.

resolve_point ~348

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.

NameTypeReqDescription
batch_idstring–Optional caller-supplied batch id echoed for point arrays.
familystring–One exact family within the selected scope; defaults to administrative.
latnumber–Latitude in WGS84 decimal degrees.
lonnumber–Longitude in WGS84 decimal degrees.
pointsarray–Bounded WGS84 point array. Use top-level lat/lon instead for one point.
request_idstring–Optional caller-supplied request id for tracing.
scope_idstring–GLOBAL (default), MARINE, or one published ISO3 country. No automatic fallback into another scope.
water_kindstring–Required only for MARINE water_body: named seas or water zones.
NameTypeReqDescription
available_deeper_admin_levelsarray––
batch_idstring|null––
clarificationobject––
deeper_availableboolean––
deepest_resolved_admin_levelstring|integer|null––
deepest_resolved_familystring|null––
deepest_resolved_loc_idstring|null––
errorobject––
familystring––
family_resultobject––
guidanceobject––
join_keysobject––
matchedobject|null––
meter_receiptobject––
next_stepobject––
okboolean––
overlap_familiesarray––
point–––
point_countinteger––
reasonstring––
request_idstring|null––
resolved_countinteger––
resultsarray––
settlement_receiptobject––
shallow_loc_idstring––
stackarray––
unresolved_countinteger––
warningsarray––

No examples provided.

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.

remote · app.daedalmap.com

# add to Claude Code
claude mcp add --transport http com-daedalmap-reverse-geocoding 'https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry'
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.