Remote MCP · Endpoint

Texas Treasure Map MCP server

No. Texas Treasure Map answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://mcp.texastreasuremap.com/mcp

The last check completed an MCP handshake.

Registry name
com.texastreasuremap/estate-sales
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
83 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Estate sales around Dallas-Fort Worth, route planning between them, and Texas shopping guides.
Listing
From the official MCP registry (active).
Recent checks of Texas Treasure Map
CheckedResultHandshake
12 minutes agoHandshake completed83 ms
9 days agoHandshake completed64 ms
9 days agoHandshake completed55 ms
11 days agoHandshake completed53 ms
12 days agoHandshake completed188 ms
13 days agoHandshake completed55 ms
14 days agoHandshake completed63 ms
14 days agoHandshake completed76 ms
16 days agoHandshake completed51 ms
19 days agoHandshake completed57 ms
21 days agoHandshake completed56 ms
24 days agoHandshake completed58 ms
26 days agoHandshake completed57 ms
28 days agoHandshake completed57 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Texas Treasure Map and makes no claim about it beyond what these checks measured.