Texas Treasure Map
REMOTE · MCP.TEXASTREASUREMAP.COM
Estate sales around Dallas-Fort Worth, route planning between them, and Texas shopping guides.
Available components
Last scanned (23 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 22 Oct 2026.
Category E-commerce
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 689 tokens (~137/item across 5 items; 5 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 Oct 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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 69
First indexed and scored.
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 22 Oct 2026 · Probed https://mcp.texastreasuremap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.texastreasuremap.com | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 581735c232e0d3b87b0675ee4fa0c445d8b |
| SANs: mcp.texastreasuremap.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 mcp.texastreasuremap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| texastreasuremap.com. | absent | 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://mcp.texastreasuremap.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.texastreasuremap.com/mcp | HTTPS enforced | 308 | https://mcp.texastreasuremap.com/mcp |
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 →
get_estate_sale Get one estate sale ~56
Days, hours, address, host and link for one estate sale, by the id search_estate_sales returns.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The sale id, e.g. "s0618b657e28e". |
No output schema declared.
No examples provided.
get_estate_sale_guide Read an estate sale guide ~62
The full text of one guide, with its questions and answers, by the slug list_estate_sale_guides returns.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | e.g. "how-to-find-estate-sales-in-texas" or "plano". |
No output schema declared.
No examples provided.
list_estate_sale_guides List estate sale guides ~57
Texas Treasure Map guides: how estate sales work in Texas and how to find them, plus a guide to each DFW city (where sales cluster, permit rules, neighborhoods). Titles, short answers, slugs and links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_estate_sale_route Plan an estate sale route ~164
Put 2 to 10 estate sales in driving order for one day, from an optional starting point, with each stop's hours that day and a Google Maps link for the whole trip. Order is by straight-line distance. Sales whose street address is not posted yet, or that are not open that day, are left off and listed separately.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD. Defaults to the day most of the chosen sales are open. |
| sale_ids | array | yes | Sale ids from search_estate_sales. |
| start_city | string | – | Where the trip starts, e.g. "Richardson". Or use start_latitude and start_longitude. |
| start_latitude | number | – | – |
| start_longitude | number | – | – |
No output schema declared.
No examples provided.
search_estate_sales Search estate sales ~160
Estate sales coming up near a city or point in the Dallas-Fort Worth area, nearest first. Defaults to the next 7 days within 15 miles. Returns up to 20 sales with days, hours, address (or city, until the address is posted), host and a link.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | A Texas city or town, e.g. "Plano", "Fort Worth" or "DFW". |
| end_date | string | – | YYYY-MM-DD, at most 14 days after start_date. |
| latitude | number | – | Use with longitude instead of city. |
| longitude | number | – | – |
| radius_miles | number | – | – |
| start_date | string | – | YYYY-MM-DD. Defaults to today. |
No output schema declared.
No examples provided.
How do I install the Texas Treasure Map MCP server?
Texas Treasure Map is a hosted endpoint at https://mcp.texastreasuremap.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.
remote · mcp.texastreasuremap.com
claude mcp add --transport http com-texastreasuremap-estate-sales 'https://mcp.texastreasuremap.com/mcp'
What is the Texas Treasure Map MCP server?
Texas Treasure Map is an MCP server listed in the public MCP registry as com.texastreasuremap/estate-sales. Estate sales around Dallas-Fort Worth, route planning between them, and Texas shopping guides. This page covers its hosted endpoint (https://mcp.texastreasuremap.com/mcp).
Is the Texas Treasure Map MCP server safe to use?
Texas Treasure Map scores 72 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 Texas Treasure Map MCP server expose?
Texas Treasure Map exposes 5 tools: search_estate_sales, get_estate_sale, plan_estate_sale_route, list_estate_sale_guides, get_estate_sale_guide. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.
Does the Texas Treasure Map MCP server require authentication?
No. We connected to Texas Treasure Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Texas Treasure Map MCP server still maintained?
Texas Treasure Map is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.