Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tennessee Property Records

REMOTE · TNPROPERTYSEARCH.APP

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

+3 this week 70 Trust /100

Last scanned (18 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 9 Nov 26 +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.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tnpropertysearch.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tnpropertysearch.app CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 60dbe9159132e3f50ed6acb68017d168
SANs: tnpropertysearch.app, www.tnpropertysearch.app, *.www.tnpropertysearch.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tnpropertysearch.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
tnpropertysearch.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tnpropertysearch.app/mcp Verified 200
http (plaintext) http://tnpropertysearch.app/mcp Inconclusive 405
MCP tools · 11 exposed · ~1,600 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
dataset_info ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_property ~127

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.

NameTypeReqDescription
apnstring–Assessor parcel number.
countystring–County, to disambiguate apn.
include_geometryboolean–Include the boundary rings ([lon,lat] pairs).
pinstring–Parcel id as returned by other tools.

No output schema declared.

No examples provided.

owner_portfolio ~171

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.

NameTypeReqDescription
countystring–Limit to county(ies).
current_onlyboolean–Only properties still owned.
cursorstring–next_cursor from the previous page, to fetch the next page.
limitinteger–Records per page, 1–1000 (default 200).
mailingstring–Exact mailing address as stored (from a property or owner record).
owner_keystring–owner_key from search_owners (an exact name also works; it is normalized).

No output schema declared.

No examples provided.

property_at ~43

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

NameTypeReqDescription
latnumberyesLatitude.
lonnumberyesLongitude.

No output schema declared.

No examples provided.

property_stats ~107

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'.

NameTypeReqDescription
countystring–One county (default: statewide).
group_bystring–Field to group on.
limitinteger–Groups to return, 1–500 (default 25).

No output schema declared.

No examples provided.

recent_changes ~232

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.

NameTypeReqDescription
bboxstring–Bounding box 'west,south,east,north'.
countystring–County(ies).
cursorstring–next_cursor from the previous page, to fetch the next page.
kindstring–Kind(s), comma-separated: owner_change, new_parcel, retired.
limitinteger–Results per page, 1–200 (default varies by tool).
nearstring–Center point 'lat,lon', e.g. '36.1627,-86.7816'.
ownerstring–Old or new owner name words.
radius_mnumber–Radius in meters around `near` (default 500).
sincestring–Detected on or after (YYYY-MM-DD).
untilstring–Detected on or before (YYYY-MM-DD).

No output schema declared.

No examples provided.

refresh_property ~78

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.

NameTypeReqDescription
pinsstringyesParcel pin(s), comma-separated (max 5).

No output schema declared.

No examples provided.

search_owners ~132

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.

NameTypeReqDescription
countystring–Limit to county(ies).
current_onlyboolean–Only owners who currently hold property.
limitinteger–Owners to return, 1–100 (default 20).
namestringyesName words in any order, e.g. 'john smith' or 'ryman hospitality'.

No output schema declared.

No examples provided.

search_ownership_records ~288

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'.

NameTypeReqDescription
addressstring–Property address words (filters the other results).
countystring–County (one, for date searches).
currentboolean–true = current owners only, false = former owners only.
cursorstring–next_cursor from the previous page, to fetch the next page.
date_fromstring–Acquired on or after, YYYY-MM-DD.
date_tostring–Acquired on or before, YYYY-MM-DD.
limitinteger–Results per page, 1–200 (default varies by tool).
mailingstring–Exact mailing address.
max_pricenumber–Maximum recorded price.
min_pricenumber–Minimum recorded price.
ownerstring–Owner name words.
owner_keystring–Exact owner_key.
pinstring–Parcel pin(s), comma-separated.
sortstring–date_desc (default), date_asc, price_desc.

No output schema declared.

No examples provided.

search_properties ~324

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.

NameTypeReqDescription
addressstring–Property address words, any order, e.g. '1313 gallatin'.
bboxstring–Bounding box 'west,south,east,north' in degrees (under about 5 km across).
citystring–City name (populated mainly in Davidson).
countystring–County name, or several comma-separated, e.g. 'Davidson,Williamson'.
cursorstring–next_cursor from the previous page, to fetch the next page.
limitinteger–Results per page, 1–200 (default varies by tool).
nearstring–Center point 'lat,lon', e.g. '36.1627,-86.7816'.
ownerstring–Current owner name words, e.g. 'bailey trust'. For former owners use search_owners.
qstring–Free text matched against the address, or the current owner name.
radius_mnumber–Radius in meters around `near` (default 500, max 2000).
sortstring–relevance (default with text), distance (default with near), address.
zipstring–ZIP code(s), comma-separated.

No output schema declared.

No examples provided.

update_status ~41

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · tnpropertysearch.app

# add to Claude Code
claude mcp add --transport http app-tnpropertysearch-tn-property 'https://tnpropertysearch.app/mcp'
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.