HeritageDeed Title Search and Property Data
REMOTE · HERITAGEDEED.COM
US title search, auction pre-checks, surplus and tax sale lists, free flood, radon and LLC lookups.
Available components
Last scanned (15 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11476 tokens (~197/item across 58 items; 58 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_tax" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 59 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_property_watch” rewrote its description, which is the text the model reads security
- Tool “list_products” rewrote its description, which is the text the model reads security
- Tool “order_title_search” rewrote its description, which is the text the model reads security
- Tool “surplus_funds_search” rewrote its description, which is the text the model reads security
- Tool “tax_sale_search” rewrote its description, which is the text the model reads security
- Schema quality: 10221 → 11476 ▼ functional
- New tool “auction_precheck_summary” functional
- New tool “buy_county_list_pass” functional
- New tool “buy_plan” functional
- New tool “my_account” functional
- New tool “upcoming_auction_sales” functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_property_watch” rewrote its description, which is the text the model reads security
- Tool “flood_zone_lookup” rewrote its description, which is the text the model reads security
- Tool “hoa_lookup” rewrote its description, which is the text the model reads security
- Tool “order_tax_appeal_evidence” rewrote its description, which is the text the model reads security
- Tool “order_title_search” rewrote its description, which is the text the model reads security
- Tool “power_lines_near_address” rewrote its description, which is the text the model reads security
- Tool “radon_by_county” rewrote its description, which is the text the model reads security
- Tool “radon_lookup” rewrote its description, which is the text the model reads security
- Tool “start_tax_sale_due_diligence” rewrote its description, which is the text the model reads security
- Tool “superfund_sites_near_address” rewrote its description, which is the text the model reads security
- Tool “surplus_funds_search” rewrote its description, which is the text the model reads security
- Tool “tax_sale_search” rewrote its description, which is the text the model reads security
- Tool “usda_eligibility_lookup” rewrote its description, which is the text the model reads security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Tool “building_records_lookup” rewrote its description, which is the text the model reads security
- Tool “property_history_lookup” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://heritagedeed.com/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=heritagedeed.com | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5bf7a08e0b823ef16d372afb79beef826da |
| SANs: *.heritagedeed.com, heritagedeed.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of heritagedeed.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| heritagedeed.com. | 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://heritagedeed.com/mcp/public | Verified | 200 | |
| http (plaintext) | http://heritagedeed.com/mcp/public | HTTPS enforced | 301 | https://heritagedeed.com/mcp/public |
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 →
tax_sale_search ~350
Search properties still on an official tax sale / sheriff sale list. `state`: two-letter code or name; `county`: optional county name (e.g. "Horry"; New York City boroughs by county: "Kings" for Brooklyn); `sort`: sale_date_asc, sale_date_desc, amount_desc or amount_asc; `page_number` from 1, `per_page` 1 to 100. Each row: case or certificate number, parcel id, property address, owner (people as initials, businesses as recorded), sale type and date, the amount as the office labels it (opening bid, judgment, taxes due; some lists publish none), appraised value where given, status and the official list URL. Rows leave the list when the office removes them (paid, redeemed, sold, cancelled). Before bidding, a title search on the parcel shows the other liens and mortgages of record: order_title_search where the county is covered. Free preview: this tool returns the first 10 rows of each county's list (page_number above 1 is empty) with the county's true `total_rows`; the full list and the CSV open with a County List Pass ($19 one-time, 30 days, one county: buy_county_list_pass) or HeritageDeed Pro ($39 a month, every county: buy_plan); the `message` field says so. Summaries are complete.
| Name | Type | Req | Description |
|---|---|---|---|
| county | – | – | – |
| page_number | integer | – | – |
| per_page | integer | – | – |
| sort | string | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
tax_sale_summary ~99
Per county: rows on the official tax sale list, the next and last sale dates, the total of the published amounts, the list's own date and the last refresh, the office and list URL, the statute, the cited bidding and redemption rules and how to bid, and whether HeritageDeed's title search covers the county. Optional `state` (code or name) narrows it.
| Name | Type | Req | Description |
|---|---|---|---|
| state | – | – | – |
No output schema declared.
No examples provided.
title_insurance_premium ~335
Title insurance premiums from the official rate schedule, free: Texas (TDI promulgated basic premium, effective March 1, 2026), Florida (Rule 69O-186.003), Pennsylvania (TIRBOP manual, August 1, 2024) and New York (TIRSA Seventh Revision, October 1, 2024, Zone 1 / Zone 2). `state`: TX, FL, PA or NY. `owner_amount`: owner's policy amount, usually the price (0 for a refinance = loan policy only); `loan_amount`: lender's policy amount (0 for cash). New York: `ny_county` (e.g. "Erie", "Kings", "Brooklyn") or `ny_zone` (1 or 2; NYC and downstate are Zone 2, the default). Pennsylvania: `pa_homeowner` for the ALTA Homeowner's Policy (+10%). Florida: `fl_prior_policy` = the seller's prior owner's policy amount when the reissue rate applies. Returns owner, loan and fee totals, every line with its rule, notes on what is excluded, the schedule's regulator, manual and effective date, and the sources. An estimate: endorsements and settlement fees are extra.
| Name | Type | Req | Description |
|---|---|---|---|
| fl_prior_policy | number | – | – |
| loan_amount | number | – | – |
| ny_county | – | – | – |
| ny_zone | – | – | – |
| owner_amount | number | – | – |
| pa_homeowner | boolean | – | – |
| state | string | yes | – |
No output schema declared.
No examples provided.
transfer_tax ~209
Real estate transfer taxes on a sale, from the statutes and tax offices, free. `place`: nyc (all five boroughs), ny (New York State outside NYC), fl (Florida outside Miami-Dade), philadelphia, chicago, cook (Cook County outside Chicago), nc, sc, ar, tx or az (state or city names work too). `price`: the consideration in dollars. `kind`: residential or other (NYC rates differ). `mortgage`: Florida only, the new mortgage amount (adds note stamps and the intangible tax). Returns each tax with its amount and who customarily pays (seller, buyer, negotiable), the total, flags for what is not included (NYC supplemental tax, local municipal taxes), and the sources. An estimate, not tax advice.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| mortgage | number | – | – |
| place | string | yes | – |
| price | number | yes | – |
No output schema declared.
No examples provided.
ucc_lien_search ~201
UCC financing statements (and NYC federal tax lien notices) where a BUSINESS is the debtor. `name`: the debtor business name as registered (e.g. 'Publix Super Markets, Inc.'). `where`: 'all' (default), 'FL' (Florida Secured Transaction Registry, statewide), 'NYC' (ACRIS personal property records: fixture and co-op filings and federal tax liens, four boroughs), 'CO' or 'CT' (state open data). Returns each filing's number, type, filing date, lapse date, status, secured parties and, in NYC, the property. New York State (DOS), Texas, Illinois, Ohio, Arizona and Pennsylvania are not searched automatically; `not_automated` gives each official search link and why. Refuses a person's name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| where | string | – | – |
No output schema declared.
No examples provided.
upcoming_auction_sales ~156
Upcoming tax sales and sheriff sales in the next 21 days in counties HeritageDeed title-searches, each with how many properties are listed and how many were already pre-checked with a title search: how many carry an open mortgage (on a mortgage foreclosure the loan being foreclosed is not counted), a second mortgage, a lien, a lis pendens, open code violations or a high risk score, and how many came back clear. Optional `state` (two-letter code or name). Counts only: no addresses or owners. The per-property results come with the county's auction pack (buy_county_list_pass, product 'auction_pack').
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | – |
No output schema declared.
No examples provided.
usda_eligibility_lookup ~180
Is a US street address in a USDA Rural Development eligible area (the property-location test for USDA Single Family Housing Direct and Guaranteed loans, Section 502, and Multifamily Housing)? Give a full street address with city and state. Locates the address, then checks the point against USDA's official ineligible-area map layer (the one USDA's own Property Eligibility map uses). Returns eligible true/false, the matched address and county. NOT an official USDA determination (Rural Development decides on a complete application) and location only: household income limits (USDA income tool linked in the answer), credit and loan approval are separate. status 'not_determined' means USDA's map service did not answer: never read it as yes or no.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
zoning_lookup ~143
Zoning district of a property in New York City, Chicago or Philadelphia, from the city's own zoning data: the district (e.g. R6B, DC-16, RM-1), commercial overlays / overlay districts, special or planned development districts, and links to the city's zoning text. `place`: an NYC borough ('Manhattan', 'Brooklyn', 'Queens', 'Bronx', 'Staten Island'; 'nyc' works when the address names its borough or ZIP), 'chicago' or 'philadelphia'. Not an official zoning determination.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| place | string | yes | – |
No output schema declared.
No examples provided.
How do I install the HeritageDeed Title Search and Property Data MCP server?
HeritageDeed Title Search and Property Data is a hosted endpoint at https://heritagedeed.com/mcp/public, 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 · heritagedeed.com
claude mcp add --transport http com-heritagedeed-title-search 'https://heritagedeed.com/mcp/public'
What is the HeritageDeed Title Search and Property Data MCP server?
HeritageDeed Title Search and Property Data is an MCP server listed in the public MCP registry as com.heritagedeed/title-search. US title search, auction pre-checks, surplus and tax sale lists, free flood, radon and LLC lookups. This page covers its hosted endpoint (https://heritagedeed.com/mcp/public).
Is the HeritageDeed Title Search and Property Data MCP server safe to use?
HeritageDeed Title Search and Property Data 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 HeritageDeed Title Search and Property Data MCP server expose?
HeritageDeed Title Search and Property Data exposes 58 tools: list_coverage, check_coverage, check_address, order_title_search, get_order_status, and 53 more. Their descriptions and schemas cost roughly 9,732 tokens of context every time the server is loaded.
Does the HeritageDeed Title Search and Property Data MCP server require authentication?
No. We connected to HeritageDeed Title Search and Property Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HeritageDeed Title Search and Property Data MCP server still maintained?
HeritageDeed Title Search and Property Data is still listed as active in the MCP registry. We last reached this channel on 5 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 HeritageDeed Title Search and Property Data MCP server?
VerifyMCP ran 13 checks on HeritageDeed Title Search and Property Data, 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.