# GetParcelData (remote · api.getparceldata.com)

US parcel boundaries and assessor data: lookup by APN, point, radius or polygon.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.getparceldata.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-getparceldata-parcels/api.md), [page](https://verifymcp.io/servers/com-getparceldata-parcels/api)

## Channel facts

- Endpoint: `https://api.getparceldata.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1167 tokens (~166/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the GetParcelData MCP server?

GetParcelData is a hosted endpoint at https://api.getparceldata.com/mcp, 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.

### Claude

```bash
claude mcp add --transport http com-getparceldata-parcels 'https://api.getparceldata.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-getparceldata-parcels": {
      "url": "https://api.getparceldata.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getparceldata-parcels": {
      "type": "http",
      "url": "https://api.getparceldata.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getparceldata-parcels]
url = "https://api.getparceldata.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getparceldata-parcels": {
      "type": "remote",
      "url": "https://api.getparceldata.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getparceldata-parcels --url 'https://api.getparceldata.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getparceldata-parcels:
    url: "https://api.getparceldata.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getparceldata-parcels": {
      "Transport": "http",
      "Url": "https://api.getparceldata.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getparceldata-parcels -t streamable-http -u 'https://api.getparceldata.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-getparceldata-parcels": {
      "type": "http",
      "url": "https://api.getparceldata.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03

## MCP tools (7)

### `check_coverage` (~98 tokens)

Check county coverage

Free, no API key. Says whether a county is in the current data release, or lists every covered county in a state when no county is given. Parcel lookups in counties that are not covered cost no credits.

Input parameters:

- `county`: Optional county name, 3-digit county code or 5-digit FIPS
- `state` (string, required): USPS code, state name or 2-digit state FIPS, e.g. 'TX'

### `get_pricing` (~65 tokens)

Get prices and plans

Free, no API key. Returns the monthly API plans (price, included credits, overage per credit, rate limit), the credit cost of each lookup type and the one-off extract downloads. Statewide and nationwide licences are quoted at https://getparceldata.com/pricing.

### `preview_area` (~131 tokens)

Count parcels in an area

Free, no API key. Counts the parcels inside a bounding box, lists the counties it touches, and says whether the area fits the $49 extract of up to 5,000 parcels. Each side of the box can be up to 2 degrees. Limited to 30 requests per IP address per minute.

Input parameters:

- `east` (number, required): Eastern longitude, EPSG:4326
- `north` (number, required): Northern latitude, EPSG:4326
- `south` (number, required): Southern latitude, EPSG:4326
- `west` (number, required): Western longitude, EPSG:4326

### `find_parcels_by_apn` (~232 tokens)

Find parcels by APN

Finds parcels by assessor parcel number (APN) in one county. Costs 1 credit per completed request, including no_match and ambiguous results. Up to 100 parcels per request. Validate each candidate before using it. Needs an API key. Lookups in counties we do not cover and failed requests cost no credits. Returns parcel records with WKT boundaries in EPSG:4326, owner, address, assessed values, land use and zoning where the county publishes them.

Input parameters:

- `apn` (string, required): APN, with any leading zeros
- `county` (string, required): County name, 5-digit FIPS or 3-digit county code
- `limit` (integer): Parcels per request, 1 to 100
- `match_mode` (string): normalized ignores punctuation and case; exact needs the original identifier; contains (alpha) finds identifiers containing the input
- `offset` (integer): Parcels to skip; each page is a new, charged request
- `state`: USPS code, state name or 2-digit FIPS; needed with a county name

### `find_parcels_at_point` (~157 tokens)

Find parcels at a point

Finds the parcels that contain a latitude and longitude. Costs 1 credit per request, however many parcels come back. Up to 1,000 parcels per request. Needs an API key. Lookups in counties we do not cover and failed requests cost no credits. Returns parcel records with WKT boundaries in EPSG:4326, owner, address, assessed values, land use and zoning where the county publishes them.

Input parameters:

- `lat` (number, required): Latitude, decimal degrees
- `limit` (integer): Parcels per request, 1 to 1,000
- `lng` (number, required): Longitude, decimal degrees
- `offset` (integer): Parcels to skip; each page is a new, charged request

### `find_parcels_in_radius` (~187 tokens)

Find parcels within a radius

Finds every parcel within a radius of a point, nearest first. Costs 3 credits per request, however many parcels come back. Radius up to 5,000 metres. Up to 1,000 parcels per request. Needs an API key. Lookups in counties we do not cover and failed requests cost no credits. Returns parcel records with WKT boundaries in EPSG:4326, owner, address, assessed values, land use and zoning where the county publishes them.

Input parameters:

- `lat` (number, required): Latitude, decimal degrees
- `limit` (integer): Parcels per request, 1 to 1,000
- `lng` (number, required): Longitude, decimal degrees
- `offset` (integer): Parcels to skip; each page is a new, charged request
- `radius_m` (number, required): Radius in metres, up to 5,000

### `find_parcels_in_polygon` (~194 tokens)

Find parcels in a polygon

Finds every parcel that intersects a WKT geometry (polygon, multipolygon, line or point). Costs 3 credits per request, however many parcels come back. The geometry's bounding box can be up to 25 km². Up to 1,000 parcels per request. Needs an API key. Lookups in counties we do not cover and failed requests cost no credits. Returns parcel records with WKT boundaries in EPSG:4326, owner, address, assessed values, land use and zoning where the county publishes them.

Input parameters:

- `limit` (integer): Parcels per request, 1 to 1,000
- `offset` (integer): Parcels to skip; each page is a new, charged request
- `wkt` (string, required): WKT in EPSG:4326 lon/lat order, e.g. POLYGON((-97.75 30.26, ...))

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getparceldata-parcels/api#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73
- 2026-11-12: 72
- 2026-11-11: 72
- 2026-11-10: 71
- 2026-11-09: 71
- 2026-11-08: 71
- 2026-11-07: 70
- 2026-11-06: 70

## Common questions

### What is the GetParcelData MCP server?

GetParcelData is an MCP server listed in the public MCP registry as com.getparceldata/parcels. US parcel boundaries and assessor data: lookup by APN, point, radius or polygon. This page covers its hosted endpoint (https://api.getparceldata.com/mcp).

### Is the GetParcelData MCP server safe to use?

GetParcelData scores 77 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 GetParcelData MCP server expose?

GetParcelData exposes 7 tools: check_coverage, get_pricing, preview_area, find_parcels_by_apn, find_parcels_at_point, and 2 more. Their descriptions and schemas cost roughly 1,064 tokens of context every time the server is loaded.

### Does the GetParcelData MCP server require authentication?

No. We connected to GetParcelData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GetParcelData MCP server still maintained?

GetParcelData is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the GetParcelData MCP server?

VerifyMCP ran 13 checks on GetParcelData, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.getparceldata.com/mcp
- Website: https://getparceldata.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-getparceldata-parcels/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getparceldata-parcels/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-getparceldata-parcels/api.json
- HTML version of this page: https://verifymcp.io/servers/com-getparceldata-parcels/api
