DaedalMap Administrative Boundaries (loc_id to polygon)

At a glance

Runs where

On their server. What you send to it goes to them.

What you need

Nothing: it answered without a login

Tools

7 tools

Its own safety labels

7 read-only

Memory it takes

About 1,900 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 1.2 KB in our test

Speed

Average answer in our test: 109 ms

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 12 Nov 2026.

Is DaedalMap Administrative Boundaries (loc_id to polygon) MCP server safe?

• None of the hidden-instruction wordings we know were found in its 7 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 7 of its tools are labeled read-only.
• Overall it scored 84/100 on 12 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

• Its source code and packages.
• What a tool quietly does behind the scenes, such as writing a file or calling another service.
• Instructions hidden inside live tool answers. We only look for those in tool descriptions.
• Hidden instructions worded in a way our list doesn't know yet.
• Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

Not looked up yet. QAmcp tests how a server behaves. It does not scan source code.

What it can do

7 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-06-18). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  1 warning

  • !get_geography: Inputs with no description: family_id, scope_id, year
  note
• !
  Resources and prompts work

  1 warning ()

  • –Could not list resources: the server limited our requests (HTTP 429)
  • !Listing resource templates failed: Error POSTing to endpoint: {"error":"The MCP service is receiving requests too quickly. Retry after the indicated delay.","error_code":"mcp…
  • –Could not list prompts: the server limited our requests (HTTP 429)
  note
• ✓
  ConnectsConnected in 376 ms
  pass
• ✓
  Lists its toolsFound 7 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓get_tool_help: Answered with an error, probably because of our sample input: Provide exactly one of tool_name or topic
  • ✓get_catalog: Worked (37 ms)
  • ✓get_pack: Answered with an error, probably because of our sample input: {"error":{"message":"Pack not found","code":"data_tool_failed"},"pack_id":"test","reason":"data_tool_failed","next_step":{"action":"review_…
  • ✓get_geography: Answered with an error, probably because of our sample input: get_geography requires exactly one of family_id or scope_id; optional year
  • ✓get_loc_id_info: Answered with an error, probably because of our sample input: use exactly one of loc_id or loc_ids; no other fields are accepted
  • –compare_geographies: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
  • –get_shape: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓get_tool_help: Refused wrong type for "tool_name" with a clear error
  • ✓get_catalog: Refused missing required input "catalog" with a clear error
  • ✓get_catalog: Refused wrong type for "catalog" with a clear error
  • ✓get_pack: Refused missing required input "pack_id" with a clear error
  • ✓get_pack: Refused wrong type for "pack_id" with a clear error
  • ✓get_geography: Refused wrong type for "family_id" with a clear error
  • ✓get_loc_id_info: Refused wrong type for "loc_id" with a clear error
  • –compare_geographies: The server limited our requests, so bad inputs were not tested
  • and 1 more
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 376 ms
  • ✓Listing tools took 38 ms
  • ✓Average tool answer: 109 ms
  • ✓get_pack: Slowest tool: get_pack (393 ms)
  pass
• ✓
  No secrets leakedChecked 15 error messages: no secrets or internal details
  pass
• ✓
  Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 12 Nov 202684

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use DaedalMap Administrative Boundaries (loc_id to polygon), signed in with GitHub, one per person. Reviews never change the score.