Year Fifteen: LIHTC Year 15 properties and exits
REMOTE · LIHTC.LOAN
LIHTC properties reaching Year 15 by state and year, with dates and exit options.
Available components
Last scanned (15 hours ago)
Scores higher than 57% 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 837 tokens (~209/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 Management10
- Stability observed for 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 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.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 69
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://lihtc.loan/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lihtc.loan | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3808bef95130b2900eaf3f7e5711f818 |
| SANs: lihtc.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 lihtc.loan. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| loan. | DS published | 61084 | 8 | Verified |
| lihtc.loan. | No DS | 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://lihtc.loan/mcp | Verified | 200 | |
| http (plaintext) | http://lihtc.loan/mcp | HTTPS enforced | 301 | https://lihtc.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 →
find_year15_properties LIHTC properties reaching Year 15 in a state ~229
Lists tax credit properties in one state from HUD's LIHTC database (placed in service 2009 to 2018) with name, HUD id, city, units, low-income units, credit type and estimated compliance-period end year. Filter by end year (2023 to 2032), city, minimum units or credit type; returns the total matched and a page of rows.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City as HUD lists it, e.g. "Houston". |
| compliance_end_year | integer | – | Estimated year the 15-year compliance period ends (placed-in-service year + 14), e.g. 2027. |
| credit_type | string | – | Credit type decoded from HUD's CREDIT field. |
| limit | integer | – | Rows to return (default 10, max 50). Sorted by units, largest first. |
| min_units | integer | – | Only properties with at least this many total units. |
| offset | integer | – | Rows to skip, for paging. |
| state | string | yes | Two-letter state or territory code, e.g. TX. |
No output schema declared.
No examples provided.
get_property One LIHTC property and its Year 15 dates ~113
One tax credit property by HUD project id (e.g. TXA20120123): HUD's record (address, units, low-income units, placed-in-service and allocation years, credit type, monitoring flag) plus the estimated credit period, compliance-period end, qualified contract request date, right of first refusal date and minimum extended-use end.
| Name | Type | Req | Description |
|---|---|---|---|
| hud_id | string | yes | HUD project id (HUD_ID): three letters and eight digits, e.g. AKA20090010. Find ids with find_year15_properties. |
No output schema declared.
No examples provided.
year15_exit_options Year 15 exit options and key dates ~170
The five Year 15 paths for a LIHTC property (investor buyout, right of first refusal, sale, qualified contract, resyndication) with the statutory price rules as this site publishes them, and, given a placed-in-service year, the credit period, compliance end, qualified contract and right of first refusal dates and extended-use end.
| Name | Type | Req | Description |
|---|---|---|---|
| credits_start_next_year | boolean | – | True if the owner elected on Form 8609 to start credits the year after placed in service. |
| extended_use_end_year | integer | – | Extended use end year in the recorded agreement, if known and later than the federal minimum. |
| placed_in_service_year | integer | – | Year the building was placed in service, e.g. 2012. Omit for the exit paths only. |
No output schema declared.
No examples provided.
year15_summary How many LIHTC properties reach Year 15, by year ~93
Counts of tax credit properties, total units and low-income units whose estimated 15-year compliance periods end in each year from 2023 to 2032, for one state or the whole US, from HUD's LIHTC database (placed in service 2009 to 2018).
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Two-letter state or territory code, e.g. CA. Omit for the national totals. |
No output schema declared.
No examples provided.
How do I install the Year Fifteen: LIHTC Year 15 properties and exits MCP server?
Year Fifteen: LIHTC Year 15 properties and exits is a hosted endpoint at https://lihtc.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 · lihtc.loan
claude mcp add --transport http loan-lihtc-lihtc-loan 'https://lihtc.loan/mcp'
What is the Year Fifteen: LIHTC Year 15 properties and exits MCP server?
Year Fifteen: LIHTC Year 15 properties and exits is an MCP server listed in the public MCP registry as loan.lihtc/lihtc-loan. LIHTC properties reaching Year 15 by state and year, with dates and exit options. This page covers its hosted endpoint (https://lihtc.loan/mcp).
Is the Year Fifteen: LIHTC Year 15 properties and exits MCP server safe to use?
Year Fifteen: LIHTC Year 15 properties and exits scores 71 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 Year Fifteen: LIHTC Year 15 properties and exits MCP server expose?
Year Fifteen: LIHTC Year 15 properties and exits exposes 4 tools: find_year15_properties, get_property, year15_summary, year15_exit_options. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.
Does the Year Fifteen: LIHTC Year 15 properties and exits MCP server require authentication?
No. We connected to Year Fifteen: LIHTC Year 15 properties and exits without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Year Fifteen: LIHTC Year 15 properties and exits MCP server still maintained?
Year Fifteen: LIHTC Year 15 properties and exits 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.
What did VerifyMCP test on the Year Fifteen: LIHTC Year 15 properties and exits MCP server?
VerifyMCP ran 13 checks on Year Fifteen: LIHTC Year 15 properties and exits, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.