# 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.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `lihtc.loan`: 71/100 (this document), [markdown](https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc.md), [page](https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc)

## Channel facts

- Endpoint: `https://lihtc.loan/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2026.1101.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http loan-lihtc-lihtc-loan 'https://lihtc.loan/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "loan-lihtc-lihtc-loan": {
      "url": "https://lihtc.loan/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "loan-lihtc-lihtc-loan": {
      "type": "http",
      "url": "https://lihtc.loan/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.loan-lihtc-lihtc-loan]
url = "https://lihtc.loan/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "loan-lihtc-lihtc-loan": {
      "type": "remote",
      "url": "https://lihtc.loan/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add loan-lihtc-lihtc-loan --url 'https://lihtc.loan/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  loan-lihtc-lihtc-loan:
    url: "https://lihtc.loan/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "loan-lihtc-lihtc-loan": {
      "Transport": "http",
      "Url": "https://lihtc.loan/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add loan-lihtc-lihtc-loan -t streamable-http -u 'https://lihtc.loan/mcp'
```

### Other

```json
{
  "mcpServers": {
    "loan-lihtc-lihtc-loan": {
      "type": "http",
      "url": "https://lihtc.loan/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +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.

### 2026-11-03 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 69)

First indexed and scored.

## MCP tools (4)

### `find_year15_properties` (~229 tokens)

LIHTC properties reaching Year 15 in a state

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.

Input parameters:

- `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, required): Two-letter state or territory code, e.g. TX.

### `get_property` (~113 tokens)

One LIHTC property and its Year 15 dates

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.

Input parameters:

- `hud_id` (string, required): HUD project id (HUD_ID): three letters and eight digits, e.g. AKA20090010. Find ids with find_year15_properties.

### `year15_summary` (~93 tokens)

How many LIHTC properties reach Year 15, by year

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).

Input parameters:

- `state` (string): Two-letter state or territory code, e.g. CA. Omit for the national totals.

### `year15_exit_options` (~170 tokens)

Year 15 exit options and key dates

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.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69

## Common questions

### 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.

## Links

- Remote endpoint: https://lihtc.loan/mcp
- Website: https://lihtc.loan/developers/
- Changelog RSS feed: https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc.xml
- Changelog JSON feed: https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc.json
- HTML version of this page: https://verifymcp.io/servers/loan-lihtc-lihtc-loan/lihtc