Banking Regulations
NPM · @PIPEWORX/MCP-BANKING-REGULATIONS · 2 COMPONENTS
Banking Regulations MCP — US banking & consumer-finance rules (12 CFR).
Available components
Last scanned (11 hours ago)
Scores higher than 69% 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-banking-regulations). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 902 tokens (~451/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 78
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-banking-regulations@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-banking-regulations |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-banking-regulations/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601383047 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9d9af858af96a7aefff25b581bbd22c81bf943ad38f8273089328e645b177d10851da869a4854082517fdeacef1b9f9c65e4ea08b2b492a2c4fa1cb56 |
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 →
banking_regulation ~550
Get the full text of one banking regulation — a US Federal Reserve, OCC, FDIC, CFPB or NCUA rule codified in 12 CFR — by its citation or Regulation letter. Returns the exact regulatory wording currently in force. Answers "what does Regulation E require", "what is the Federal Reserve regulation for X", "read 12 CFR 1026.19", "the CFPB rule on X", "the OCC / FDIC regulation for X", "bank capital requirement". Forgiving input: "1026.19", "12 CFR 1026.19", "§ 217.10", "1026.19(e)" (paragraph stripped to the section), "part 1026". Fed "Regulation letters" resolve automatically: "Regulation Z" (truth in lending) -> part 1026, "Reg B" (ECOA) -> 1002, "Reg C" (HMDA) -> 1003, "Reg D" -> 204, "Reg E" (EFTA) -> 1005, "Reg O" (insider lending) -> 215, "Reg W" (affiliate transactions) -> 223, "Reg X" (RESPA) -> 1024, "Reg Y" (bank holding companies) -> 225, "Reg CC" (funds availability) -> 229, "Reg DD" (truth in savings) -> 1030, "Reg Q" / capital -> 217, plus "Volcker rule" -> 248, "CRA" -> 228, "liquidity coverage ratio" -> 249. Covers bank compliance across all of Title 12: consumer financial protection, mortgage disclosure and servicing, deposits and payments, capital and liquidity, holding-company supervision, safety and soundness. Pass a whole part or Regulation letter to get that part's section list. Example: banking_regulation({ citation: "1026.19" }) -> certain mortgage and variable-rate transactions; banking_regulation({ citation: "Regulation Z" }) -> the truth-in-lending part's section list. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | Banking-regulation citation or Regulation letter. A section: "1026.19", "12 CFR 1026.19", "§ 217.10", "1002.9", "1026.19(e)". A Regulation letter or statute name: "Regulation Z", "Reg E", "truth in l… |
No output schema declared.
No examples provided.
banking_regulations_search ~297
Keyword search across the US banking regulations — Federal Reserve, OCC, FDIC, CFPB and NCUA rules in 12 CFR. Answers "what banking regulations cover X", "the Federal Reserve regulation about X", "find the CFPB rule for X", "which consumer financial protection rule applies to X", "the bank compliance requirement for X". Great for topics: truth in lending disclosure, mortgage origination and servicing, closing disclosures and TRID, ability to repay and qualified mortgages, electronic fund transfers and error resolution, overdraft and remittances, fair lending and adverse action notices, HMDA reporting, funds availability and check holds, deposit insurance, risk-based capital and leverage ratios, liquidity coverage, transactions with affiliates, insider lending limits, bank holding company activities, stress testing, community reinvestment. Returns matching banking rules with citation (12 CFR), heading, excerpt, and source URL. Example: banking_regulations_search({ query: "truth in lending disclosure" }); banking_regulations_search({ query: "ability to repay qualified mortgage", limit: 15 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, 1-20 (default 10). |
| query | string | yes | Banking-regulation topic or phrase, e.g. "truth in lending disclosure", "ability to repay", "overdraft", "capital conservation buffer", "adverse action notice", "funds availability". |
No output schema declared.
No examples provided.
How do I install the Banking Regulations MCP server?
Banking Regulations runs locally as an npm package, launched with npx -y @pipeworx/mcp-banking-regulations. 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-banking-regulations
claude mcp add pipeworx-io-banking-regulations -- npx -y @pipeworx/mcp-banking-regulations
What is the Banking Regulations MCP server?
Banking Regulations is an MCP server listed in the public MCP registry as io.github.pipeworx-io/banking-regulations. Banking Regulations MCP, US banking & consumer-finance rules (12 CFR). This page covers its npm package (@pipeworx/mcp-banking-regulations).
Is the Banking Regulations MCP server safe to use?
Banking Regulations scores 81 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 Banking Regulations MCP server expose?
Banking Regulations exposes 2 tools: banking_regulation, banking_regulations_search. Their descriptions and schemas cost roughly 847 tokens of context every time the server is loaded.
Is the Banking Regulations MCP server still maintained?
Banking Regulations 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 Banking Regulations MCP server under?
Banking Regulations declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.