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

Convert WGS84 coordinates to the latest available administrative loc_id chain.

−1 this week 81 Trust /100

Last scanned (44 minutes ago)

Scores higher than 83% of remote servers

Reachable. Last reached 5 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
Transport & Reachability100
Schema Quality & AI Usability77
  • 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 1702 tokens (~154/item across 11 items; 5 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 Management68
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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.

  • 5 Nov 26 0
    • Stability: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: 77% → 87% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • “get_geography” dropped the optional parameter “include_geometry” cosmetic
    • “get_geography” dropped the optional parameter “page” cosmetic
    • “get_geography” dropped the optional parameter “page_size” cosmetic
    • Tool “get_geography” changed its title: Discover or Read Geography Coverage → Inspect One Geography Family or Scope cosmetic
  • 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
  • 31 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 87% → 77% ▼ 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
  • 25 Oct 26 0
    • Tool “resolve_point” rewrote its description, which is the text the model reads security
    • “resolve_point” reworded the description of “family” cosmetic
  • 24 Oct 26 0
    • Tool “resolve_point” rewrote its description, which is the text the model reads security
    • “resolve_point” added an optional parameter “family” cosmetic
    • “resolve_point” added an optional parameter “scope_id” cosmetic
    • “resolve_point” added an optional parameter “water_kind” cosmetic
    • Tool “resolve_point” changed its title: Resolve Point(s) (Shallow) → Resolve Point(s) in One Scope cosmetic
  • 22 Oct 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 70.

  • 17 Oct 26 −4
    • A breaking change shipped without a version bump: still 1.4.2 ▼ security
    • Tool “get_pack” was removed ▼ 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 “resolve_deep_point” 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 coverage: 100% → 85% ▼ functional
    • “get_catalog” made “catalog” required, so existing callers break ▼ functional
    • Schema quality: 168 → 150 ▲ functional
    • Schema quality: excellent → good functional
    • New tool “get_geography” functional
    • “get_catalog” reworded the description of “catalog” 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
    • “resolve_point” dropped the optional parameter “include_marine_context” cosmetic
    • “resolve_point” dropped the optional parameter “target_admin_level” cosmetic
    • Tool “get_catalog” changed its title: List Available Packs and Geometry Families → List Published Packs or Geographies cosmetic
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 64 to 71.

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 5 Nov 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
MCP tools · 5 exposed · ~947 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––
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_deep_point ~334

Second-pass containment only after resolve_point. Supply the original WGS84 coordinate or a bounded point array, one shared shallow_loc_id returned by resolve_point, 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_idstringyesThe 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.
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 ~321

Resolve WGS84 coordinates in exactly one selected scope and family. GLOBAL administrative finds Admin0; an ISO3 administrative scope finds its shallow country bank. 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. Discover families with get_catalog(catalog='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
batch_idstring–Optional caller-supplied batch id echoed for point arrays.
familystring–One exact family within the selected scope.
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, 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, 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'
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. 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 81 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 5 tools: get_tool_help, get_catalog, get_geography, resolve_point, resolve_deep_point. Their descriptions and schemas cost roughly 947 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.