Ferc Eqr
NPM · @PIPEWORX/MCP-FERC-EQR · 2 COMPONENTS
FERC Electric Quarterly Reports (EQR) — wholesale power sales: who sells to whom, under what…
Available components
Last scanned (7 hours ago)
Scores higher than 76% 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-eqr). 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 888 tokens (~222/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.
- 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.
- 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
- Security disclosure: unverified → fail ▼ functional
- 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
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ 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-eqr@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-eqr |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ferc-eqr/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635942334 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c66cb9bc9a9b9a5a39b44e2691b465fbdf5c40d6926e29eb3383835e432fc13671b7d2b0f906b4715fae5990eebd51afa46422276aee15c5372271ec6 |
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 →
eqr_contracts_search ~306
Search FERC EQR wholesale power contracts by seller, counterparty and/or product. Returns contract-level records: seller, customer, product (e.g. ENERGY, CAPACITY), quantity, rate, rate units, delivery/receipt points, and the contract execution/term dates. Each row is one RATE-PERIOD line item within a contract (a single contract can have several rows for different rate periods) — not a settled trade. Use eqr_seller_lookup first to resolve a company name to a company_id_ferc if you want an exact-seller match rather than a name substring. Sourced from FERC EQR via PUDL (CC-BY-4.0), Phase 1 (contract terms; no transaction-level price/volume yet).
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty | string | – | Counterparty/customer company name, substring match. |
| limit | number | – | Max rows to return (default 20, max 100). |
| offset | number | – | Row offset for paging beyond `limit` (default 0). |
| product | string | – | Product name substring, e.g. "ENERGY", "CAPACITY", "TRANSMISSION". |
| quarter_from | string | – | Earliest quarter to include, format "2020q1". |
| quarter_to | string | – | Latest quarter to include, format "2026q2". |
| seller | string | – | Seller name (substring match) or exact company_id_ferc. |
No output schema declared.
No examples provided.
eqr_counterparty_sellers ~216
Who sells wholesale power TO a given counterparty — the reverse of eqr_contracts_search. Aggregates FERC EQR contracts by seller for a counterparty name match, returning each seller's contract count, the quarter range they appear in, and the distinct products sold. Answers "who sells power to PacifiCorp" / "which generators have contracts with <utility>" directly, which a single-table filter cannot (it needs a group-by across all matching contracts). Sourced from FERC EQR via PUDL (CC-BY-4.0), Phase 1 (contract terms only).
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty | string | yes | Counterparty/customer company name, substring match, e.g. "PacifiCorp". |
| limit | number | – | Max sellers to return (default 25, max 100). |
| quarter_from | string | – | Earliest quarter to include, format "2020q1". |
| quarter_to | string | – | Latest quarter to include, format "2026q2". |
No output schema declared.
No examples provided.
eqr_coverage ~88
What FERC EQR data is currently available and how fresh it is: row counts for the filer-identity, index-publisher and contracts tables, the quarter range covered, and when it was last refreshed. Use before relying on a result to confirm coverage includes the quarter you care about. Sourced from FERC EQR via PUDL (CC-BY-4.0).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
eqr_seller_lookup ~222
Find a FERC Electric Quarterly Report filer (seller/power marketer/utility) by name or FERC company id (e.g. "C000740"). Returns their per-quarter filing records — company name(s) as filed and whether they reported transactions to an index price publisher (Argus, ICE, S&P Global/SNL, etc.). Company-level identity only, no filer contact details. Use this to resolve a company name to its company_id_ferc before calling eqr_contracts_search, or to check whether/when a company filed an EQR. Sourced from FERC EQR via PUDL (CC-BY-4.0). Distinct from ferc-elibrary, which is the FERC docket/document search, not filer or transaction data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max filing records to return (default 20, max 100). |
| query | string | yes | Company name (substring match, e.g. "NextEra") or exact FERC company id (e.g. "C000740"). |
No output schema declared.
No examples provided.
How do I install the Ferc Eqr MCP server?
Ferc Eqr runs locally as an npm package, launched with npx -y @pipeworx/mcp-ferc-eqr. 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-eqr
claude mcp add pipeworx-io-ferc-eqr -- npx -y @pipeworx/mcp-ferc-eqr
What is the Ferc Eqr MCP server?
Ferc Eqr is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ferc-eqr. FERC Electric Quarterly Reports (EQR), wholesale power sales: who sells to whom, under what… This page covers its npm package (@pipeworx/mcp-ferc-eqr).
Is the Ferc Eqr MCP server safe to use?
Ferc Eqr scores 83 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 Eqr MCP server expose?
Ferc Eqr exposes 4 tools: eqr_seller_lookup, eqr_contracts_search, eqr_counterparty_sellers, eqr_coverage. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.
Is the Ferc Eqr MCP server still maintained?
Ferc Eqr 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 Eqr MCP server under?
Ferc Eqr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.