Route 232: HUD Section 232 programs, queue and timing
REMOTE · FHAASSISTEDLIVING.LOAN
HUD Section 232 program chooser, weekly ORCF queue, closing times and note rates.
Available components
Last scanned (39 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1056 tokens (~264/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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- 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://fhaassistedliving.loan/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fhaassistedliving.loan | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2b8984dfeb0ab8d5132bb9c9e8679864 |
| SANs: fhaassistedliving.loan | ||||||
| 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 fhaassistedliving.loan. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| loan. | present | 61084 | 8 | Verified |
| fhaassistedliving.loan. | 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://fhaassistedliving.loan/mcp | Verified | 200 | |
| http (plaintext) | http://fhaassistedliving.loan/mcp | HTTPS enforced | 301 | https://fhaassistedliving.loan/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 →
estimate_232_timeline How long a HUD 232 loan takes ~208
How long a HUD Section 232 loan takes, from HUD's own closing records: for 223(f), median and middle-half days from firm application to underwriter assignment, firm commitment and closing, with estimated dates from a firm application date you give; for 223(a)(7), new construction and 241(a), firm-commitment-to-closing medians by fiscal year.
| Name | Type | Req | Description |
|---|---|---|---|
| firm_application_date | string | – | Date the lender submits (or submitted) the firm application, YYYY-MM-DD. Optional; with it, the steps come back as dates. |
| from_fiscal_year | integer | – | First fiscal year of firm-commitment-to-closing history to return (default 2023, earliest 2011). |
| program | string | yes | 223f (refinance or purchase), 223a7 (streamlined refinance of an FHA loan), new-construction (new construction or substantial rehab) or 241a (supplemental loan). |
No output schema declared.
No examples provided.
get_closing_stats HUD 232 closing rates and volumes ~155
Note rates on HUD Section 232 loans at closing from HUD's fiscal-year closings file (count, median and middle half, by program, and month by month for 223(f)), plus the number of loans HUD endorsed each fiscal year since 2016 for the program. Historical rates, not a quote.
| Name | Type | Req | Description |
|---|---|---|---|
| by_month | boolean | – | For 223f, include the month-by-month note rates (months with 3 or more loans). |
| program | string | – | Default 223f. 223f (refinance or purchase), 223a7 (streamlined refinance of an FHA loan), new-construction (new construction or substantial rehab) or 241a (supplemental loan). |
No output schema declared.
No examples provided.
get_queue_times HUD Section 232 queue this week ~130
HUD ORCF's weekly Section 232 underwriting queue report, summarized: how many 223(f), 223(a)(7) and new construction/241(a) applications are waiting, Express Lane counts, median and oldest days waiting, how long this week's underwriter assignments waited, the fiscal-year median wait, and optionally every saved weekly snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| include_history | boolean | – | Also return the saved weekly snapshots, newest first. |
| limit | integer | – | Weeks of history to return (default 10, max 50). |
| offset | integer | – | Weeks of history to skip, for paging. |
No output schema declared.
No examples provided.
which_232_program Which HUD Section 232 loan fits ~324
Answers which HUD Section 232 program fits an assisted living, memory care or nursing home (223(f), 223(a)(7), new construction/substantial rehab or 241(a)) from the same questions as the Route 232 chooser, with eligibility warnings, and returns that program's published rules: who qualifies, loan limits, coverage, mortgage insurance and fees, required reports and the HUD median closing time. Pass "program" alone to get one program's rules.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | Only when has_fha_loan is true: a lower rate or payment, or money for improvements or an addition. |
| has_fha_loan | boolean | – | Does the building have an FHA-insured (HUD) loan today? |
| independent_living_over_25pct | boolean | – | Are more than a quarter of the beds independent living? |
| licensed_20_plus_beds | boolean | – | Licensed or regulated by the state, with 20 or more beds? |
| operating | boolean | – | Only when has_fha_loan is false: is the building open and operating (false = building new or gutting it)? |
| program | string | – | Skip the questions and return the rules of one program: 223f (refinance or purchase), 223a7 (streamlined refinance of an FHA loan), new-construction (new construction or substantial rehab) or 241a (s… |
| years_since_completion | number | – | Only when operating is true: years since the building was completed or last substantially rehabilitated. |
No output schema declared.
No examples provided.
How do I install the Route 232: HUD Section 232 programs, queue and timing MCP server?
Route 232: HUD Section 232 programs, queue and timing is a hosted endpoint at https://fhaassistedliving.loan/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 · fhaassistedliving.loan
claude mcp add --transport http loan-fhaassistedliving-fhaassistedliving-loan 'https://fhaassistedliving.loan/mcp'
What is the Route 232: HUD Section 232 programs, queue and timing MCP server?
Route 232: HUD Section 232 programs, queue and timing is an MCP server listed in the public MCP registry as loan.fhaassistedliving/fhaassistedliving-loan. HUD Section 232 program chooser, weekly ORCF queue, closing times and note rates. This page covers its hosted endpoint (https://fhaassistedliving.loan/mcp).
Is the Route 232: HUD Section 232 programs, queue and timing MCP server safe to use?
Route 232: HUD Section 232 programs, queue and timing 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 Route 232: HUD Section 232 programs, queue and timing MCP server expose?
Route 232: HUD Section 232 programs, queue and timing exposes 4 tools: which_232_program, get_queue_times, estimate_232_timeline, get_closing_stats. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.
Does the Route 232: HUD Section 232 programs, queue and timing MCP server require authentication?
No. We connected to Route 232: HUD Section 232 programs, queue and timing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Route 232: HUD Section 232 programs, queue and timing MCP server still maintained?
Route 232: HUD Section 232 programs, queue and timing 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.