mcpbeat Sign in

dealcheck: US property deal-check MCP Server

by workers-daderader-dealcheck Your server? Claim it
answering

dealcheck: US property deal-check is answering right now. Last checked 8 min ago. It exposes 3 tools.

Any US address: flood, HUD rent, county tax. Parcel zoning/STR rules: Nashville, Denver, Scottsdale.

Uptime history 12 days of history · worst day 99%
12 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
399 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 October 2026. No other catalogue keeps this.

1 Nov 3 tool descriptions were rewritten nashville_deal_check, ziplot_deal_check, ziplot_deal_picture
30 Oct a tool appeared ziplot_deal_picture
29 Oct 2 tool descriptions were rewritten4 times that day nashville_deal_check, ziplot_deal_check
22 Oct 2 tool descriptions were rewritten4 times that day nashville_deal_check, ziplot_deal_check
22 Oct 2 tools changed the parameters they ask for nashville_deal_check, ziplot_deal_check
and 4 more, back to 22 October 2026

dealcheck: US property deal-check missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add dealcheck --transport http https://dealcheck.daderader.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://dealcheck.daderader.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.dealcheck]
url = "https://dealcheck.daderader.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dealcheck": {
      "url": "https://dealcheck.daderader.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "dealcheck": {
      "type": "http",
      "url": "https://dealcheck.daderader.workers.dev/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ziplot
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. Full parcel-level coverage (zoning district, overlays, STR permit eligibility for owner-occupied vs non-owner-occupied, caps, existing STR permits/licenses) only in Nashville/Davidson County TN, Denver CO, Scottsdale AZ, Chicago IL (building size, Prohibited Buildings List, Restricted Residential Zones), and Boise ID (City of Boise and unincorporated Ada County; zoning district plus Idaho Code 67-6539 state STR rules). New York City (city-wide rules plus a per-building Prohibited Buildings List and registration check by BIN) and Austin TX (city-wide rules plus a per-parcel full/limited-purpose/ETJ check) are also covered, as are Phoenix, Mesa, Tempe, and Tucson (city limits) AZ (city-wide rules); str.granularity says which. 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 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.
ziplot_deal_picture
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.
nashville
nashville_deal_check
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. Full parcel-level coverage (zoning district, overlays, STR permit eligibility for owner-occupied vs non-owner-occupied, caps, existing STR permits/licenses) only in Nashville/Davidson County TN, Denver CO, Scottsdale AZ, Chicago IL (building size, Prohibited Buildings List, Restricted Residential Zones), and Boise ID (City of Boise and unincorporated Ada County; zoning district plus Idaho Code 67-6539 state STR rules). New York City (city-wide rules plus a per-building Prohibited Buildings List and registration check by BIN) and Austin TX (city-wide rules plus a per-parcel full/limited-purpose/ETJ check) are also covered, as are Phoenix, Mesa, Tempe, and Tucson (city limits) AZ (city-wide rules); str.granularity says which. 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 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.

Endpoints

URLTransportStateLatencyChecked
https://dealcheck.daderader.workers.dev/mcp streamable-http answering 72 ms 8 min ago

Alternatives to dealcheck: US property deal-check

same job, measured the same way
Locus
by velinussage

Official US-address public records: zoning, flood, parcel, permits, taxes. Free look, x402 paid.

2 tools answering
King County Permit Status
by chaoz23

Live permit history + status for any King County, WA address, parcel or permit number. Read-only.

1 tools answering
Ceny Nieruchomosci MCP
by contentwriterco

Polish real-estate deed prices and parcel checks: zoning plan, utilities, flood risk

569 installs/wk 4 tools answering
US Flood Zone & Property Risk (FEMA, NOAA, USGS, Census)
by thestackunderflow

FEMA flood zone, hazard history and demographics for any US address, with sources on every answer.

6 tools answering
PLU IA
by azeria-it

French zoning (PLU) for any address or parcel in France, rules cited with the official PDF page.

answering
BatchData
by batchdataco

Real estate data for AI agents: property lookup, comps, search, skip tracing, phone/address checks

answering
A
Agent Risk Desk
by soldanoandrea

EVM address enrichment, counterparty risk and tx screening for agents, paid per call in USDC (x402)

7 tools answering
Atria
by askatria

US site diligence for agents: parcels, power, flood, zoning rules and more, each with its source.

answering

dealcheck: US property deal-check — questions

Answers built from our own checks of this server.

What can dealcheck: US property deal-check do?
It exposes 3 tools, read directly from the server on our last check. Among them: nashville_deal_check, ziplot_deal_check, ziplot_deal_picture. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is dealcheck: US property deal-check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 399 ms. The bar chart above shows every period we have measured.
How do I connect dealcheck: US property deal-check?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does dealcheck: US property deal-check need an API key?
No. dealcheck: US property deal-check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is dealcheck: US property deal-check?
It answers our handshake in 399 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.