Ffiec Call Reports
NPM · @PIPEWORX/MCP-FFIEC-CALL-REPORTS · 2 COMPONENTS
FFIEC Call Reports MCP — US bank line-item detail (fleet #338).
Available components
Last scanned (8 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-ffiec-call-reports). 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1280 tokens (~256/item across 5 items; 5 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 Management20
- Stability observed for 6 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 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.
- 2 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.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 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-ffiec-call-reports@0.2.2
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-ffiec-call-reports |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ffiec-call-reports/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635942367 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:31af21f0265fbedfad5ff7f7a9b229826aee04bbbe0e0765c6c5347f1f3274313012bd78144fdbb80f7d9f4b877965590f23ac644155b9f5cfc3b5d11 |
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 →
ffiec_call_report ~295
Get a US bank's filed call report for one quarter — the balance sheet, income statement, regulatory capital, loan and deposit detail as actually reported, with every line item labeled rather than left as a raw code. Answers "show me JPMorgan's call report", "what did this bank report last quarter", "total assets and equity for bank X". Identify the bank by name, FDIC certificate number, or Federal Reserve IDRSSD — the response states which one it resolved on. Pass `schedule` (RC, RI, RCRI, RCN, RCCI, RCE, RCK) to narrow to one schedule. Example: ffiec_call_report({ name: "jpmorgan chase bank" }); ffiec_call_report({ cert: 628, schedule: "RI" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | number | – | FDIC certificate number (as used by the fdic pack) |
| idrssd | number | – | Federal Reserve IDRSSD (as used by the CDR) |
| limit | number | – | Max line items (default 150, max 600) |
| name | string | – | Bank name (fuzzy) |
| quarter | string | – | Quarter end as YYYY-MM-DD; defaults to the latest quarter available |
| schedule | string | – | Restrict to one schedule: RC, RI, RCRI, RCN, RCCI, RCE, RCK |
No output schema declared.
No examples provided.
ffiec_compare_banks ~285
Compare or rank US banks on a call report figure — largest by assets, most deposits, highest net income — optionally within one state. Answers "largest banks in Ohio", "compare JPMorgan and Bank of America", "which banks have the most deposits". Pass `names`/`certs` to compare a specific set, or omit them to rank the whole industry. Amounts are in whole US dollars, normalised from the thousands banks file in, so figures line up with the ncua pack for credit unions. Example: ffiec_compare_banks({ metric: "total_assets", state: "OH", limit: 10 }); ffiec_compare_banks({ names: ["jpmorgan chase bank", "bank of america"] }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| certs | array | – | Specific banks to compare, by FDIC certificate number |
| limit | number | – | Max results when ranking (default 20, max 100) |
| metric | string | – | total_assets (default), total_loans, total_deposits, total_equity, net_income, past_due_90, or a raw MDRM code |
| names | array | – | Specific banks to compare, by name |
| quarter | string | – | Quarter end as YYYY-MM-DD; defaults to latest |
| state | string | – | Restrict a ranking to one state |
No output schema declared.
No examples provided.
ffiec_coverage ~191
Report what FFIEC call report data is available here — which quarters are loaded, how many banks and line items each holds, which schedules are covered, and the filing lag between a quarter ending and its data being published. Answers "what call report data do you have", "how current is this", "which quarters can I compare". Use before a trend question to see the window. Also resolves an MDRM code or searches for one by description. Example: ffiec_coverage({}); ffiec_coverage({ code: "RCFD2170" }); ffiec_coverage({ query: "total deposits" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | An MDRM code to explain, e.g. "RCFD2170" |
| limit | number | – | Max search results (default 15) |
| query | string | – | Search line item descriptions, e.g. "total deposits" |
No output schema declared.
No examples provided.
ffiec_line_item ~254
Track one US bank call report line item over time — total assets, net income, deposits, equity, or any MDRM code. Answers "how have this bank's deposits changed", "net income trend for bank X", "what is RCFD2170 for this bank over the last two years". Pass a friendly metric (total_assets, total_loans, total_deposits, total_equity, net_income, past_due_90) or a raw MDRM code. Amounts are returned in whole US dollars, normalised from the thousands the call report is filed in. Example: ffiec_line_item({ name: "jpmorgan chase bank", metric: "total_assets" }); ffiec_line_item({ cert: 628, metric: "RIAD4340" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| cert | number | – | FDIC certificate number |
| idrssd | number | – | Federal Reserve IDRSSD |
| metric | string | – | total_assets, total_loans, total_deposits, total_equity, net_income, past_due_90 — or a raw MDRM code like "RCFD2170" |
| name | string | – | Bank name (fuzzy) |
No output schema declared.
No examples provided.
ffiec_search_banks ~196
Find US banks and savings institutions that file the FFIEC Call Report, by name, city or state. Returns the bank's Federal Reserve IDRSSD, its FDIC certificate number, location, which call report form it files (031/041/051), and total assets. Answers "banks in Austin Texas", "is there a bank called Zions", "list Ohio banks". Name matching is fuzzy, so partial names work. Example: ffiec_search_banks({ name: "jpmorgan" }); ffiec_search_banks({ state: "OH", limit: 25 }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name |
| limit | number | – | Max results (default 20, max 100) |
| name | string | – | Full or partial bank name, e.g. "jpmorgan" |
| state | string | – | Two-letter state code, e.g. "TX" |
No output schema declared.
No examples provided.
How do I install the Ffiec Call Reports MCP server?
Ffiec Call Reports runs locally as an npm package, launched with npx -y @pipeworx/mcp-ffiec-call-reports. 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-ffiec-call-reports
claude mcp add pipeworx-io-ffiec-call-reports -- npx -y @pipeworx/mcp-ffiec-call-reports
What is the Ffiec Call Reports MCP server?
Ffiec Call Reports is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ffiec-call-reports. FFIEC Call Reports MCP, US bank line-item detail (fleet #338). This page covers its npm package (@pipeworx/mcp-ffiec-call-reports).
Is the Ffiec Call Reports MCP server safe to use?
Ffiec Call Reports 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 Ffiec Call Reports MCP server expose?
Ffiec Call Reports exposes 5 tools: ffiec_search_banks, ffiec_call_report, ffiec_line_item, ffiec_compare_banks, ffiec_coverage. Their descriptions and schemas cost roughly 1,221 tokens of context every time the server is loaded.
Is the Ffiec Call Reports MCP server still maintained?
Ffiec Call Reports 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 Ffiec Call Reports MCP server under?
Ffiec Call Reports declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.