LIHTC Atlas: income limits, QCT/DDA and LIHTC properties
REMOTE · LIHTC.LOANS
LIHTC data: HUD income and rent limits, 2027 QCT/DDA checks, LIHTC properties, credit math.
Available components
Last scanned (6 hours ago)
Scores higher than 54% 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1573 tokens (~157/item across 10 items; 10 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 67
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.loans/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lihtc.loans | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 74dd52eda2906aa40e1648ea95aed3e3 |
| SANs: lihtc.loans | ||||||
| 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.loans. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| loans. | present | 19444, 42307 | 8, 8 | Verified |
| lihtc.loans. | 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://lihtc.loans/mcp | Verified | 200 | |
| http (plaintext) | http://lihtc.loans/mcp | HTTPS enforced | 301 | https://lihtc.loans/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 →
calculate_credits LIHTC credit and equity estimate ~195
Annual and 10-year housing credits and equity from eligible basis, applicable fraction, credit type (4 or 9), the optional 130% basis boost and a credit price (default: the latest public median). Uses the statutory floor unless applicable_percentage is given. Same math as the lihtc.loans credit estimator.
| Name | Type | Req | Description |
|---|---|---|---|
| applicable_fraction | number | yes | Low-income share of the building, 0 to 1 (or a percent) |
| applicable_percentage | number | – | Override the rate, in percent (e.g. 3.53) when the floor does not apply |
| boost | boolean | – | 130% basis boost (QCT, DDA or state-designated) |
| credit_price | number | – | Equity per $1 of credit, e.g. 0.85 |
| credit_type | string | yes | 4 or 9 |
| eligible_basis | number | yes | Eligible basis in dollars |
No output schema declared.
No examples provided.
calculate_max_rent Maximum LIHTC rent ~211
Maximum LIHTC gross rent and tenant-paid rent for one unit: county, bedroom count and AMI level, less an optional utility allowance, from HUD FY2026 MTSP limits by the IRS Publication 5913 method, with the formula.
| Name | Type | Req | Description |
|---|---|---|---|
| ami_level | integer | yes | Percent of area median income |
| bedrooms | integer | yes | 0 for a studio |
| county | string | – | County name, e.g. "Harris County" or "Harris"; in New England, a town ("Boston"). Use fips when a name is ambiguous. |
| fips | string | – | 5-digit county FIPS (48201) or HUD's 10-digit area code (county + county subdivision, e.g. 2502507000 for Boston) |
| state | string | – | Two-letter state or territory code (CA, DC, PR) or name |
| utility_allowance | number | – | Monthly utility allowance for tenant-paid utilities, dollars (default 0) |
No output schema declared.
No examples provided.
check_qct_dda QCT and DDA check ~134
Is a site in a Qualified Census Tract or Difficult Development Area on HUD's 2027 lists (and any newer year HUD has posted)? Give a US street address (geocoded by the Census Bureau), or lat + lon, or an 11-digit 2020 census tract. Returns the tract, county, ZCTA and metro area and one result per list year.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address with city and state or ZIP |
| lat | number | – | – |
| lon | number | – | – |
| tract | string | – | 11-digit 2020 census tract GEOID |
No output schema declared.
No examples provided.
get_applicable_percentages IRS applicable percentages ~83
The monthly 70% (9%) and 30% (4%) present value credit rates from the IRS revenue ruling, the statutory 9% and 4% floors and the rate a deal uses. Defaults to the latest month, with the last 12.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | – | YYYY-MM, e.g. 2026-11 |
No output schema declared.
No examples provided.
get_equity_pricing LIHTC equity pricing ~49
Median net equity price per $1 of federal housing credit from CohnReznick's Housing Tax Credit Monitor, the series since late 2024, and current national fund pricing ranges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_financing_quote_link LIHTC financing quote link ~70
The page where a developer or owner can request a financing quote for a 4% or 9% deal (construction, tax-exempt bond, bridge, permanent, Year 15) from Janover Capital LLC, and what the desk handles. Returns a link only; it submits nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_income_limits LIHTC income and rent limits ~223
HUD FY2026 MTSP income limits for a county (town in New England): every level from 20% to 80% of area median for 1 to 8 persons, HERA Special limits where HUD lists them, the area median family income, and the maximum gross rent by bedroom count at each level (IRS Pub. 5913 method). Give state + county, or fips.
| Name | Type | Req | Description |
|---|---|---|---|
| ami_level | integer | – | Only this level (percent of AMI) |
| county | string | – | County name, e.g. "Harris County" or "Harris"; in New England, a town ("Boston"). Use fips when a name is ambiguous. |
| fips | string | – | 5-digit county FIPS (48201) or HUD's 10-digit area code (county + county subdivision, e.g. 2502507000 for Boston) |
| household_size | integer | – | Only this household size |
| state | string | – | Two-letter state or territory code (CA, DC, PR) or name |
No output schema declared.
No examples provided.
get_property Get one LIHTC property ~159
Everything HUD's LIHTC database lists for one property (units, income-restricted units, bedrooms, placed-in-service and allocation years, credit type, bonds, income test, targeting), its compliance and extended-use years, 2027 QCT/DDA status, its county's 2026 50% and 60% limits and rents, and nearby properties. Give the page url or the HUD project id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | HUD project id, e.g. ALA19940016 |
| state | string | – | Two-letter state or territory code (CA, DC, PR) or name |
| url | string | – | A lihtc.loans property page, /apartments/<state>/<city>/<property>/ |
No output schema declared.
No examples provided.
get_state_lihtc State LIHTC facts ~93
One state's allocating agency and LIHTC page, current Qualified Allocation Plan, state credit, 2026 9% credit ceiling and private activity bond cap (with the per-capita or minimum basis and population), and its count of 2027 QCTs and nonmetro DDA counties.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter state or territory code (CA, DC, PR) or name |
No output schema declared.
No examples provided.
search_properties Search LIHTC properties ~128
HUD-listed LIHTC properties still monitored for compliance, in one state, optionally one city and a name or street fragment, largest first. Each result has its lihtc.loans page URL and HUD project id for get_property. Covers cities with 5 or more monitored properties.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name as HUD lists it, e.g. "Los Angeles" |
| limit | integer | – | – |
| name | string | – | Words from the property name or street address |
| state | string | yes | Two-letter state or territory code (CA, DC, PR) or name |
No output schema declared.
No examples provided.
How do I install the LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server?
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties is a hosted endpoint at https://lihtc.loans/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.loans
claude mcp add --transport http loans-lihtc-lihtc-loans 'https://lihtc.loans/mcp'
What is the LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server?
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties is an MCP server listed in the public MCP registry as loans.lihtc/lihtc-loans. LIHTC data: HUD income and rent limits, 2027 QCT/DDA checks, LIHTC properties, credit math. This page covers its hosted endpoint (https://lihtc.loans/mcp).
Is the LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server safe to use?
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties scores 69 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 LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server expose?
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties exposes 10 tools: get_income_limits, calculate_max_rent, check_qct_dda, search_properties, get_property, and 5 more. Their descriptions and schemas cost roughly 1,345 tokens of context every time the server is loaded.
Does the LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server require authentication?
No. We connected to LIHTC Atlas: income limits, QCT/DDA and LIHTC properties without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LIHTC Atlas: income limits, QCT/DDA and LIHTC properties MCP server still maintained?
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties 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.