Hmda
NPM · @PIPEWORX/MCP-HMDA · 2 COMPONENTS
HMDA — every US mortgage application at loan level (CFPB / FFIEC).
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hmda). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 862 tokens (~215/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 Management23
- Stability observed for 7 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 supported MCP spec version (2025-11-25); the latest is 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 · Analysed npm/@pipeworx/mcp-hmda@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-hmda |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hmda/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637392102 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2e8cd2e1140e286423d594a909cb095fab88290eddad60383f2eb8c35e3e3ebd7d2434acd3bbc443bc1f7f4072afb3ab57e5d19940af1601806a5f3b9 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
hmda_geography_activity ~227
Mortgage lending in a place — how many applications were originated, denied or withdrawn in a county or state in a given year, with dollar volume, from the federal HMDA register. Break the answer down by applicant race, ethnicity, sex, loan purpose or loan type to see how outcomes differ across groups, which is the fair-lending question this data exists to make answerable. Covers 2018-2025.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Optional outcome filter: originated | approved_not_accepted | denied | withdrawn | incomplete | purchased. Omit to see every outcome side by side. |
| breakdown | string | – | Optional dimension to split by: race | ethnicity | sex | loan_purpose | loan_type. |
| county | string | – | 5-digit county FIPS, e.g. "11001" for the District of Columbia. |
| state | string | – | Two-letter state, e.g. "TX". Give a county OR a state. |
| year | number | – | Filing year, 2018-2025. Defaults to the most recent published. |
No output schema declared.
No examples provided.
hmda_lender_activity ~202
What a specific mortgage lender did in a year — applications, originations, denials and dollar volume — from the federal Home Mortgage Disclosure Act register, optionally narrowed to a state or county. Identify the lender by its LEI (the 20-character Legal Entity Identifier HMDA files under); resolve_entity maps a company name to one. Covers every US mortgage application 2018-2025. Reports what lenders DISCLOSED, which is a regulatory filing rather than a market estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Optional 5-digit county FIPS, e.g. "06037" for Los Angeles. |
| lei | string | yes | 20-character Legal Entity Identifier, e.g. "549300FGXN1K3HLB1R50". |
| state | string | – | Optional two-letter state, e.g. "CA". |
| year | number | – | Filing year, 2018-2025. Defaults to the most recent published. |
No output schema declared.
No examples provided.
hmda_lenders_in_county ~184
Which lenders were most active in a county, ranked by loan count, from HMDA loan-level records for that county and year. Returns each lender LEI with its originations, denials and dollar volume, so "who lends here" and "who denies most here" are answerable. Bounded: it reads the county's records directly, so very large counties are sampled rather than fully ranked, and the response says so.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Outcome to rank on: originated | approved_not_accepted | denied | withdrawn | incomplete | purchased. Default originated. |
| county | string | yes | 5-digit county FIPS, e.g. "11001". |
| limit | number | – | Lenders to return (1-100, default 20). |
| year | number | – | Filing year, 2018-2025. |
No output schema declared.
No examples provided.
hmda_loan_records ~196
Individual mortgage application records from the HMDA register — the loan-level rows behind the totals, with loan amount, action taken, rate spread, applicant income, lender LEI and census tract. Use when an aggregate is not enough and the individual applications matter. Filtered by geography and outcome; a large county returns tens of thousands of rows, so this caps what it returns and says when it truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Outcome filter: originated | approved_not_accepted | denied | withdrawn | incomplete | purchased. |
| county | string | – | 5-digit county FIPS. Give a county OR a state. |
| lei | string | – | Optional lender LEI to narrow to one institution. |
| limit | number | – | Maximum records to return (1-500, default 50). |
| state | string | – | Two-letter state. |
| year | number | – | Filing year, 2018-2025. |
No output schema declared.
No examples provided.
How do I install the Hmda MCP server?
Hmda runs locally as an npm package, launched with npx -y @pipeworx/mcp-hmda. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-hmda
claude mcp add pipeworx-io-hmda -- npx -y @pipeworx/mcp-hmda
What is the Hmda MCP server?
Hmda is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hmda. HMDA, every US mortgage application at loan level (CFPB / FFIEC). This page covers its npm package (@pipeworx/mcp-hmda).
Is the Hmda MCP server safe to use?
Hmda scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Hmda MCP server expose?
Hmda exposes 4 tools: hmda_lender_activity, hmda_geography_activity, hmda_loan_records, hmda_lenders_in_county. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.
Is the Hmda MCP server still maintained?
Hmda 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 licence is the Hmda MCP server under?
Hmda declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.