Skip to content

DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server

com.daedalmap/reverse-geocodingdaedalmap.comstreamable-httpv1.4.3Scanned

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

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server can do

The DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server is published by daedalmap.com, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.4.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • get_catalogChoose data or geometry to list published pack IDs or family and scope IDs.No findings

    Why it is in this group

    • The name "get_catalog" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List Published Packs or Geographies
  • get_geographyInspect one published geometry family across scopes or one scope across families.No findings

    Why it is in this group

    • The name "get_geography" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Inspect One Geography Family or Scope
  • get_tool_helpDescribe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.No findings

    Why it is in this group

    • The name "get_tool_help" says "get": a word for reading.
    Description, as the server wrote it
    Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get Tool Help
  • resolve_bboxCompare one non-wrapping rectangular WGS84 viewport with the published Global administrative spine through Admin 2.No findings

    Why it is in this group

    • The name "resolve_bbox" says "resolve": a word for reading.
    Description, as the server wrote it
    Compare one non-wrapping rectangular WGS84 viewport with the published Global administrative spine through Admin 2. Supply its four corners. 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. This tool reads no country deep bank.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Resolve Map Viewport
  • resolve_deep_bboxSecond-pass rectangle overlap within one returned shallow administrative loc_id.No findings

    Why it is in this group

    • The name "resolve_deep_bbox" says "resolve": a word for reading.
    Description, as the server wrote it
    Second-pass rectangle overlap within one returned shallow administrative loc_id. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Resolve Map Viewport (Deep)
  • resolve_deep_pointSecond-pass containment only after resolve_point.No findings

    Why it is in this group

    • The name "resolve_deep_point" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Resolve Point(s) (Deep)
  • resolve_pointResolve WGS84 coordinates in exactly one selected scope and family.No findings

    Why it is in this group

    • The name "resolve_point" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Resolve Point(s) in One Scope

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:25 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 5 changed.+2 added~5 changedView diff
  2. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.4.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http reverse-geocoding https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry
claude mcp add --transport http reverse-geocoding https://app.daedalmap.com/mcp/reverse-geocoding?registry=mcpregistry

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__reverse-geocoding__get_tool_help",
      "mcp__reverse-geocoding__get_catalog",
      "mcp__reverse-geocoding__get_geography",
      "mcp__reverse-geocoding__resolve_point",
      "mcp__reverse-geocoding__resolve_bbox",
      "mcp__reverse-geocoding__resolve_deep_bbox",
      "mcp__reverse-geocoding__resolve_deep_point"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as reverse-geocoding. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.daedalmap/reverse-geocoding/verify?hash=b59a6c1543e652c32307a87952382cf123a39288137650c11f327f4ee5ed0a14" | jq -e '.changed == false'

Pinned hash b59a6c1543e6, from Nov 12, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.daedalmap/reverse-geocoding/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.daedalmap/reverse-geocoding
[![Anlyon Radar](https://radar.anlyon.com/badge/com.daedalmap/reverse-geocoding.svg)](https://radar.anlyon.com/servers/com.daedalmap/reverse-geocoding)

Source: MCP Registry · repository. Synced Nov 12, 2026, 07:17 UTC.

DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server have?

7 tools: 7 read. get_tool_help, get_catalog, get_geography, resolve_point, resolve_bbox, resolve_deep_bbox and resolve_deep_point.

Does the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DaedalMap Reverse Geocoding (coordinates to loc_id) MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.