Contract Clock: HUD Section 8 contract expirations
REMOTE · MULTIFAMILY.DEALS
HUD Section 8 HAP contract expirations, below-FMR screen and property lookup by state.
Available components
Last scanned (8 minutes ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1218 tokens (~304/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 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.
- 3 Nov 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.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 68
First indexed and scored.
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://multifamily.deals/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=multifamily.deals | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4dbed501447ceec40e25146cad22af61 |
| SANs: multifamily.deals | ||||||
| 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 multifamily.deals. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| deals. | present | 58487 | 8 | Verified |
| multifamily.deals. | 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://multifamily.deals/mcp | Verified | 200 | |
| http (plaintext) | http://multifamily.deals/mcp | HTTPS enforced | 301 | https://multifamily.deals/mcp |
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 →
expiring_contracts Section 8 contracts expiring in a state ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city name, e.g. "Cleveland". |
| contract_type | string | – | Optional HUD contract document type. |
| county | string | – | Optional county name as HUD spells it, e.g. "Cuyahoga". |
| date_field | string | – | "overall" = end of the contract term (default); "current" = end of the currently funded piece, which is often renewed. |
| from | string | – | Optional window start, YYYY-MM-DD (default: the HUD file's as-of date). |
| limit | integer | – | Rows to return, 1 to 20 (default 10); page with offset for more. |
| min_assisted_units | integer | – | Optional minimum assisted units on the contract. |
| offset | integer | – | Rows to skip, for paging. |
| sort | string | – | Soonest first (default) or largest first. |
| state | string | yes | Two-letter state or territory code, e.g. OH. |
| through | string | – | Optional window end, YYYY-MM-DD. |
| within_months | integer | – | 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. |
No output schema declared.
No examples provided.
get_property Section 8 property and its contracts ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city, to narrow a name search. |
| contract_number | string | – | HUD contract number, 11 characters, e.g. DE26M000010. |
| name | string | – | Property name or part of it, e.g. "Carvel Gardens" (needs "state"). |
| property_id | integer | – | HUD property ID, e.g. 800003809 (needs "state"). |
| state | string | – | Two-letter state code. Optional with a contract number. |
No output schema declared.
No examples provided.
screen_below_fmr Section 8 HAP contracts paying under Fair Market Rent ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city name, e.g. "Cleveland". |
| county | string | – | Optional county name as HUD spells it, e.g. "Cuyahoga". |
| expiring_within_months | integer | – | Optional: only contracts whose overall expiration falls within this many months of the HUD file date. |
| limit | integer | – | Rows to return, 1 to 20 (default 10); page with offset for more. |
| max_rent_to_fmr | number | – | Keep contracts whose rent-to-FMR ratio is under this percent (default 90, the deal screen's line). |
| min_assisted_units | integer | – | Optional minimum assisted units (the state page table uses 20). |
| offset | integer | – | Rows to skip, for paging. |
| sort | string | – | Lowest ratio first (default), largest first, or soonest overall expiration first. |
| state | string | yes | Two-letter state or territory code, e.g. OH. |
No output schema declared.
No examples provided.
state_contract_summary Section 8 contract counts by state ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | States to list in the ranking, 1 to 30 (default 15). |
| rank_by | string | – | National ranking order (ignored with "state"). |
| state | string | – | Two-letter state code, e.g. CA. Omit for all states. |
No output schema declared.
No examples provided.
How do I install the Contract Clock: HUD Section 8 contract expirations MCP server?
Contract Clock: HUD Section 8 contract expirations is a hosted endpoint at https://multifamily.deals/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 · multifamily.deals
claude mcp add --transport http deals-multifamily-multifamily-deals 'https://multifamily.deals/mcp'
What is the Contract Clock: HUD Section 8 contract expirations MCP server?
Contract Clock: HUD Section 8 contract expirations is an MCP server listed in the public MCP registry as deals.multifamily/multifamily-deals. HUD Section 8 HAP contract expirations, below-FMR screen and property lookup by state. This page covers its hosted endpoint (https://multifamily.deals/mcp).
Is the Contract Clock: HUD Section 8 contract expirations MCP server safe to use?
Contract Clock: HUD Section 8 contract expirations scores 70 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 Contract Clock: HUD Section 8 contract expirations MCP server expose?
Contract Clock: HUD Section 8 contract expirations exposes 4 tools: expiring_contracts, screen_below_fmr, get_property, state_contract_summary. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.
Does the Contract Clock: HUD Section 8 contract expirations MCP server require authentication?
No. We connected to Contract Clock: HUD Section 8 contract expirations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Contract Clock: HUD Section 8 contract expirations MCP server still maintained?
Contract Clock: HUD Section 8 contract expirations 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.