dealcheck: US property deal-check
REMOTE · DEALCHECK.DADERADER.WORKERS.DEV
Any US address: flood, HUD rent, county tax. Parcel zoning/STR rules: Nashville, Denver, Scottsdale.
Available components
Last scanned (11 minutes ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability69
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2490 tokens (~498/item across 5 items; 3 tools + 2 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 Management50
- Stability observed for 15 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
- Structured output schemas are declared (67% 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nashville_deal_check” rewrote its description, which is the text the model reads security
- Tool “ziplot_deal_check” rewrote its description, which is the text the model reads security
- Tool coverage: 91% → 100% ▲ functional
- MCP protocol version: 2025-03-26 → 2025-06-18 functional
- “nashville_deal_check” reworded the description of “include” cosmetic
- “ziplot_deal_check” reworded the description of “include” cosmetic
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nashville_deal_check” rewrote its description, which is the text the model reads security
- Tool “ziplot_deal_check” rewrote its description, which is the text the model reads security
- Tool “ziplot_deal_picture” rewrote its description, which is the text the model reads security
- 1 Nov 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.
- 31 Oct 26 0
- Schema quality: 374 → 429 ▼ functional
- Tool coverage: 75% → 91% ▲ functional
- Tool “ziplot_deal_check” now declares an output schema ▲ functional
- First check of Tool coverage: 67 functional
- New tool “ziplot_deal_picture” functional
- Tool “ziplot_deal_check” changed its title: Ziplot deal check cosmetic
- 30 Oct 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nashville_deal_check” rewrote its description, which is the text the model reads security
- Tool “ziplot_deal_check” rewrote its description, which is the text the model reads security
- Schema quality: 685 → 374 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- New prompt “check_address” functional
- New resource “coverage” functional
- New resource “free-key” functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 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.
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 5 Nov 2026 · Probed https://dealcheck.daderader.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=daderader.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5fead5ae019206809a50b5e3c9a3af9dbeb |
| SANs: *.daderader.workers.dev, daderader.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dealcheck.daderader.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dealcheck.daderader.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://dealcheck.daderader.workers.dev/mcp | Inconclusive | 405 |
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 →
nashville_deal_check ~774
Deprecated: use ziplot_deal_check. Public-record due-diligence facts for a US residential address. Any US address: FEMA flood zone at the geocoded point, HUD FY2026 Small Area FMR (or area FMR) by bedrooms, and a property-tax estimate: official rates in Nashville (Metro rate), Denver (levy by tax district), Chicago (Cook County tax code) and Maricopa County cities (tax area code), elsewhere a rough county-level estimate from Census ACS, labeled as such. Zoning or address-level eligibility plus short-term-rental (STR) rules (coverage level "full"): Nashville / Davidson County, TN; Denver (City and County), CO; Scottsdale (city limits), AZ; Chicago (city limits), IL; New York City (five boroughs), NY; Austin (full- and limited-purpose city), TX; Boise (City of Boise and unincorporated Ada County), ID; Miami (City of Miami, Miami Beach, unincorporated Miami-Dade), FL; Orlando (City of Orlando and unincorporated Orange County), FL; San Diego (City of San Diego), CA. City-wide STR rules plus an address-level permit lookup ("partial"): Phoenix (city limits), AZ; Tempe (city limits), AZ. 59 more cities, counties and resort areas get STR rules and taxes only, with no zoning or per-address check ("rules_only"). The current market list with levels and verified dates: GET /v1/coverage; str.granularity in each answer says which applies. Elsewhere zoning/STR return not_covered. Every value carries a source and as-of date. HOA/deed restrictions are not checked. Informational only; not legal/tax/insurance/lending advice. Ziplot tool (original name kept for compatibility; ziplot_deal_check is the same tool). Status values. Top-level status: ok = every evaluated section answered; needs_review = partial answer, at least one section needs a person or a retry (read each section's status and the warnings); unavailable = no section could be answered (address not found, or every source failed); out_of_scope = no evaluated section applies at this address. Section status uses the same word…
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | US street address including city and state, e.g. '321 50th Ave N, Nashville, TN' |
| bedrooms | integer | – | For HUD rent benchmark. Defaults to 2. |
| include | array | – | Optional sections to return. Omit it (or send an empty list) for all five; 'zoning' adds the zoning lookup used by the STR section. |
| value | number | – | Optional purchase price or value in USD. Echoed in query.value. Where no Assessor value exists it drives property_tax.estimated_annual_tax; where one exists, the estimate at your value is in property… |
No output schema declared.
No examples provided.
ziplot_deal_check Ziplot deal check ~752
Public-record due-diligence facts for a US residential address. Any US address: FEMA flood zone at the geocoded point, HUD FY2026 Small Area FMR (or area FMR) by bedrooms, and a property-tax estimate: official rates in Nashville (Metro rate), Denver (levy by tax district), Chicago (Cook County tax code) and Maricopa County cities (tax area code), elsewhere a rough county-level estimate from Census ACS, labeled as such. Zoning or address-level eligibility plus short-term-rental (STR) rules (coverage level "full"): Nashville / Davidson County, TN; Denver (City and County), CO; Scottsdale (city limits), AZ; Chicago (city limits), IL; New York City (five boroughs), NY; Austin (full- and limited-purpose city), TX; Boise (City of Boise and unincorporated Ada County), ID; Miami (City of Miami, Miami Beach, unincorporated Miami-Dade), FL; Orlando (City of Orlando and unincorporated Orange County), FL; San Diego (City of San Diego), CA. City-wide STR rules plus an address-level permit lookup ("partial"): Phoenix (city limits), AZ; Tempe (city limits), AZ. 59 more cities, counties and resort areas get STR rules and taxes only, with no zoning or per-address check ("rules_only"). The current market list with levels and verified dates: GET /v1/coverage; str.granularity in each answer says which applies. Elsewhere zoning/STR return not_covered. Every value carries a source and as-of date. HOA/deed restrictions are not checked. Informational only; not legal/tax/insurance/lending advice. Same tool as nashville_deal_check. Status values. Top-level status: ok = every evaluated section answered; needs_review = partial answer, at least one section needs a person or a retry (read each section's status and the warnings); unavailable = no section could be answered (address not found, or every source failed); out_of_scope = no evaluated section applies at this address. Section status uses the same words plus not_covered (this area is not evaluated). str.status follows the two permit deter…
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | US street address including city and state, e.g. '321 50th Ave N, Nashville, TN' |
| bedrooms | integer | – | For HUD rent benchmark. Defaults to 2. |
| include | array | – | Optional sections to return. Omit it (or send an empty list) for all five; 'zoning' adds the zoning lookup used by the STR section. |
| value | number | – | Optional purchase price or value in USD. Echoed in query.value. Where no Assessor value exists it drives property_tax.estimated_annual_tax; where one exists, the estimate at your value is in property… |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| attribution | array | yes | – |
| coverage | object | – | – |
| disclaimer | string | yes | – |
| error | object | – | Present only when an upstream failed and the caller should retry (isError true). |
| flood | object | – | – |
| generated_at | string | yes | – |
| hint | string | – | On a not-found or retry answer: what to do next. Data sections are omitted then. |
| partial | object | – | Present when slow upstreams were cut off, or when the jurisdiction lookup did not answer; retry later for the full answer. |
| property_tax | object | – | – |
| query | object | yes | – |
| rent_benchmark | object | – | – |
| resolved | – | yes | – |
| status | string | yes | Roll-up status of the answer (see the tool description for each value). |
| status_reasons | array | – | – |
| str | object | – | – |
| verify_link | – | – | – |
| verify_link_note | string | – | – |
| verify_url | string | yes | – |
| warnings | array | yes | – |
No examples provided.
ziplot_deal_picture Ziplot deal picture ~700
Same public-record answer as ziplot_deal_check for a US address, plus a `deal` block: illustrative arithmetic on the inputs you give (monthly payment, monthly cash flow, NOI, cap rate, cash-on-cash, DSCR), with every input, its source (caller, default or deal-check), each assumption and each formula shown. price is required. rent defaults to the HUD Small Area FMR from deal-check and tax to the deal-check property-tax estimate at your price; rate and insurance have no default and their results are null until given. Defaults: 30-year term, 25% down, 3% closing costs, HOA 0, vacancy 8%, management 8% (an assumption; set 0 if you self-manage), maintenance 5%. Informational arithmetic on the inputs shown. Not financial, tax or legal advice. Status values. Top-level status: ok = every evaluated section answered; needs_review = partial answer, at least one section needs a person or a retry (read each section's status and the warnings); unavailable = no section could be answered (address not found, or every source failed); out_of_scope = no evaluated section applies at this address. Section status uses the same words plus not_covered (this area is not evaluated). str.status follows the two permit determinations: new_non_owner_occupied_permit.value (allowed, not_allowed, needs_review, out_of_scope, not_covered, unavailable) and owner_occupied_permit.value (possible, not_allowed, needs_review, out_of_scope, not_covered, unavailable). Both firm = ok, one firm and one not = needs_review, none usable = unavailable. Exception: an owner_occupied_permit of possible that rests only on an active city STR license (owner_occupied_permit.basis.kind active_city_license, Denver and Scottsdale) is not a firm yes, so str.status stays needs_review there. str.supporting_data_status appears when side lookups such as permit counts or building lists were incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | US street address including city and state, e.g. '321 50th Ave N, Nashville, TN' |
| bedrooms | integer | – | For the HUD rent benchmark. Defaults to 2. |
| closing_pct | number | – | Closing costs, percent of price. Default 3. |
| down_pct | number | – | Down payment, percent of price. Default 25. |
| hoa | number | – | Monthly HOA dues in USD. Default 0. |
| insurance | number | – | Annual insurance premium in USD. No default. |
| maintenance_pct | number | – | Maintenance allowance, percent of rent. Default 5. |
| management_pct | number | – | Management fee, percent of rent. Default 8 (assumption; 0 if self-managed). |
| price | number | yes | Purchase price in USD (required). |
| rate | number | – | Annual mortgage interest rate in percent, e.g. 6.5. No default. |
| rent | number | – | Monthly rent in USD. Default: HUD Small Area FMR from deal-check. |
| tax | number | – | Annual property tax in USD. Default: deal-check estimate at your price. |
| term_years | integer | – | Loan term in years. Default 30. |
| vacancy_pct | number | – | Vacancy allowance, percent of rent. Default 8. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| attribution | array | yes | – |
| coverage | object | – | – |
| deal | object | – | Illustrative arithmetic on the inputs shown. Absent on a not-found or retry answer (isError true). |
| disclaimer | string | yes | – |
| error | object | – | Present only when an upstream failed and the caller should retry (isError true). |
| flood | object | – | – |
| generated_at | string | yes | – |
| hint | string | – | On a not-found or retry answer: what to do next. Data sections are omitted then. |
| partial | object | – | Present when slow upstreams were cut off, or when the jurisdiction lookup did not answer; retry later for the full answer. |
| property_tax | object | – | – |
| query | object | yes | – |
| rent_benchmark | object | – | – |
| resolved | – | yes | – |
| status | string | yes | Roll-up status of the answer (see the tool description for each value). |
| status_reasons | array | – | – |
| str | object | – | – |
| verify_link | – | – | – |
| verify_link_note | string | – | – |
| verify_url | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the dealcheck: US property deal-check MCP server?
dealcheck: US property deal-check is a hosted endpoint at https://dealcheck.daderader.workers.dev/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 · dealcheck.daderader.workers.dev
claude mcp add --transport http dev-workers-daderader-dealcheck-dealcheck 'https://dealcheck.daderader.workers.dev/mcp'
What is the dealcheck: US property deal-check MCP server?
dealcheck: US property deal-check is an MCP server listed in the public MCP registry as dev.workers.daderader.dealcheck/dealcheck. Any US address: flood, HUD rent, county tax. Parcel zoning/STR rules: Nashville, Denver, Scottsdale. This page covers its hosted endpoint (https://dealcheck.daderader.workers.dev/mcp).
Is the dealcheck: US property deal-check MCP server safe to use?
dealcheck: US property deal-check scores 71 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 dealcheck: US property deal-check MCP server expose?
dealcheck: US property deal-check exposes 3 tools: ziplot_deal_check, nashville_deal_check, ziplot_deal_picture. Their descriptions and schemas cost roughly 2,226 tokens of context every time the server is loaded.
Does the dealcheck: US property deal-check MCP server require authentication?
No. We connected to dealcheck: US property deal-check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dealcheck: US property deal-check MCP server still maintained?
dealcheck: US property deal-check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.