Ferc Elibrary
NPM · @PIPEWORX/MCP-FERC-ELIBRARY · 2 COMPONENTS
FERC eLibrary MCP — the Federal Energy Regulatory Commission's public docket and document search…
Available components
Last scanned (9 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-ferc-elibrary). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 664 tokens (~221/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 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.
- 1 Nov 26 +2
- 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
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → 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-ferc-elibrary@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-ferc-elibrary |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ferc-elibrary/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635942107 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bb7c94f3f4490d8baca0003af96f4b185598dca387a71d2a7fd01911d71fa361c31b58baf416f0e517dbebbcf51e79da66370c6cdb07ef70743b7b657 |
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 →
ferc_class_types ~141
Browse FERC eLibrary's document class/type/library vocabulary — what "category" and "class_types" values from ferc_docket/ferc_search mean (e.g. "Order/Opinion" / "Delegated Order", "Submittal" / "Affidavits/Sworn Statement"). Optionally filter by a search word. Use when a caller needs to know what document classification terms exist before filtering FERC results. Example: ferc_class_types({ search: "order" })
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional word to filter class/type/category names, e.g. "order", "brief", "affidavit" |
No output schema declared.
No examples provided.
ferc_docket ~212
Get all filings, orders, and correspondence for a FERC (Federal Energy Regulatory Commission) docket number — e.g. rate cases, interconnection agreements, tariff filings, orders on rehearing. Returns accession numbers, filed/issued/posted dates, document category and class/type, and the docket family (a docket query also surfaces related sub-dockets, e.g. "ER11-4046" pulling in "ER11-3872-029"). Use for "what has FERC filed/ordered in docket X", "history of docket Y", or "latest filing in case Z". Example: ferc_docket({ docket: "ER11-4046" })
| Name | Type | Req | Description |
|---|---|---|---|
| docket | string | yes | FERC docket number, e.g. "ER11-4046" or "CP20-1" |
| limit | number | – | Results per page, 1-50 (default 10) |
| page | number | – | Results page, starting at 1 (default 1) |
No output schema declared.
No examples provided.
ferc_search ~255
Full-text search across all FERC (Federal Energy Regulatory Commission) eLibrary filings and orders — not limited to one docket. Optionally bound to a filed-date window with since/until. Use for "FERC filings about X", "orders mentioning Y between date A and date B", or general keyword search across the public docket record when you do not already have a docket number (use ferc_docket if you do). Example: ferc_search({ query: "interconnection agreement", since: "2026-06-01", until: "2026-08-30", full_text: true })
| Name | Type | Req | Description |
|---|---|---|---|
| full_text | boolean | – | Search inside full document text, not just metadata/description (default false — faster, description-only) |
| limit | number | – | Results per page, 1-50 (default 10) |
| page | number | – | Results page, starting at 1 (default 1) |
| query | string | – | Search text; omit or pass "*" to match everything (combine with since/until to just browse a date window) |
| since | string | – | Earliest filed date, YYYY-MM-DD |
| until | string | – | Latest filed date, YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the Ferc Elibrary MCP server?
Ferc Elibrary runs locally as an npm package, launched with npx -y @pipeworx/mcp-ferc-elibrary. 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-ferc-elibrary
claude mcp add pipeworx-io-ferc-elibrary -- npx -y @pipeworx/mcp-ferc-elibrary
What is the Ferc Elibrary MCP server?
Ferc Elibrary is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ferc-elibrary. FERC eLibrary MCP, the Federal Energy Regulatory Commission's public docket and document search… This page covers its npm package (@pipeworx/mcp-ferc-elibrary).
Is the Ferc Elibrary MCP server safe to use?
Ferc Elibrary 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 Ferc Elibrary MCP server expose?
Ferc Elibrary exposes 3 tools: ferc_docket, ferc_search, ferc_class_types. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Is the Ferc Elibrary MCP server still maintained?
Ferc Elibrary 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 Ferc Elibrary MCP server under?
Ferc Elibrary 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 Ferc Elibrary MCP server?
VerifyMCP ran 15 checks on Ferc Elibrary, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Ferc Elibrary: Security disclosure. 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.