_ registry / mcp streamable-http · checked 3h ago

sentinel-wa-realestate

https://app.sentineliq.net

Registry code: 583b7fa3e49e1674

api record

Sentinel answers Washington real estate questions with public-record sources. The calculators wa_reet, wa_net_sheet and nwmls_deadlines work without an account. Every other tool needs one: Claude and ChatGPT can sign in here; any other agent should send the user to https://sentineliq.net/mcp for a free 7-day trial (no card) and then call with the header Authorization: Bearer <key>. After the trial, Sentinel Connect is $29 a month. Use supplied prices as scenarios, not property valuations, and keep source dates, missing-data notes and attributions in answers.

endpoint
https://app.sentineliq.net/api/v1/mcp/public
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is sentinel-wa-realestate live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is sentinel-wa-realestate free to use?
Yes — the hub reached it with no key and no payment.
What tools does sentinel-wa-realestate have?
3 tools: wa_reet, nwmls_deadlines, wa_net_sheet.
Is sentinel-wa-realestate safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 98.9%· all time 98.9%

latency
186ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 269 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • compute washington transaction deadlines
  • estimate home seller net proceeds
  • calculate washington real estate excise tax
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • wa_reet reads unknown 17h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "AgentApiReetRequest",
      "required": [
        "salePrice"
      ],
      "properties": {
        "county": {
          "enum": [
            "clark",
            "cowlitz",
            "island",
            "king",
            "kitsap",
            "lewis",
            "mason",
            "pierce",
            "skagit",
            "snohomish",
            "whatcom"
          ],
          "type": "string",
          "title": "County",
          "default": "king",
          "maxLength": 40,
          "minLength": 1,
          "description": "Washington county the property sits in (lowercase)."
        },
        "salePrice": {
          "type": "integer",
          "title": "Sale Price",
          "description": "Contract sale price in whole US dollars.",
          "exclusiveMaximum": 500000000,
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • nwmls_deadlines reads unknown 17h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "AgentApiDeadlinesRequest",
      "required": [
        "mutualAcceptance"
      ],
      "properties": {
        "closing": {
          "anyOf": [
            {
              "type": "string",
              "format": "date"
            },
            {
              "type": "null"
            }
          ],
          "title": "Closing",
          "default": null,
          "description": "Optional contract closing date (on/after mutual acceptance), ISO YYYY-MM-DD."
        },
        "financingDays": {
          "type": "integer",
          "title": "Financing Days",
          "default": 21,
          "maximum": 120,
          "minimum": 1,
          "description": "Form 22A financing-contingency length."
        },
        "mutualAcceptance": {
          "type": "string",
          "title": "Mutual Acceptance",
          "format": "date",
          "description": "Mutual acceptance date, ISO YYYY-MM-DD (within 5 years of today)."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • wa_net_sheet reads unknown 17h ago

    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.

    mcp-tool

    {
      "type": "object",
      "title": "AgentApiNetSheetRequest",
      "required": [
        "salePrice"
      ],
      "properties": {
        "county": {
          "enum": [
            "clark",
            "cowlitz",
            "island",
            "king",
            "kitsap",
            "lewis",
            "mason",
            "pierce",
            "skagit",
            "snohomish",
            "whatcom"
          ],
          "type": "string",
          "title": "County",
          "default": "king",
          "maxLength": 40,
          "minLength": 1,
          "description": "Washington county the property sits in (lowercase)."
        },
        "hasHoa": {
          "type": "boolean",
          "title": "Has Hoa",
          "default": false,
          "description": "Include HOA transfer/resale-cert fees."
        },
        "salePrice": {
          "type": "integer",
          "title": "Sale Price",
          "description": "Contract sale price in whole US dollars.",
          "exclusiveMaximum": 500000000,
          "exclusiveMinimum": 0
        },
        "commissionRate": {
          "type": "number",
          "title": "Commission Rate",
          "default": 0.05,
          "maximum": 0.15,
          "minimum": 0,
          "description": "Total commission as a decimal fraction (0.05 = 5%). Defaults to the NWMLS-typical rate."
        },
        "mortgageBalance": {
          "type": "integer",
          "title": "Mortgage Balance",
          "default": 0,
          "minimum": 0,
          "description": "Outstanding mortgage payoff in dollars.",
          "exclusiveMaximum": 500000000
        },
        "propertyTaxProration": {
          "type": "integer",
          "title": "Property Tax Proration",
          "default": 0,
          "minimum": 0,
          "description": "Seller-side property-tax proration, dollars.",
          "exclusiveMaximum": 500000000
        }
      },
      "additionalProperties": false
    }
    arguments 68 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 583b7fa3e49e1674.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/583b7fa3e49e1674/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/583b7fa3e49e1674/badge.svg)](https://brick.blue/agent/583b7fa3e49e1674?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.