QAmcp

Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.

Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions

NewYour score can change any day. QAmcp Monitor keeps testing your server and emails you when it breaks. Free for 1 server.See what Monitor does →

Directory / DaedalMap Geographic Data and Tools

DaedalMap Geographic Data and Tools

Q: Is DaedalMap Geographic Data and Tools MCP server safe?

QAmcp's test on 12 Nov 2026: None of the hidden-instruction wordings we know were found in its 16 tool descriptions. Its error messages showed no secrets or internal details. All 16 of its tools are labeled read-only. Overall it scored 69/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.

by daedalmap.com · https://app.daedalmap.com/mcp?registry=mcpregistry

Connect geographic IDs, places, shapes, and published data through DaedalMap tools.

16 tools✓ all read-only✓ no account neededPricing: on their site

See pricing →Visit website

69 /100

FAIL

Partial: 10 of 12 checks · 12 Nov 2026

Test it now for current results

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: 16 tools
Its own safety labels: 16 read-only
Memory it takes: About 7,600 tokens of your AI's memory, just for its tool descriptions

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 Geographic Data and Tools MCP server safe?

None of the hidden-instruction wordings we know were found in its 16 tool descriptions.
Its error messages showed no secrets or internal details.
All 16 of its tools are labeled read-only.
Overall it scored 69/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

16 tools, in the server's own words.

get_tool_helpread-only

Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.

get_catalogread-only

Choose data or geometry to list published pack IDs or family and scope IDs.

get_packread-only

Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.

get_geographyread-only

Inspect one published geometry family across scopes or one scope across families.

get_eventread-only

Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry.

resolve_pointread-only

Resolve WGS84 coordinates in exactly one selected scope and family.

resolve_bboxread-only

Compare one non-wrapping rectangular WGS84 viewport with the published Global administrative spine through Admin 2.

resolve_deep_bboxread-only

Second-pass rectangle overlap within one returned shallow administrative loc_id.

resolve_deep_pointread-only

Second-pass containment only after resolve_point.

get_loc_id_inforead-only

Look up one known loc_id or a small batch in the selected reference graph.

identify_dataset_geographyread-only

Fast structural column selector: pass bounded named columns to find recognized geography headers or latitude/longitude pairs.

identify_reference_systemread-only

Identify one selected identifier column within one required ISO3 country, GLOBAL, or MARINE scope.

convert_referenceread-only

Convert within one declared scope per call: iso3 is required and names one ISO3 country, GLOBAL, or MARINE.

compare_geographiesread-only

Compare two known loc_ids using selected reference-graph identity and direct relationship evidence.

get_shaperead-only

Shape lookup for exact existing loc_ids only.

get_dataread-only

Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit.

Test results

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

✕
Lists its tools
1 failed
- ✕Asking for the tool list failed: Error POSTing to endpoint: {"error":"The MCP service is receiving requests too quickly. Retry after the indicated delay.","error_code":"mcp_global_burst_limit"…
- and 1 more
fail
!
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
2 warnings
- !get_geography: Inputs with no description: family_id, scope_id, year
- !identify_dataset_geography: Inputs with no description: dataset_context, request_id
note
!
Follows MCP best practices (not scored yet)
1 tip (not scored)
- !The tool list is about 73 KB (roughly 18k tokens). AI apps send it with every message, so it takes that much of the AI's memory before any work starts.
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 98 ms
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
✓
Fast enough
All good
- ✓Connecting took 98 ms
- ✓Listing tools took 44 ms
pass
✓
No secrets leakedChecked 41 error messages: no secrets or internal details
pass
–
Tools work with good inputs
Not tested
- –get_tool_help: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –get_catalog: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –get_pack: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –get_geography: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –get_event: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –resolve_point: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –resolve_bbox: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- –resolve_deep_bbox: The server limited our requests (HTTP 429), so it was not tested (not counted against the server)
- and 8 more
not tested
–
Bad inputs give a clean error
Not tested
- –get_tool_help: The server limited our requests, so bad inputs were not tested
- –get_catalog: The server limited our requests, so bad inputs were not tested
- –get_pack: The server limited our requests, so bad inputs were not tested
- –get_geography: The server limited our requests, so bad inputs were not tested
- –get_event: The server limited our requests, so bad inputs were not tested
- –resolve_point: The server limited our requests, so bad inputs were not tested
- –resolve_bbox: The server limited our requests, so bad inputs were not tested
- –resolve_deep_bbox: The server limited our requests, so bad inputs were not tested
- and 8 more
not tested
–
Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
not tested

Test it yourself

Free and open source. Same checks, same score.

npx qamcp-cli https://app.daedalmap.com/mcp?registry=mcpregistry

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.

[![QAmcp score](https://qamcp.dev/s/com-daedalmap-county-map.svg)](https://qamcp.dev/s/com-daedalmap-county-map.html)

Score over time

12 Nov 202669

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use DaedalMap Geographic Data and Tools, signed in with GitHub, one per person. Reviews never change the score.

Is this your server? Get an alert the moment it breaks.

QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.

Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works