# Tennessee Property Records (remote · tnpropertysearch.app)

Who owns any Tennessee parcel: owner search, ownership and sale history across 2.8M parcels.

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

## Components

- remote · `tnpropertysearch.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch.md), [page](https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch)

## Channel facts

- Endpoint: `https://tnpropertysearch.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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 1717 tokens (~156/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Tennessee Property Records MCP server?

Tennessee Property Records is a hosted endpoint at https://tnpropertysearch.app/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 app-tnpropertysearch-tn-property 'https://tnpropertysearch.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-tnpropertysearch-tn-property": {
      "url": "https://tnpropertysearch.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-tnpropertysearch-tn-property": {
      "type": "http",
      "url": "https://tnpropertysearch.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-tnpropertysearch-tn-property]
url = "https://tnpropertysearch.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-tnpropertysearch-tn-property": {
      "type": "remote",
      "url": "https://tnpropertysearch.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-tnpropertysearch-tn-property --url 'https://tnpropertysearch.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-tnpropertysearch-tn-property:
    url: "https://tnpropertysearch.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-tnpropertysearch-tn-property": {
      "Transport": "http",
      "Url": "https://tnpropertysearch.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-tnpropertysearch-tn-property -t streamable-http -u 'https://tnpropertysearch.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-tnpropertysearch-tn-property": {
      "type": "http",
      "url": "https://tnpropertysearch.app/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-20 (score 70, +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-18 (score 69, +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-16 (score 68, +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-14 (score 67, +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-12 (score 66, +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-09 (score 65, +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-08 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 64)

First indexed and scored.

## MCP tools (11)

### `dataset_info` (~57 tokens)

Dataset overview

Start here. Describes what data exists: totals, every loaded county with parcel and ownership-record counts, how much ownership history each county has, which fields each county populates, data sources, bulk download files, query tips and usage terms.

### `search_properties` (~324 tokens)

Search properties

Find parcels by address words, current owner name, or location (near a point or inside a small box), optionally limited to a county, city or ZIP. Returns pin, address, owner, county, location and a link to the parcel in the map app. Paginate with next_cursor.

Input parameters:

- `address` (string): Property address words, any order, e.g. '1313 gallatin'.
- `bbox` (string): Bounding box 'west,south,east,north' in degrees (under about 5 km across).
- `city` (string): City name (populated mainly in Davidson).
- `county` (string): County name, or several comma-separated, e.g. 'Davidson,Williamson'.
- `cursor` (string): next_cursor from the previous page, to fetch the next page.
- `limit` (integer): Results per page, 1–200 (default varies by tool).
- `near` (string): Center point 'lat,lon', e.g. '36.1627,-86.7816'.
- `owner` (string): Current owner name words, e.g. 'bailey trust'. For former owners use search_owners.
- `q` (string): Free text matched against the address, or the current owner name.
- `radius_m` (number): Radius in meters around `near` (default 500, max 2000).
- `sort` (string): relevance (default with text), distance (default with near), address.
- `zip` (string): ZIP code(s), comma-separated.

### `get_property` (~127 tokens)

Property details and owner history

Everything known about one parcel: full parcel record, every ownership record (current and former, with acquisition dates, prices and deed references/links where the county provides them), sale history for Hamilton, and the county Register of Deeds website. Look up by pin, or by apn plus county.

Input parameters:

- `apn` (string): Assessor parcel number.
- `county` (string): County, to disambiguate apn.
- `include_geometry` (boolean): Include the boundary rings ([lon,lat] pairs).
- `pin` (string): Parcel id as returned by other tools.

### `property_at` (~43 tokens)

Property at a point

Which parcel contains a latitude/longitude. Uses the actual parcel boundary, not the nearest centroid.

Input parameters:

- `lat` (number, required): Latitude.
- `lon` (number, required): Longitude.

### `search_owners` (~132 tokens)

Find owners by name

Find people and companies by name across current AND former ownership records. Each result has an owner_key, how many properties they have ever owned and own now, their counties and first/last acquisition dates. Pass an owner_key to owner_portfolio for the full list.

Input parameters:

- `county` (string): Limit to county(ies).
- `current_only` (boolean): Only owners who currently hold property.
- `limit` (integer): Owners to return, 1–100 (default 20).
- `name` (string, required): Name words in any order, e.g. 'john smith' or 'ryman hospitality'.

### `owner_portfolio` (~171 tokens)

All properties for an owner

Every property an owner (by owner_key) or a mailing address has ever been recorded on, newest first, with whether they still own it, when they acquired it and the recorded price. Includes summary counts. Searching by mailing address groups LLCs and trusts that share a mailbox.

Input parameters:

- `county` (string): Limit to county(ies).
- `current_only` (boolean): Only properties still owned.
- `cursor` (string): next_cursor from the previous page, to fetch the next page.
- `limit` (integer): Records per page, 1–1000 (default 200).
- `mailing` (string): Exact mailing address as stored (from a property or owner record).
- `owner_key` (string): owner_key from search_owners (an exact name also works; it is normalized).

### `search_ownership_records` (~288 tokens)

Search ownership records / transfers

Ownership records (one row per owner per parcel) for an owner, owner_key, mailing address or pin, or every transfer recorded in one county over up to 3 calendar months. Filter by price, current vs former, and address; sort by date or price. Use it for questions like 'who bought in Davidson in March 2024 over $1M'.

Input parameters:

- `address` (string): Property address words (filters the other results).
- `county` (string): County (one, for date searches).
- `current` (boolean): true = current owners only, false = former owners only.
- `cursor` (string): next_cursor from the previous page, to fetch the next page.
- `date_from` (string): Acquired on or after, YYYY-MM-DD.
- `date_to` (string): Acquired on or before, YYYY-MM-DD.
- `limit` (integer): Results per page, 1–200 (default varies by tool).
- `mailing` (string): Exact mailing address.
- `max_price` (number): Maximum recorded price.
- `min_price` (number): Minimum recorded price.
- `owner` (string): Owner name words.
- `owner_key` (string): Exact owner_key.
- `pin` (string): Parcel pin(s), comma-separated.
- `sort` (string): date_desc (default), date_asc, price_desc.

### `property_stats` (~107 tokens)

Aggregate statistics

Parcel counts, total/average/median appraised value and total acres grouped by county, city, zip, land_use, zoning, owner, mailing or subdivision, statewide or for one county. Use it for 'largest owners in Davidson' or 'value by land use'.

Input parameters:

- `county` (string): One county (default: statewide).
- `group_by` (string): Field to group on.
- `limit` (integer): Groups to return, 1–500 (default 25).

### `refresh_property` (~78 tokens)

Refresh properties from the source

Re-read up to 5 parcels from their official county/state source right now (and, for Davidson, the full owner history), then return what changed. Use when last_checked is too old for the question, or the user says a record is out of date.

Input parameters:

- `pins` (string, required): Parcel pin(s), comma-separated (max 5).

### `recent_changes` (~232 tokens)

Recently detected changes

Changes the update jobs detected, newest first: owner_change (with old and new owners), new_parcel, and retired (parcel no longer listed by the county). Filter by county, kind, owner name, date or area.

Input parameters:

- `bbox` (string): Bounding box 'west,south,east,north'.
- `county` (string): County(ies).
- `cursor` (string): next_cursor from the previous page, to fetch the next page.
- `kind` (string): Kind(s), comma-separated: owner_change, new_parcel, retired.
- `limit` (integer): Results per page, 1–200 (default varies by tool).
- `near` (string): Center point 'lat,lon', e.g. '36.1627,-86.7816'.
- `owner` (string): Old or new owner name words.
- `radius_m` (number): Radius in meters around `near` (default 500).
- `since` (string): Detected on or after (YYYY-MM-DD).
- `until` (string): Detected on or before (YYYY-MM-DD).

### `update_status` (~41 tokens)

Data freshness and update jobs

How fresh the data is: when each county was last checked, the most recent update runs with their status and counts, what is in progress, and the schedule.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 64
- 2026-11-07: 64

## Common questions

### What is the Tennessee Property Records MCP server?

Tennessee Property Records is an MCP server listed in the public MCP registry as app.tnpropertysearch/tn-property. Who owns any Tennessee parcel: owner search, ownership and sale history across 2.8M parcels. This page covers its hosted endpoint (https://tnpropertysearch.app/mcp).

### Is the Tennessee Property Records MCP server safe to use?

Tennessee Property Records scores 70 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 Tennessee Property Records MCP server expose?

Tennessee Property Records exposes 11 tools: dataset_info, search_properties, get_property, property_at, search_owners, and 6 more. Their descriptions and schemas cost roughly 1,600 tokens of context every time the server is loaded.

### Does the Tennessee Property Records MCP server require authentication?

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

### Is the Tennessee Property Records MCP server still maintained?

Tennessee Property Records 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 Tennessee Property Records MCP server?

VerifyMCP ran 12 checks on Tennessee Property Records, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tennessee Property Records: HTTPS. 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://tnpropertysearch.app/mcp
- Website: https://tnpropertysearch.app/agents
- Changelog RSS feed: https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch.json
- HTML version of this page: https://verifymcp.io/servers/app-tnpropertysearch-tn-property/tnpropertysearch
