Fed Nic
NPM · @PIPEWORX/MCP-FED-NIC · 2 COMPONENTS
Federal Reserve National Information Center (NIC, ffiec.gov/npw)
Available components
Last scanned (16 hours 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-fed-nic). 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1096 tokens (~274/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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- 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-fed-nic@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-fed-nic |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fed-nic/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635940738 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:77f83f063f3c60c3c9ed9aa41547b74c19db5e8a4ca04c19961e68cc9fe3d8bd944b4c5a7bb3f553791cc8f79a495e5765219bcc1326bf038b73eae7f |
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 →
nic_get_hierarchy ~339
Corporate ownership hierarchy for a bank or holding company, sourced from the Federal Reserve NIC (ffiec.gov/npw) Relationships data — "which holding company owns this bank?" / "list the subsidiaries of this BHC". direction="up" (default) walks the ownership chain to its top holder(s) — for a bank subsidiary this typically resolves to a single ultimate parent (e.g. a bank holding company). direction="down" lists entities OWNED BY the given RSSD ID; pass rssd_id of the TOP-TIER parent (found via direction="up") to get the full corporate family. total_subsidiary_count is a DISTINCT count computed in SQL (deduped by RSSD ID across multiple ownership paths to the same subsidiary) — it is always the true total, independent of `limit`/`offset`; use offset to page beyond the first `limit` rows. Coverage note: this is our own computed closure over NIC's public Relationships file, not necessarily identical to NIC's own web UI tiering figure — see pack README.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | "up" (ancestors/owners, default) or "down" (subsidiaries/descendants) |
| limit | number | – | For direction="down": max subsidiary rows to return, 1-200, default 50 (total_subsidiary_count is always the true distinct total, not the page size) |
| offset | number | – | For direction="down": pagination offset into total_subsidiary_count, default 0 |
| rssd_id | number | yes | NIC RSSD ID to start from |
No output schema declared.
No examples provided.
nic_get_history ~115
Merger, acquisition, failure and charter-transformation history for an institution, sourced from the Federal Reserve NIC (ffiec.gov/npw) Transformations data — "what predecessor institutions merged into this bank?" / "what happened to this bank?". Returns rows where the given RSSD ID is either predecessor (was absorbed/transformed) or successor (absorbed/received the other institution), each with the counterpart institution's name, RSSD ID and event date.
| Name | Type | Req | Description |
|---|---|---|---|
| rssd_id | number | yes | NIC RSSD ID |
No output schema declared.
No examples provided.
nic_get_institution ~291
Full NIC record for one institution — legal name, FDIC certificate, LEI, institution type, charter type, location, and active/closed status. Sourced from the Federal Reserve National Information Center (ffiec.gov/npw). Look it up by RSSD ID (NIC's own identifier), FDIC certificate number (the join key shared with the `fdic` pack), or LEI (the join key shared with the `gleif` pack) — provide exactly one. Use nic_search_institutions first to find an RSSD ID from a name.
| Name | Type | Req | Description |
|---|---|---|---|
| fdic_cert | number | – | FDIC certificate number — chains to the `fdic` pack (fdic_get_institution), e.g. 3511 for Wells Fargo Bank, N.A. Provide exactly one of rssd_id, fdic_cert, lei. |
| lei | string | – | Legal Entity Identifier (20-character LEI code) — chains to the `gleif` pack, e.g. "7H6GLXDRUGQFU57RNE97" for JPMorgan Chase Bank, N.A. Provide exactly one of rssd_id, fdic_cert, lei. |
| rssd_id | number | – | NIC RSSD ID, e.g. 852218 for JPMorgan Chase Bank, N.A. Provide exactly one of rssd_id, fdic_cert, lei. |
No output schema declared.
No examples provided.
nic_search_institutions ~297
Search US banks, bank holding companies, financial holding companies and their subsidiaries by name — sourced from the Federal Reserve National Information Center (NIC, ffiec.gov/npw), the Fed's own repository of bank structure data. Case-insensitive substring match on legal/short name, RANKED (not alphabetical): exact name match first, then a prefix match on an active institution with an FDIC certificate, then any prefix match, then other active FDIC-cert institutions, then the rest — so searching "Wells Fargo Bank" returns the main national bank ahead of same-family entities like an Ireland-domiciled affiliate with no FDIC cert. Returns RSSD ID (NIC's identifier), FDIC certificate number, LEI, institution type, city/state, and active/closed status — RSSD ID and FDIC cert chain to the `fdic` pack (fdic_get_institution) and `ffiec-call-reports` pack (idrssd) for financials on the same bank.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-50, default 20 |
| query | string | yes | Institution name, or part of it, e.g. "JPMorgan Chase Bank" |
| state | string | – | Optional 2-letter US state abbreviation filter, e.g. "OH" |
| status | string | – | Filter: "active" | "closed" | "any" (default "active") |
No output schema declared.
No examples provided.
How do I install the Fed Nic MCP server?
Fed Nic runs locally as an npm package, launched with npx -y @pipeworx/mcp-fed-nic. 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-fed-nic
claude mcp add pipeworx-io-fed-nic -- npx -y @pipeworx/mcp-fed-nic
What is the Fed Nic MCP server?
Fed Nic is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fed-nic. Federal Reserve National Information Center (NIC, ffiec.gov/npw). This page covers its npm package (@pipeworx/mcp-fed-nic).
Is the Fed Nic MCP server safe to use?
Fed Nic 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 Fed Nic MCP server expose?
Fed Nic exposes 4 tools: nic_search_institutions, nic_get_institution, nic_get_hierarchy, nic_get_history. Their descriptions and schemas cost roughly 1,042 tokens of context every time the server is loaded.
Is the Fed Nic MCP server still maintained?
Fed Nic 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 Fed Nic MCP server under?
Fed Nic declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Fed Nic MCP server?
VerifyMCP ran 16 checks on Fed Nic, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.