Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
LIHTC data: HUD income and rent limits, 2027 QCT/DDA checks, LIHTC properties, credit math.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lihtc-atlas-income-limits-qct-dda-and-lihtc-p-mcp https://lihtc.loans/mcp
# 2 — ask your agent for something these tools do
# get_income_limits, calculate_max_rent, check_qct_dda and 7 more
LIHTC Atlas: income limits, QCT/DDA and LIHTC properties costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LIAll 1 server
lihtc1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http lihtc-atlas-income-limits-qct-dda-and-lihtc-p-mcp https://lihtc.loans/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter state or territory code (CA, DC, PR) or name |
| county | string | no | County name, e.g. "Harris County" or "Harris"; in New England, a town ("Boston"). Use fips when a name is ambiguous. |
| fips | string | no | 5-digit county FIPS (48201) or HUD's 10-digit area code (county + county subdivision, e.g. 2502507000 for Boston) |
| household_size | integer | no | Only this household size |
| ami_level | integer | no | Only this level (percent of AMI) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | Two-letter state or territory code (CA, DC, PR) or name |
| county | string | no | County name, e.g. "Harris County" or "Harris"; in New England, a town ("Boston"). Use fips when a name is ambiguous. |
| fips | string | no | 5-digit county FIPS (48201) or HUD's 10-digit area code (county + county subdivision, e.g. 2502507000 for Boston) |
| bedrooms | integer | yes | 0 for a studio |
| ami_level | integer | yes | Percent of area median income |
| utility_allowance | number | no | Monthly utility allowance for tenant-paid utilities, dollars (default 0) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | Street address with city and state or ZIP |
| lat | number | no | — |
| lon | number | no | — |
| tract | string | no | 11-digit 2020 census tract GEOID |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter state or territory code (CA, DC, PR) or name |
| city | string | no | City name as HUD lists it, e.g. "Los Angeles" |
| name | string | no | Words from the property name or street address |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | A lihtc.loans property page, /apartments/<state>/<city>/<property>/ |
| id | string | no | HUD project id, e.g. ALA19940016 |
| state | string | no | Two-letter state or territory code (CA, DC, PR) or name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | Two-letter state or territory code (CA, DC, PR) or name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| month | string | no | YYYY-MM, e.g. 2026-11 |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| eligible_basis | number | yes | Eligible basis in dollars |
| applicable_fraction | number | yes | Low-income share of the building, 0 to 1 (or a percent) |
| credit_type | string | yes | 4 or 9 |
| boost | boolean | no | 130% basis boost (QCT, DDA or state-designated) |
| credit_price | number | no | Equity per $1 of credit, e.g. 0.85 |
| applicable_percentage | number | no | Override the rate, in percent (e.g. 3.53) when the floor does not apply |
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LIHTC Atlas: income limits, QCT/DDA and LIHTC properties or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.2026.1101.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestc3f72199deb470765f892786937afb6d0c8c73af0241a6e2f7cc7185890a63f8
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_income_limits | no tags | |
| calculate_max_rent | no tags | |
| check_qct_dda | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_properties | no tags | |
| get_property | no tags | |
| get_state_lihtc | no tags | |
| get_applicable_percentages | no tags | |
| get_equity_pricing | no tags | |
| calculate_credits | no tags | |
| get_financing_quote_link | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc3f72199deb47076
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2026.1101.0.
1.2026.1101.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LIHTC Atlas: income limits, QCT/DDA and LIHTC properties can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.