GetParcelData

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.4 KB in our test

Tools that look alike

3 pairs of tools with nearly the same description, so the AI may pick the wrong one

Speed

Average answer in our test: 172 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, 6 Nov 2026.

Is GetParcelData 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 88/100 on 6 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

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. 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-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  3 warnings

  • !find_parcels_at_point and find_parcels_in_radius have nearly the same description (77% of their words are shared; the only difference: "contain", "latitude", "longitude" vs "radiu", "point", "every"), so an AI may not know which to pick
  • !find_parcels_in_radius and find_parcels_in_polygon have nearly the same description (75% of their words are shared; the only difference: "radiu", "within", "nearest" vs "polygon", "intersect", "geometry"), so an AI may not know which to pic
  • !find_parcels_at_point and find_parcels_in_polygon have nearly the same description (74% of their words are shared; the only difference: "contain", "latitude", "longitude" vs "polygon", "point", "every"), so an AI may not know which to pick
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !1 tool answers with structured data but doesn't declare its shape (outputSchema): get_pricing. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
  note
• ✓
  ConnectsConnected in 458 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

  • ✓check_coverage: Answered with an error, probably because of our sample input: Error executing tool check_coverage: invalid_state: State must be a USPS code, state FIPS code or state name.
  • ✓get_pricing: Worked (117 ms)
  • ✓preview_area: Answered with an error, probably because of our sample input: Error executing tool preview_area: HTTP 400: {"detail":"bbox must satisfy west<east and south<north, within valid lat/lon"}
  • ✓find_parcels_by_apn: Answered with an error, probably because of our sample input: Error executing tool find_parcels_by_apn: This tool needs a GetParcelData API key. Connect with the header 'Authorization: Bearer <key>'. G…
  • ✓find_parcels_at_point: Answered with an error, probably because of our sample input: Error executing tool find_parcels_at_point: This tool needs a GetParcelData API key. Connect with the header 'Authorization: Bearer <key>'.…
  • ✓find_parcels_in_radius: Answered with an error, probably because of our sample input: Error executing tool find_parcels_in_radius: This tool needs a GetParcelData API key. Connect with the header 'Authorization: Bearer <key>'…
  • ✓find_parcels_in_polygon: Answered with an error, probably because of our sample input: Error executing tool find_parcels_in_polygon: This tool needs a GetParcelData API key. Connect with the header 'Authorization: Bearer <key>…
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓check_coverage: Refused missing required input "state" with a clear error
  • ✓check_coverage: Refused wrong type for "state" with a clear error
  • ✓preview_area: Refused missing required input "west" with a clear error
  • ✓preview_area: Refused wrong type for "west" with a clear error
  • ✓find_parcels_by_apn: Refused missing required input "apn" with a clear error
  • ✓find_parcels_by_apn: Refused wrong type for "apn" with a clear error
  • ✓find_parcels_at_point: Refused missing required input "lat" with a clear error
  • ✓find_parcels_at_point: Refused wrong type for "lat" with a clear error
  • and 4 more
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 458 ms
  • ✓Listing tools took 439 ms
  • ✓Average tool answer: 172 ms
  • ✓find_parcels_at_point: Slowest tool: find_parcels_at_point (431 ms)
  pass
• ✓
  No secrets leakedChecked 18 error messages: no secrets or internal details
  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

• 6 Nov 202688

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use GetParcelData, signed in with GitHub, one per person. Reviews never change the score.