_ registry / mcp streamable-http · checked 53m ago

multifamily-deals

https://multifamily.deals

Registry code: 60282691808aaadc

api record

Contract Clock (multifamily.deals) answers questions about HUD project-based Section 8 and assistance contracts (HAP, PRAC, RAC, PAC, COOP) on apartment properties: which contracts reach their overall or current expiration in a date window, which HAP contracts pay under Fair Market Rent, one property with all its contracts, and counts by state. The data is HUD's Multifamily Assistance & Section 8 Database (https://www.hud.gov/hud-partners/multifamily-assist-section8-database); every result gives the file's as-of date and the HUD link, so cite them. The overall expiration date is the end of…

endpoint
https://multifamily.deals/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 multifamily-deals live?
Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
Is multifamily-deals free to use?
Yes — the hub reached it with no key and no payment.
What tools does multifamily-deals have?
4 tools: screen_below_fmr, get_property, expiring_contracts, state_contract_summary.
Is multifamily-deals 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
243ms

last good check

priced tools
0

of 4 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 4 tools
1 open 3 never probed 1 of 4 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.

  • state_contract_summary open 53m ago

    Deal-screen counts for one state, or every state ranked: properties, active contracts and assisted units, contracts reaching final (overall) expiration within two years of the HUD file date with their assisted units, and HAP contracts paying under 90% of Fair Market Rent. Omit state for the national ranking.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 30,
          "minimum": 1,
          "description": "States to list in the ranking, 1 to 30 (default 15)."
        },
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Two-letter state code, e.g. CA. Omit for all states."
        },
        "rank_by": {
          "enum": [
            "expiring",
            "below_fmr",
            "assisted_units"
          ],
          "type": "string",
          "default": "expiring",
          "description": "National ranking order (ignored with \"state\")."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • screen_below_fmr unknown never probed

    The deal screen's rent test for one state: active Section 8 HAP contracts whose rent-to-FMR ratio in HUD's file is above zero and under a threshold (default 90%), with property, assisted units, ratio, both expiration dates and a prefilled offer-calculator link. Optional filters: county, city, minimum assisted units, overall expiration within N months.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Optional city name, e.g. \"Cleveland\"."
        },
        "sort": {
          "enum": [
            "rent_to_fmr",
            "assisted_units",
            "expiration"
          ],
          "type": "string",
          "default": "rent_to_fmr",
          "description": "Lowest ratio first (default), largest first, or soonest overall expiration first."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "Rows to return, 1 to 20 (default 10); page with offset for more."
        },
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Two-letter state or territory code, e.g. OH."
        },
        "county": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Optional county name as HUD spells it, e.g. \"Cuyahoga\"."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 100000,
          "minimum": 0,
          "description": "Rows to skip, for paging."
        },
        "max_rent_to_fmr": {
          "type": "number",
          "default": 90,
          "maximum": 150,
          "minimum": 1,
          "description": "Keep contracts whose rent-to-FMR ratio is under this percent (default 90, the deal screen's line)."
        },
        "min_assisted_units": {
          "type": "integer",
          "maximum": 5000,
          "minimum": 0,
          "description": "Optional minimum assisted units (the state page table uses 20)."
        },
        "expiring_within_months": {
          "type": "integer",
          "maximum": 120,
          "minimum": 1,
          "description": "Optional: only contracts whose overall expiration falls within this many months of the HUD file date."
        }
      },
      "additionalProperties": false
    }
    arguments 69 lines
  • get_property unknown 53m ago

    One HUD Section 8 or assistance property with every contract on it: address, county, total units, HUD property category and financing type, FHA number, and per contract the number, program, status, effective date, both expiration dates, term, assisted units and rent-to-FMR ratio. Look up by contract number, HUD property ID, or property name within a state.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Optional city, to narrow a name search."
        },
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 3,
          "description": "Property name or part of it, e.g. \"Carvel Gardens\" (needs \"state\")."
        },
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Two-letter state code. Optional with a contract number."
        },
        "property_id": {
          "type": "integer",
          "maximum": 9999999999,
          "minimum": 1,
          "description": "HUD property ID, e.g. 800003809 (needs \"state\")."
        },
        "contract_number": {
          "type": "string",
          "pattern": "^[A-Za-z0-9]{11}$",
          "description": "HUD contract number, 11 characters, e.g. DE26M000010."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • expiring_contracts unknown 53m ago

    Active HUD project-based Section 8 and assistance contracts (HAP, PRAC, RAC, PAC) in one state whose overall or current expiration date falls in a date window, with property name, city, county, assisted units, program, both expiration dates, rent-to-FMR ratio and FHA number. Filter by county, city, contract type and size; page through results.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Optional city name, e.g. \"Cleveland\"."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional window start, YYYY-MM-DD (default: the HUD file's as-of date)."
        },
        "sort": {
          "enum": [
            "date",
            "assisted_units"
          ],
          "type": "string",
          "default": "date",
          "description": "Soonest first (default) or largest first."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "Rows to return, 1 to 20 (default 10); page with offset for more."
        },
        "state": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Two-letter state or territory code, e.g. OH."
        },
        "county": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Optional county name as HUD spells it, e.g. \"Cuyahoga\"."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 100000,
          "minimum": 0,
          "description": "Rows to skip, for paging."
        },
        "through": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional window end, YYYY-MM-DD."
        },
        "date_field": {
          "enum": [
            "overall",
            "current"
          ],
          "type": "string",
          "default": "overall",
          "description": "\"overall\" = end of the contract term (default); \"current\" = end of the currently funded piece, which is often renewed."
        },
        "contract_type": {
          "enum": [
            "HAP",
            "PRAC",
            "RAC",
            "PAC",
            "COOP"
          ],
          "type": "string",
          "description": "Optional HUD contract document type."
        },
        "within_months": {
          "type": "integer",
          "default": 24,
          "maximum": 120,
          "minimum": 1,
          "description": "Window length in months, measured from the HUD file's as-of date (default 24, as on the deal screen). Ignored when \"through\" is given."
        },
        "min_assisted_units": {
          "type": "integer",
          "maximum": 5000,
          "minimum": 0,
          "description": "Optional minimum assisted units on the contract."
        }
      },
      "additionalProperties": false
    }
    arguments 92 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 60282691808aaadc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/60282691808aaadc/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/60282691808aaadc/badge.svg)](https://brick.blue/agent/60282691808aaadc?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
80%

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.