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.

app.doorbase/market-data

REMOTE · DOORBASE.APP

US rental market data by zip: rent, cap rates, vacancy, hazard risk, rent trends. Free, no auth.

Available components

+10 this week 74 Trust /100

Last scanned (1 hour ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 808 tokens (~134/item across 6 items; 6 tools + 0 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +8
    • Authorization: unverified → partial ▲ security
    • Tool “get_zip_market” rewrote its description, which is the text the model reads security
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 62

    First indexed and scored.

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 5 Nov 2026 · Probed https://doorbase.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=doorbase.app CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 c9af9de5623635df0e882d321a95e8c5
SANs: doorbase.app
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 doorbase.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
doorbase.app. 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://doorbase.app/mcp Verified 200
http (plaintext) http://doorbase.app/mcp HTTPS enforced 301 https://doorbase.app/mcp
MCP tools · 6 exposed · ~674 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
compare_zips ~81

How do these zip codes compare as rental markets? Side-by-side comparison of 2-6 US zips: rent, cap-rate band (modeled), vacancy, home value, population, renter share, income, employment, with a doorbase.app link for each.

NameTypeReqDescription
zipsarrayyes2-6 five-digit US zip codes.

No output schema declared.

No examples provided.

get_zip_market ~96

What does the rental market look like in this zip code? Full profile for a single US zip: rent, cap-rate band (modeled), vacancy, home value, demographics, income, employment, the county's HMDA mortgage lending conditions (purchase/refinance denial rate, median rate and loan, loan-type mix), plus the canonical doorbase.app page URL.

NameTypeReqDescription
zipstringyes5-digit US zip code.

No output schema declared.

No examples provided.

hazard_risk ~89

What flood, wildfire, and wind risk does this zip code carry? NFIP flood-insurance claims on record (count, payouts, recency, claims per 1,000 housing units), FEMA National Risk Index county scores for flood, wildfire, and wind, and recent significant storm events. Claims are history, not a forecast.

NameTypeReqDescription
zipstringyes5-digit US zip code.

No output schema declared.

No examples provided.

rent_trend ~75

Which way is rent moving in this zip code? Monthly median-rent history with home values, the direction of movement, and the zip's national and state rank for 3-month rent growth. Updated monthly.

NameTypeReqDescription
monthsinteger–History window in months.
zipstringyes5-digit US zip code.

No output schema declared.

No examples provided.

search_markets ~239

Which US zip codes match these rental-market criteria? Filters 30,000+ US zip codes by state, cap rate, vacancy, rent, population, home value, and renter share. Returns matching zips with key investor metrics and a doorbase.app link for each. Cap rates are a modeled band; min_cap_rate matches the band's high end.

NameTypeReqDescription
limitinteger––
max_median_home_valuenumber–Maximum median home value in USD.
max_median_rentnumber–Maximum median monthly rent in USD.
max_vacancy_ratenumber–Maximum vacancy rate in percent.
min_cap_ratenumber–Minimum estimated cap rate in percent; matches cap_rate_high (band top) >= value.
min_median_rentnumber–Minimum median monthly rent in USD.
min_populationnumber–Minimum zip population.
min_renter_rationumber–Minimum renter-occupied share in percent.
sort_bystring––
statestring–2-letter US state code, e.g. GA. Omit for nationwide.

No output schema declared.

No examples provided.

top_markets ~94

Which US rental markets look strongest right now? National (or single-state) leaderboard: zips with the highest estimated cap-rate bands among markets with population of 10,000+ and complete rent, vacancy, and home-value data. Cap rates are a modeled band.

NameTypeReqDescription
limitinteger––
statestring–Optional 2-letter US state code, e.g. GA. Omit for nationwide.

No output schema declared.

No examples provided.

Install

How do I install the app.doorbase/market-data MCP server?

app.doorbase/market-data is a hosted endpoint at https://doorbase.app/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 · doorbase.app

# add to Claude Code
claude mcp add --transport http app-doorbase-market-data 'https://doorbase.app/mcp'
Common questions

What is the app.doorbase/market-data MCP server?

app.doorbase/market-data is an MCP server listed in the public MCP registry as app.doorbase/market-data. US rental market data by zip: rent, cap rates, vacancy, hazard risk, rent trends. Free, no auth. This page covers its hosted endpoint (https://doorbase.app/mcp).

Is the app.doorbase/market-data MCP server safe to use?

app.doorbase/market-data scores 74 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 app.doorbase/market-data MCP server expose?

app.doorbase/market-data exposes 6 tools: search_markets, get_zip_market, top_markets, compare_zips, hazard_risk, rent_trend. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.

Does the app.doorbase/market-data MCP server require authentication?

No. We connected to app.doorbase/market-data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the app.doorbase/market-data MCP server still maintained?

app.doorbase/market-data 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.