SENTINEL Washington Real Estate
REMOTE · APP.SENTINELIQ.NET · 2 COMPONENTS
Washington property evidence and transaction math for agents in Claude, ChatGPT and AI apps.
Available components
Last scanned (12 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 767 tokens (~255/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 0
- Stability: 0.87 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Nov 2026 · Probed https://app.sentineliq.net/api/v1/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.sentineliq.net | CN=YR1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 6f8ad2182bf87cd444893bf1d26403932fb |
| SANs: app.sentineliq.net | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.sentineliq.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| sentineliq.net. | 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 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.sentineliq.net/api/v1/mcp/public | Verified | 200 | |
| http (plaintext) | http://app.sentineliq.net/api/v1/mcp/public | HTTPS enforced | 301 | https://app.sentineliq.net/api/v1/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 →
nwmls_deadlines NWMLS deadline calculator ~269
Compute the standard NWMLS transaction deadline set from a mutual-acceptance date: earnest money (Form 21), seller disclosure delivery + buyer rescission (Form 17, RCW 64.06), title contingency (Form 22T), inspection (Form 35), financing (Form 22A), and FIRPTA certification (Form 22E). Business-day counts exclude weekends and Washington state holidays per RCW 1.16.050 — never plain calendar arithmetic. Washington/NWMLS transactions only. Dates are the standard form DEFAULTS computed from public rules (no NWMLS data or form text); the result flags dates landing on non-business days and includes a verify-against-the-executed-contract disclaimer that must accompany any advice built on these dates. The result includes an 'attributions' array (upstream source lines and the NWMLS/DOR/county non-affiliation line) and a professional-advice disclaimer — pass both through to end users.
| Name | Type | Req | Description |
|---|---|---|---|
| closing | – | – | Optional contract closing date (on/after mutual acceptance), ISO YYYY-MM-DD. |
| financingDays | integer | – | Form 22A financing-contingency length. |
| mutualAcceptance | string | yes | Mutual acceptance date, ISO YYYY-MM-DD (within 5 years of today). |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| deadline_disclaimer | string | yes | – |
| deadlines | array | yes | – |
| disclaimer | string | yes | – |
| financing_days | integer | yes | – |
| mutual_acceptance | string | yes | – |
No examples provided.
wa_net_sheet Washington seller net sheet ~243
Estimate a Washington home seller's net proceeds: commission, graduated REET, title/escrow/closing costs, mortgage payoff, and optional HOA/tax prorations — every line item computed deterministically by the same engine SENTINEL's product uses. Use for 'what will the seller walk away with' questions on WA sales; WA counties only. The result is an itemized dict. Uses no third-party data. The result includes an 'attributions' array (upstream source lines and the NWMLS/DOR/county non-affiliation line) and a professional-advice disclaimer — pass both through to end users.
| Name | Type | Req | Description |
|---|---|---|---|
| commissionRate | number | – | Total commission as a decimal fraction (0.05 = 5%). Defaults to the NWMLS-typical rate. |
| county | string | – | Washington county the property sits in (lowercase). |
| hasHoa | boolean | – | Include HOA transfer/resale-cert fees. |
| mortgageBalance | integer | – | Outstanding mortgage payoff in dollars. |
| propertyTaxProration | integer | – | Seller-side property-tax proration, dollars. |
| salePrice | integer | yes | Contract sale price in whole US dollars. |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| commission | integer | yes | – |
| commission_rate | number | yes | – |
| county | string | yes | – |
| disclaimer | string | yes | – |
| escrow_fee | integer | yes | – |
| hoa_transfer | integer | yes | – |
| local_reet | integer | yes | – |
| local_reet_assumption | string | yes | – |
| local_reet_rate | number | yes | – |
| local_reet_rate_effective_date | string | yes | – |
| mortgage_payoff | integer | yes | – |
| net_proceeds | integer | yes | – |
| property_tax_proration | integer | yes | – |
| recording_fees | integer | yes | – |
| reet_scope | string | yes | – |
| reet_technology_fee | integer | yes | – |
| sale_price | integer | yes | – |
| state_reet | integer | yes | – |
| state_reet_brackets | array | yes | – |
| state_reet_brackets_effective_through | string | yes | – |
| title_insurance | integer | yes | – |
| total_costs | integer | yes | – |
| total_deductions | integer | yes | – |
| total_reet | integer | yes | – |
No examples provided.
wa_reet Washington REET calculator ~194
Calculate Washington State Real Estate Excise Tax (REET, RCW 82.45) for one sale: graduated state brackets plus the county's local rate, computed deterministically by SENTINEL's production engine — never estimated. Use when you need the exact excise tax owed on a WA home sale (seller-paid by default). Washington State counties only. The result includes the per-bracket breakdown, the $5 DOR technology fee, and rate-assumption caveats (verify the DOR location code for city-level exceptions). Uses no third-party data. The result includes an 'attributions' array (upstream source lines and the NWMLS/DOR/county non-affiliation line) and a professional-advice disclaimer — pass both through to end users.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Washington county the property sits in (lowercase). |
| salePrice | integer | yes | Contract sale price in whole US dollars. |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| county | string | yes | – |
| disclaimer | string | yes | – |
| effective_rate_pct | number | yes | – |
| estimated_total_due | integer | yes | total_reet + technology_fee. |
| local_rate | number | yes | – |
| local_rate_assumption | string | yes | County-level local-rate assumption; verify the DOR location code. |
| local_rate_effective_date | string | yes | – |
| local_reet | integer | yes | – |
| reet_scope | string | yes | – |
| sale_price | integer | yes | – |
| state_brackets | array | yes | – |
| state_brackets_effective_through | string | yes | – |
| state_reet | integer | yes | – |
| technology_fee | integer | yes | Flat DOR electronic-technology fee (RCW 82.45.180). |
| total_reet | integer | yes | – |
No examples provided.
How do I install the SENTINEL Washington Real Estate MCP server?
SENTINEL Washington Real Estate is a hosted endpoint at https://app.sentineliq.net/api/v1/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 · app.sentineliq.net
claude mcp add --transport http cheadlee10-sentinel-wa-realestate 'https://app.sentineliq.net/api/v1/mcp/public'
What is the SENTINEL Washington Real Estate MCP server?
SENTINEL Washington Real Estate is an MCP server listed in the public MCP registry as io.github.cheadlee10/sentinel-wa-realestate. Washington property evidence and transaction math for agents in Claude, ChatGPT and AI apps. This page covers its hosted endpoint (https://app.sentineliq.net/api/v1/mcp/public).
Is the SENTINEL Washington Real Estate MCP server safe to use?
SENTINEL Washington Real Estate scores 83 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 SENTINEL Washington Real Estate MCP server expose?
SENTINEL Washington Real Estate exposes 3 tools: wa_reet, wa_net_sheet, nwmls_deadlines. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.
Does the SENTINEL Washington Real Estate MCP server require authentication?
No. We connected to SENTINEL Washington Real Estate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SENTINEL Washington Real Estate MCP server still maintained?
SENTINEL Washington Real Estate 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 SENTINEL Washington Real Estate MCP server?
VerifyMCP ran 13 checks on SENTINEL Washington Real Estate, 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.