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 (18 hours ago)
Scores higher than 71% 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 Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4028 tokens (~236/item across 17 items; 17 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
- 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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.
- 21 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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 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.
- 9 Nov 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.
- 7 Nov 26 0
- Endpoint reachability: unreachable → reachable ▲ 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
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 | Verified | 200 | |
| http (plaintext) | http://app.sentineliq.net/api/v1/mcp | HTTPS enforced | 301 | https://app.sentineliq.net/api/v1/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 →
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_compare_offers Compare Washington purchase offers ~149
Compare buyer offers using seller proceeds, concessions and the supplied financing and contingency terms. Make tradeoffs visible without treating the highest price as an automatic recommendation or predicting closing. 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 means 5%. Commission is negotiable. |
| county | string | yes | – |
| hasHoa | boolean | – | – |
| mortgageBalance | – | – | – |
| offers | array | yes | – |
| propertyTaxProration | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| comparison_basis | string | yes | – |
| county | string | yes | – |
| disclaimer | string | – | – |
| discussion_points | array | yes | – |
| fully_comparable | boolean | yes | – |
| highest_proceeds_labels | array | yes | – |
| missing_or_unclear | array | yes | – |
| mortgage_balance | – | yes | – |
| offers | array | yes | – |
| proceeds_spread | – | yes | – |
No examples provided.
wa_compare_seller_scenarios Compare Washington seller proceeds ~100
Compare multiple proposed sale prices using explicit seller cost assumptions. Return itemized proceeds for each scenario and the difference between them. Prices are supplied scenarios, not valuations. 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 | yes | – |
| scenarios | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| attributions | array | yes | – |
| county | string | yes | – |
| deltas | array | yes | – |
| disclaimer | string | – | – |
| fully_comparable | boolean | yes | – |
| scenarios | array | yes | – |
No examples provided.
wa_comps Comparable sales with a chart for a pricing conversation ~543
Find recorded home sales around an address (radius), inside a drawn neighborhood outline (polygon of [latitude, longitude] points) or in a ZIP code, over the last 1-36 months, filtered by beds, baths, living sq ft, year built, price and property type. Returns each sale (address, date, price, price per sq ft, size, distance; no owner, buyer or seller names), median and quartile price and price per sq ft, a half-over-half trend, a price band when subjectSqft is given (or known from the county record), chart-ready series (chart.points, chart.monthly_median) and chart.image_url, a signed SVG chart an agent can open, save and show a seller. Use it for 'what did 3 bed homes near this street sell for in the last year' or 'what should we list at'. Show the chart (draw it from the series, or link chart.image_url) and quote the numbers exactly. King, Pierce and Snohomish county assessor records only; Snohomish has year built and property class but no size or bedrooms, and its dates are sale months. King condominium units may lack size and location. Statistics are not an appraisal. A miss is not charged. 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 |
|---|---|---|---|
| address | string | – | Subject or center address; comps are searched within radiusMiles of it. |
| bathsMin | – | – | – |
| bedsMax | – | – | – |
| bedsMin | – | – | – |
| city | – | – | – |
| county | – | – | Limit to one county. Recorded sales cover king, pierce and snohomish only; any other county returns a not-covered answer. |
| latitude | – | – | – |
| limit | integer | – | – |
| longitude | – | – | – |
| months | integer | – | How many months back to include (default 12, up to 36). |
| polygon | – | – | Neighborhood outline as [latitude, longitude] points (3-60). |
| priceMax | – | – | – |
| priceMin | – | – | – |
| propertyTypes | – | – | – |
| radiusMiles | number | – | Search radius around the address or point (default 0.5). |
| sqftMax | – | – | – |
| sqftMin | – | – | – |
| subjectSqft | – | – | Living sq ft of the home being priced, for the price band. |
| yearBuiltMax | – | – | – |
| yearBuiltMin | – | – | – |
| zipCode | – | – | With an address, helps place it. Alone, searches the whole ZIP. |
| Name | Type | Req | Description |
|---|---|---|---|
| area | – | yes | – |
| attributions | array | – | – |
| chart | – | – | – |
| disclaimer | string | – | – |
| excluded | object | – | – |
| fetched_at | string | – | – |
| filters | object | yes | – |
| has_more | boolean | – | – |
| price_band | – | – | – |
| sales | array | – | – |
| sources | array | – | – |
| stats | – | – | – |
| stats_disclaimer | string | – | – |
| status | string | yes | – |
| warnings | array | – | – |
| window_end | string | yes | – |
| window_start | string | yes | – |
No examples provided.
wa_local_context Housing, transit and school program context ~202
Get aggregate Census housing tenure estimates and margins of error by ZIP/ZCTA, nearby published Metro boarding stops by coordinate, and factual OSPI language programs by county, district or exact four-digit schoolCode. Combined school filters must all match. Sources have independent coverage, timestamps and required attributions. Does not determine school attendance, quality, neighborhood suitability or walking time. Supply a geography, schoolCode or supported research identifier; latitude and longitude must be paired.
| Name | Type | Req | Description |
|---|---|---|---|
| businessUbi | – | – | Exact Washington Unified Business Identifier for official registry handoff |
| county | – | – | – |
| latitude | – | – | – |
| limit | integer | – | – |
| longitude | – | – | – |
| parcelNumber | – | – | Complete ten-digit King County PIN; requires county=King |
| schoolCode | – | – | Exact four-digit OSPI school code, preserving leading zeros; filters reported language programs, not attendance eligibility. |
| schoolDistrict | – | – | – |
| transitRadiusM | integer | – | – |
| zipCode | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| census_housing | – | yes | – |
| disclaimer | string | – | – |
| disclosure_resources | array | yes | – |
| query | – | yes | – |
| school_programs | – | yes | – |
| transit | – | yes | – |
No examples provided.
wa_market_snapshot Washington market snapshot ~247
Latest Redfin market snapshot for a Washington area — ZIP code, neighborhood, city, or county: median sale price, year-over-year change, days on market, months of supply, and percent sold above list, with an explicit data-freshness period. Western Washington focus. Aggregate statistics only — no individual listings, parcels, or people. Use for 'how is the market in X' questions; quote the returned numbers verbatim and reproduce the Redfin attribution (required) wherever the numbers are shown. Paused while Sentinel arranges a licensed sale-statistics source: it then answers SOURCE_UNAVAILABLE, uncharged. For recorded sale prices use wa_comps (King, Pierce and Snohomish); for price-index and other trends use wa_market_trends. 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 |
|---|---|---|---|
| area | string | yes | Area name: a ZIP like '98103', a neighborhood, a city, or a county. |
| regionType | – | – | Optional hint: zip, neighborhood, city, or county. |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| disclaimer | string | yes | – |
| market | – | yes | – |
| source_attribution | string | yes | – |
No examples provided.
wa_market_trends Washington market trends (licensed sources) ~253
Monthly listing inventory from Realtor.com (median asking price, active, new and pending listings, median days on market, share with price cuts, pending ratio, each with the publisher's month-over-month and year-over-year change), FHFA House Price Index appreciation, Census building permits (new housing units authorized, month and year to date, for counties and cities), BLS county unemployment and Washington OFM population (counties and whole cities) for a Washington ZIP, county, city or metro. Every block names its publisher, period, file hash and required attribution. A median listing price is an asking price, not a sale price. Quote numbers verbatim with their period and reproduce each required attribution. Unknown areas are free. 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 |
|---|---|---|---|
| area | string | yes | A ZIP like '98052', a county like 'King County', a city like 'Kirkland', or a metro like 'Seattle-Tacoma-Bellevue'. |
| regionType | – | – | Optional hint: zip, county, city or metro. |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| city_permits | array | – | City queries: building permits for the matching permit-issuing place. |
| city_profiles | array | – | City queries: OFM April 1 population estimates for the whole city. |
| disclaimer | string | – | – |
| matched_as | string | yes | – |
| notices | array | yes | – |
| query | – | yes | – |
| regions | array | yes | – |
| truncated | boolean | – | – |
No examples provided.
wa_monthly_payment Estimate monthly housing payment ~212
Calculate a monthly mortgage and housing-cost estimate using the buyer's supplied price, down payment, loan term and interest rate. An entered rate is an assumption, not a live lender quote. Review every included cost. 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 |
|---|---|---|---|
| annualHomeInsurance | – | – | – |
| annualPropertyTax | – | – | – |
| downPayment | – | – | – |
| downPaymentPct | – | – | Percent, e.g. 20 means 20%; omit both down-payment fields to assume 20%. |
| interestRatePct | number | yes | User-supplied annual rate, e.g. 6.5 means 6.5%. |
| loanTermYears | integer | – | – |
| monthlyHoa | integer | – | – |
| pmiPct | number | – | – |
| propertyTaxRatePct | number | – | – |
| salePrice | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | – | yes | – |
| attributions | array | yes | – |
| disclaimer | string | – | – |
| down_payment | integer | yes | – |
| down_payment_pct | number | yes | – |
| interest_rate_pct | number | yes | – |
| loan_amount | integer | yes | – |
| loan_term_years | integer | yes | – |
| monthly_hoa | number | yes | – |
| monthly_home_insurance | number | yes | – |
| monthly_pmi | number | yes | – |
| monthly_property_tax | number | yes | – |
| piti_breakdown | – | yes | – |
| pmi_applies | boolean | yes | – |
| principal_interest | number | yes | – |
| sale_price | integer | yes | – |
| total_monthly_payment | number | 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_permit_history Property permit history and observed changes ~216
Read dated building-permit records for one exact property, including agency status, application/issue/completion dates, unit counts, project cost, zoning labels and observed changes. Connected sources are Seattle building permits, Everett permits and Pierce County PALS records; this is not complete city/county coverage. Other municipal sources return official lookup resources while commercial permission is unresolved. Use address or county plus parcelId. Match uses exact county/parcel or recorded street, unit and ZIP; no records does not prove no permits, and permit labels do not establish current development rights. Source update times may represent a bulk republish; distinguish source dates from observation time. 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 |
|---|---|---|---|
| address | string | – | – |
| city | – | – | – |
| county | – | – | – |
| limit | integer | – | – |
| parcelId | – | – | – |
| zipCode | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| coverage | – | yes | – |
| disclaimer | string | – | – |
| fetched_at | string | – | – |
| has_more | boolean | – | – |
| lookup_resources | array | – | – |
| observed_changes | array | – | – |
| property | – | yes | – |
| records | array | – | – |
| source_coverages | array | – | – |
| warnings | array | – | – |
No examples provided.
wa_property_changes Read captured permit history and observed changes ~227
Read immutable permit evidence for an exactly matched property. Supply since for changes after that capture time, or asOf for versions known by that time. Permit event dates are separate from Sentinel observation/capture times. Initial captures are baselines, not changes. History starts at first immutable capture and is incomplete; unavailable history is free. Use next_cursor with unchanged inputs to continue a bounded page. Never infer unpermitted work. 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 |
|---|---|---|---|
| address | string | – | – |
| asOf | – | – | Inclusive immutable capture time; defaults to the first page's time. Not a permit event date. |
| city | – | – | – |
| county | – | – | – |
| cursor | – | – | – |
| limit | integer | – | Maximum candidate versions inspected per page, including withheld records and initial baselines. |
| parcelId | – | – | – |
| since | – | – | Exclusive immutable capture time; supplied means changes mode. |
| zipCode | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| as_of_records | array | – | – |
| attributions | array | – | – |
| coverage | – | yes | – |
| mode | string | yes | – |
| next_cursor | – | – | – |
| observed_changes | array | – | – |
| permit_events | array | – | – |
| property | – | yes | – |
| since | – | yes | – |
| snapshot_at | string | yes | – |
| warnings | array | – | – |
No examples provided.
wa_property_lookup Washington county property record ~423
Look up one Washington property from already-ingested county assessor records (King, Pierce, Snohomish, Whatcom counties). Returns cached property facts with field-level source observations and explicit unverified, missing, withheld and stale states: physical attributes, assessed values, last recorded sale, ownership tenure, and a coverage_note naming any fields the county extract lacks. Listing status, list price and days on market are populated only when the matched listing row came from a licensed listing provider (fields: listing_status, list_price, dom, listed_date, removed_date, listing_source, listing_status_source, listing_fetched_at, listing_attribution). When the only match is a scraped portal row, or no listing matched, all of them are null — which is the usual case today. Read a null as 'no licensed listing on file for this address', not as 'this home is not for sale', and do not infer a status or a price from the county fields. Owner identity fields (owner or taxpayer names, mailing addresses, owner-status classification) and equity estimates are not included in this version. Listing links, listing photos and portal automated valuations are not returned. Per-address queries only (RCW 42.56.070(8)); no area enumeration. Use a specific WA street address or county plus parcelId; a NOT_FOUND error means the address is outside covered counties or not in the ingested rows — say so rather than guessing. 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 |
|---|---|---|---|
| address | string | – | Street address, e.g. '456 CEDAR CT'. |
| city | – | – | Optional city to disambiguate. |
| county | – | – | Optional county filter: king, pierce, snohomish, or whatcom. |
| parcelId | – | – | Exact county parcel ID; county is required. May replace address. |
| zipCode | – | – | Optional 5-digit ZIP to disambiguate. |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| disclaimer | string | yes | – |
| property | – | yes | – |
| served_at | string | – | Response generation time, distinct from source_as_of and listing_fetched_at. |
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.
wa_research_packet Research a Washington property with cited evidence ~172
Get a bounded property research packet with exact identity matching, source-backed facts, explicit calculations, conflicts, unknowns and follow-up questions. Compact and full projections retain identical claims, references and required notices. Optional coordinate context is a separate point observation, never an inferred parcel match. Preserve every qualification. Unavailable or ambiguous research is free; useful partial evidence counts as one answer. 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 |
|---|---|---|---|
| includePermits | boolean | – | – |
| local | – | – | – |
| permitLimit | integer | – | – |
| projection | string | – | – |
| property | – | yes | – |
| sellerScenarios | – | – | – |
| site | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| calculations | array | – | – |
| conflicts | array | – | – |
| details_omitted | boolean | – | – |
| facts | array | – | – |
| generated_at | string | yes | – |
| identity | – | yes | – |
| limitations | array | yes | – |
| packet_version | string | – | – |
| projection | string | yes | – |
| questions | array | – | – |
| references | array | – | – |
| sections | array | – | – |
| source_details | – | – | Full projection only. Claim evidence, caveats and notices are identical in compact responses. |
| status | string | yes | – |
| unknowns | array | – | – |
No examples provided.
wa_sale_history Recorded sale history for one property ~215
Read recorded sale dates and prices for one exact King, Pierce or Snohomish County parcel, from the county assessor's own published sale records (up to the last three years). Each record gives the parcel count, the county's market-validity code and whether it can serve as a comparable sale; multi-parcel, nominal and unverified prices are flagged, not hidden. No buyer, seller or owner names. Use address or county plus parcelId. A miss is not an answer and is not charged; missing records do not prove that no sale occurred, and a sale price is not a current value. 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 |
|---|---|---|---|
| address | string | – | – |
| city | – | – | – |
| county | – | – | – |
| days | integer | – | – |
| limit | integer | – | – |
| parcelId | – | – | – |
| zipCode | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| disclaimer | string | – | – |
| fetched_at | string | – | – |
| has_more | boolean | – | – |
| property | – | yes | – |
| records | array | – | – |
| source_coverages | array | – | – |
| status | string | yes | – |
| warnings | array | – | – |
| window_end | string | yes | – |
| window_start | string | yes | – |
No examples provided.
wa_seller_packet Build a Washington seller decision packet ~172
Prepare one seller briefing that combines proposed sale-price scenarios with available county property records and dated market context (licensed listing and price-index trends when sale-price snapshots are paused). Includes assumptions, missing information and source attributions. Missing or old data must remain visible; supplied prices are scenarios, not a CMA or appraisal. 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 | yes | – |
| deadlines | – | – | – |
| includePermits | boolean | – | Include dated permit evidence for the supplied property; currently City of Seattle building permits. |
| market | – | – | – |
| monthlyPayment | – | – | – |
| property | – | – | – |
| scenarios | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | yes | – |
| deadlines | – | – | – |
| disclaimer | string | – | – |
| gaps | array | yes | – |
| generated_at | string | yes | – |
| market | – | – | – |
| market_trends | – | – | Licensed market trends (FHFA price index, Census building permits, BLS unemployment, OFM population and, when enabled, Realtor.com listing inventory), used when sale-price market snapshots are unavai… |
| monthly_payment | – | – | – |
| packet_version | string | – | – |
| permits | – | – | – |
| property | – | – | – |
| report_markdown | string | yes | – |
| scenarios | – | yes | – |
| sections | array | yes | – |
| status | string | yes | – |
No examples provided.
wa_site_context Official environmental site context ~130
Query FEMA flood mapping, WGS landslide study coverage and inventory, liquefaction, mapped faults within 5 km, and an official Ecology cleanup lookup link. Cleanup site observations require documented commercial reuse permission. Supply a verified coordinate; results describe a point, not an entire parcel or structure. Each source declares unavailable/outside-study/no-mapped-feature states, observation times and required attributions. No absence claim establishes safety, disclosure compliance or insurance requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Caller-supplied latitude in Washington's bounding box; no address match is implied. |
| longitude | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attributions | array | – | – |
| disclaimer | string | – | – |
| expires_at | string | yes | – |
| limitations | array | – | – |
| location | – | yes | – |
| location_method | string | – | – |
| observations | object | yes | – |
| pierce_regulatory | – | – | – |
| retrieved_at | string | yes | – |
| schema_version | string | – | – |
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, 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'
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).
Is the SENTINEL Washington Real Estate MCP server safe to use?
SENTINEL Washington Real Estate scores 78 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 17 tools: wa_research_packet, wa_property_changes, wa_local_context, wa_market_trends, wa_site_context, and 12 more. Their descriptions and schemas cost roughly 3,967 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.