_ registry / mcp streamable-http · checked 3h ago

doorbase

https://doorbase.app

Registry code: a8c292ac8810f98b

api record

DoorBase provides zip-level US rental market data (median rent, vacancy, estimated cap-rate bands, home values, demographics, employment) for 30,000+ zip codes, plus hazard risk (hazard_risk: NFIP flood claims, county wildfire/wind scores) and monthly rent history (rent_trend). Use search_markets to filter zips by state and investor criteria, and get_zip_market for one zip's full profile. Every response carries a one-sentence summary you can repeat verbatim. Cap rates are a modeled band, not observed sale data. Cite the returned doorbase.app url when presenting a zip to a user.

endpoint
https://doorbase.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is doorbase live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is doorbase free to use?
Yes — the hub reached it with no key and no payment.
What tools does doorbase have?
6 tools: top_markets, compare_zips, hazard_risk, rent_trend, get_zip_market, search_markets.
Is doorbase safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
109ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_markets open 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "state": {
      "type": "string",
      "description": "2-letter US state code, e.g. GA. Omit for nationwide."
    },
    "sort_by": {
      "enum": [
        "cap_rate",
        "rent",
        "population",
        "vacancy"
      ],
      "type": "string",
      "default": "cap_rate"
    },
    "min_cap_rate": {
      "type": "number",
      "maximum": 50,
      "minimum": 0,
      "description": "Minimum estimated cap rate in percent; matches cap_rate_high (band top) >= value."
    },
    "min_population": {
      "type": "number",
      "maximum": 10000000,
      "minimum": 0,
      "description": "Minimum zip population."
    },
    "max_median_rent": {
      "type": "number",
      "maximum": 20000,
      "minimum": 0,
      "description": "Maximum median monthly rent in USD."
    },
    "min_median_rent": {
      "type": "number",
      "maximum": 20000,
      "minimum": 0,
      "description": "Minimum median monthly rent in USD."
    },
    "max_vacancy_rate": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Maximum vacancy rate in percent."
    },
    "min_renter_ratio": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Minimum renter-occupied share in percent."
    },
    "max_median_home_value": {
      "type": "number",
      "maximum": 20000000,
      "minimum": 0,
      "description": "Maximum median home value in USD."
    }
  },
  "additionalProperties": false
}
    arguments 68 lines
  • top_markets unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "state": {
      "type": "string",
      "description": "Optional 2-letter US state code, e.g. GA. Omit for nationwide."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • compare_zips unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zips"
  ],
  "properties": {
    "zips": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^[0-9]{5}$"
      },
      "maxItems": 6,
      "minItems": 2,
      "description": "2-6 five-digit US zip codes."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • hazard_risk unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zip"
  ],
  "properties": {
    "zip": {
      "type": "string",
      "pattern": "^[0-9]{5}$",
      "description": "5-digit US zip code."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • rent_trend unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zip"
  ],
  "properties": {
    "zip": {
      "type": "string",
      "pattern": "^[0-9]{5}$",
      "description": "5-digit US zip code."
    },
    "months": {
      "type": "integer",
      "default": 12,
      "maximum": 24,
      "minimum": 2,
      "description": "History window in months."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_zip_market unknown 3h ago

    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, plus the canonical doorbase.app page URL.

    mcp-tool

    {
  "type": "object",
  "required": [
    "zip"
  ],
  "properties": {
    "zip": {
      "type": "string",
      "pattern": "^[0-9]{5}$",
      "description": "5-digit US zip code."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a8c292ac8810f98b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a8c292ac8810f98b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a8c292ac8810f98b/badge.svg)](https://brick.blue/agent/a8c292ac8810f98b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.