Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DealScanner

REMOTE · MCP.DEALSCANNER.IO

Search real-estate deals, rank top areas, run rental/BRRRR/flip analysis, pull sold comps.

0 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 668 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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://mcp.dealscanner.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dealscanner.io CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 39eb4b95d92bf40411afa1ac9b4e9290
SANs: dealscanner.io, *.dealscanner.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dealscanner.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
dealscanner.io. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dealscanner.io/mcp Verified 200
http (plaintext) http://mcp.dealscanner.io/mcp Inconclusive 406
MCP tools · 7 exposed · ~668 tokens

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 →

Tool Tokens
analyze_brrrr ~100

Run a BRRRR (buy-rehab-rent-refinance-repeat) analysis. Provide either `address` to analyze an existing listing, or the raw inputs (`purchase_price`, `rehab_cost`, `arv`, `monthly_rent`) for an ad-hoc deal.

NameTypeReqDescription
address–––
arv–––
monthly_rent–––
purchase_price–––
rehab_cost–––

No output schema declared.

No examples provided.

area_stats ~92

Get aggregated market, sheriff, sold, and investment stats for one area. Args: name: Neighborhood or municipality name (e.g. "Point Breeze North"). area_type: "neighborhood" or "municipality". Returns counts, median prices, average cap rate, and sold-comp metrics for the area.

NameTypeReqDescription
area_typestring––
namestringyes–

No output schema declared.

No examples provided.

get_comps ~53

Get recently sold comparable properties. Args: query: Address or area substring to match. limit: Max results (1-100).

NameTypeReqDescription
limitinteger––
querystring––

No output schema declared.

No examples provided.

get_property ~61

Get the full DealScanner analysis for one property by street address. Args: address: Full property address. strategy: "flip", "rental", or "brrrr".

NameTypeReqDescription
addressstringyes–
strategystring––

No output schema declared.

No examples provided.

search_deals ~189

Search DealScanner investment properties. Args: query: Address, municipality, or neighborhood text to match. strategy: Investment lens - one of "flip", "rental", "brrrr". min_price / max_price: Listing price bounds (USD). beds / baths: Minimum bedroom / bathroom count. property_class: Comma-separated neighborhood grades (A,B,C,D). source: "market" (listed) or "sheriff" (auction). limit: Max results (1-100). Returns a dict with `results`, `total`, and pagination info.

NameTypeReqDescription
baths–––
beds–––
limitinteger––
max_price–––
min_price–––
property_class–––
querystring––
sourcestring––
strategystring––

No output schema declared.

No examples provided.

top_investment_areas ~152

Rank the best areas to invest (neighborhoods + municipalities). Answers "where should I invest?" using DealScanner's market intelligence. Args: sort_by: Ranking metric - one of "cap_rate" (avg cap rate), "roi"/"flip_watch" (projected flip ROI), "count" (inventory), or "price" (lowest median price first). limit: Number of areas to return (1-50). Returns a dict with `areas` (name, type, cap_rate, roi, count, median_price, ...) sorted by the chosen metric.

NameTypeReqDescription
limitinteger––
sort_bystring––

No output schema declared.

No examples provided.

whoami ~21

Return the identity and scopes of the current DealScanner API principal.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the DealScanner MCP server?

DealScanner is a hosted endpoint at https://mcp.dealscanner.io/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 · mcp.dealscanner.io

# add to Claude Code
claude mcp add --transport http io-dealscanner-dealscanner 'https://mcp.dealscanner.io/mcp'
Common questions

What is the DealScanner MCP server?

DealScanner is an MCP server listed in the public MCP registry as io.dealscanner/dealscanner. Search real-estate deals, rank top areas, run rental/BRRRR/flip analysis, pull sold comps. This page covers its hosted endpoint (https://mcp.dealscanner.io/mcp).

Is the DealScanner MCP server safe to use?

DealScanner 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 DealScanner MCP server expose?

DealScanner exposes 7 tools: search_deals, get_property, analyze_brrrr, get_comps, top_investment_areas, and 2 more. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.

Does the DealScanner MCP server require authentication?

No. We connected to DealScanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DealScanner MCP server still maintained?

DealScanner 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 DealScanner MCP server?

VerifyMCP ran 11 checks on DealScanner, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about DealScanner: Authorization and HTTPS. 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.