Skip to content

dealcheck: US property deal-check MCP server

dev.workers.daderader.dealcheck/dealcheckdealcheck.daderader.workers.devstreamable-httpv0.2.0Scanned

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

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the dealcheck: US property deal-check MCP server can do

The dealcheck: US property deal-check MCP server is published by dealcheck.daderader.workers.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: ziplot_deal_check, nashville_deal_check and ziplot_deal_picture), but cannot delete data. None of its tools only reads.

3 tools bring in text other people can write (ziplot_deal_check, nashville_deal_check and ziplot_deal_picture).

The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • nashville_deal_checkDeprecated: use ziplot_deal_check.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,742 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ppears when side lookups such as permit counts or building lists were incomplete."

      What this check looks for
    Description, as the server wrote it
    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 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • ziplot_deal_checkPublic-record due-diligence facts for a US residential address.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,654 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ppears when side lookups such as permit counts or building lists were incomplete."

      What this check looks for
    Description, as the server wrote it
    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 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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • ziplot_deal_pictureSame 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 r…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dealcheck.daderader.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including ziplot_deal_check (write), nashville_deal_check (write), ziplot_deal_picture (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

2 info
  • The description is 2,654 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ppears when side lookups such as permit counts or building lists were incomplete."

    What this check looks for
  • The description is 2,742 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ppears when side lookups such as permit counts or building lists were incomplete."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  3. Tools2 added, 1 changed.+2 added~1 changedView diff

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dealcheck https://dealcheck.daderader.workers.dev/mcp
claude mcp add --transport http dealcheck https://dealcheck.daderader.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__dealcheck__ziplot_deal_check",
      "mcp__dealcheck__nashville_deal_check",
      "mcp__dealcheck__ziplot_deal_picture"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dealcheck. Review it before you use it.

Capability tags behind 3 rules
  • mcp__dealcheck__ziplot_deal_check untrusted-input
  • mcp__dealcheck__nashville_deal_check untrusted-input
  • mcp__dealcheck__ziplot_deal_picture untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.daderader.dealcheck/dealcheck/verify?hash=8bb13b14cb303bc518a7e9137043f92d7127c3ab434eec7ef943603bef1c3b74" | jq -e '.changed == false'

Pinned hash 8bb13b14cb30, from Nov 15, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.daderader.dealcheck/dealcheck/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.daderader.dealcheck/dealcheck
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.daderader.dealcheck/dealcheck.svg)](https://radar.anlyon.com/servers/dev.workers.daderader.dealcheck/dealcheck)

Source: MCP Registry. Synced Oct 21, 2026, 19:17 UTC.

dealcheck: US property deal-check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the dealcheck: US property deal-check MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the dealcheck: US property deal-check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the dealcheck: US property deal-check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the dealcheck: US property deal-check MCP server have?

3 tools: 3 write. ziplot_deal_check, nashville_deal_check and ziplot_deal_picture.

Does the dealcheck: US property deal-check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the dealcheck: US property deal-check MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the dealcheck: US property deal-check MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.