EstateTrace Pre-Probate Intelligence
REMOTE · API.ESTATETRACE.AI · SCANNED SEP 20
Pre-probate and inheritance real estate intelligence with Base L2 USDC settlement.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 521 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the EstateTrace Pre-Probate Intelligence MCP server?
EstateTrace Pre-Probate Intelligence is a hosted endpoint at https://api.estatetrace.ai/mcp/sse, 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 · api.estatetrace.ai
claude mcp add --transport http palunallc-estatetrace-mcp 'https://api.estatetrace.ai/mcp/sse'
{
"mcpServers": {
"palunallc-estatetrace-mcp": {
"url": "https://api.estatetrace.ai/mcp/sse"
}
}
} {
"servers": {
"palunallc-estatetrace-mcp": {
"type": "http",
"url": "https://api.estatetrace.ai/mcp/sse"
}
}
} [mcp_servers.palunallc-estatetrace-mcp] url = "https://api.estatetrace.ai/mcp/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"palunallc-estatetrace-mcp": {
"type": "remote",
"url": "https://api.estatetrace.ai/mcp/sse",
"enabled": true
}
}
} openclaw mcp add palunallc-estatetrace-mcp --url 'https://api.estatetrace.ai/mcp/sse' --transport streamable-http
mcp_servers:
palunallc-estatetrace-mcp:
url: "https://api.estatetrace.ai/mcp/sse" {
"McpServers": {
"palunallc-estatetrace-mcp": {
"Transport": "http",
"Url": "https://api.estatetrace.ai/mcp/sse"
}
}
} assistant mcp add palunallc-estatetrace-mcp -t streamable-http -u 'https://api.estatetrace.ai/mcp/sse'
{
"mcpServers": {
"palunallc-estatetrace-mcp": {
"type": "http",
"url": "https://api.estatetrace.ai/mcp/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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.
- 6 Sept 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.
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://api.estatetrace.ai/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=estatetrace.ai | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 65ef228a9753166613b5466805adc53d |
| SANs: estatetrace.ai, *.estatetrace.ai | ||||||
| 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 api.estatetrace.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| estatetrace.ai. | 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 | 405 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://api.estatetrace.ai/mcp/sse | Verified | 200 | |
| http (plaintext) | http://api.estatetrace.ai/mcp/sse | HTTPS enforced | 302 | https://api.estatetrace.ai/mcp/sse |
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 →
estatetrace_a2a_checkout ~77
Initiate machine checkout for candidate leads. Returns HTTP 402 with Base L2 USDC payment instructions and a 120-second atomic reservation lock.
| Name | Type | Req | Description |
|---|---|---|---|
| lead_ids | array | yes | Array of lead UUIDs to purchase. |
| promo_code | string | – | Optional promo voucher code (e.g. 'LAUNCH25'). |
No output schema declared.
No examples provided.
estatetrace_a2a_inventory ~218
Discover available candidate pre-probate real estate leads for autonomous agents. Returns zero-PII teasers, confidence scores, estimated equity metrics, and lead_ids in 44 compliant states + DC (excludes CA, OR, WA, CT, NJ, MD).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional target city (e.g. 'Huntsville', 'Dallas'). |
| county | string | – | Optional target county (e.g. 'Madison', 'Jefferson', 'Dallas'). |
| limit | integer | – | Max results to return (default 10, max 50). |
| min_equity | number | – | Optional minimum estimated equity spread filter. |
| state | string | yes | Two-letter state abbreviation (e.g. 'AL', 'TX', 'FL', 'TN'). Required. |
| tier | integer | – | Optional motivation tier (1: High Equity/Core, 2: Moderate, 3: High Distress/Urgent). |
| zip_code | string | – | Optional 5-digit ZIP code. |
No output schema declared.
No examples provided.
estatetrace_a2a_settle ~84
Submit a completed Base L2 USDC transaction hash to verify payment and receive the unblurred lead payload with ephemeral living heir intelligence.
| Name | Type | Req | Description |
|---|---|---|---|
| charge_id | string | yes | The charge ID returned from the 402 checkout challenge. |
| tx_hash | string | yes | On-chain transaction hash confirming USDC transfer on Base L2 (chain 8453). |
No output schema declared.
No examples provided.
estatetrace_a2a_status ~43
Check the status of a lead reservation (pending, settled, expired, or released).
| Name | Type | Req | Description |
|---|---|---|---|
| charge_id | string | yes | The charge ID to inspect. |
No output schema declared.
No examples provided.
estatetrace_search_signals ~99
Discover available pre-probate real estate leads by county or state (44 compliant states). Returns anonymized teasers and lead IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| county_ids | string | yes | County identifier (e.g. 'madison_al', 'jefferson_al') or county name. |
| tiers | string | – | Comma-separated motivation tiers: '1' (High Equity/Core Metro), '2' (Standard), '3' (Value). |
No output schema declared.
No examples provided.
What is the EstateTrace Pre-Probate Intelligence MCP server?
EstateTrace Pre-Probate Intelligence is an MCP server listed in the public MCP registry as io.github.palunallc/estatetrace-mcp. Pre-probate and inheritance real estate intelligence with Base L2 USDC settlement. This page covers its hosted endpoint (https://api.estatetrace.ai/mcp/sse).
Is the EstateTrace Pre-Probate Intelligence MCP server safe to use?
EstateTrace Pre-Probate Intelligence scores 66 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 EstateTrace Pre-Probate Intelligence MCP server expose?
EstateTrace Pre-Probate Intelligence exposes 5 tools: estatetrace_a2a_inventory, estatetrace_search_signals, estatetrace_a2a_checkout, estatetrace_a2a_settle, estatetrace_a2a_status. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.
Does the EstateTrace Pre-Probate Intelligence MCP server require authentication?
No. We connected to EstateTrace Pre-Probate Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EstateTrace Pre-Probate Intelligence MCP server still maintained?
EstateTrace Pre-Probate Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.