Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ferc Form1

NPM · @PIPEWORX/MCP-FERC-FORM1 · 2 COMPONENTS

FERC Form 1 — annual financial and operating reports of major US investor-owned electric, gas and…

69 Trust /100

Last scanned (22 hours ago)

Scores higher than 40% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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 & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 857 tokens (~171/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

Changelog

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.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 54

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@pipeworx/mcp-ferc-form1@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~801 tokens

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 →

Tool Tokens
ferc1_balance_sheet ~146

FERC Form 1 comparative balance sheet (Schedule 110) for one utility and report year: assets and liabilities/equity line items with starting and ending balances in US dollars. Source: FERC Form 1 as processed by Catalyst Cooperative PUDL.

NameTypeReqDescription
utilitystringyesFERC Form 1 respondent: a name (e.g. "PacifiCorp") or the numeric FERC respondent id (utility_id_ferc1, e.g. 303). Find ids with ferc1_find_utility.
yearinteger–Report year (e.g. 2023). Default: the latest year on file for the respondent.

No output schema declared.

No examples provided.

ferc1_find_utility ~109

Find FERC Form 1 respondents (US investor-owned electric/gas utilities that file the annual FERC Form 1) by name. Returns the FERC respondent id to use in the other ferc1_* tools. found:false when no respondent matches.

NameTypeReqDescription
limitinteger–Max matches to return (default 20, max 100).
querystringyesPart of the utility name, e.g. "PacifiCorp" or "duke energy".

No output schema declared.

No examples provided.

ferc1_income_history ~168

One FERC Form 1 income-statement line (default operating_revenues) for one utility across every report year on file, 1994 to date, for trends. Use ferc1_income_statement to see the available income_type names.

NameTypeReqDescription
income_typestring–Line item name, e.g. operating_revenues (default), net_income_loss, utility_operating_expenses, depreciation_expense.
utilitystringyesFERC Form 1 respondent: a name (e.g. "PacifiCorp") or the numeric FERC respondent id (utility_id_ferc1, e.g. 303). Find ids with ferc1_find_utility.
utility_typestring–Segment: total (default), electric, gas, other.

No output schema declared.

No examples provided.

ferc1_income_statement ~200

FERC Form 1 income statement (Schedule 114) for one utility and report year: operating revenues, operating expenses, taxes, net utility operating income, net income, in US dollars as filed, by line item and segment. The headline block gives total operating revenues and net income. Source: FERC Form 1 as processed by Catalyst Cooperative PUDL.

NameTypeReqDescription
utilitystringyesFERC Form 1 respondent: a name (e.g. "PacifiCorp") or the numeric FERC respondent id (utility_id_ferc1, e.g. 303). Find ids with ferc1_find_utility.
utility_typestring–Optional filter on the business segment the rows describe: total, electric, gas, other. Default: all segments the respondent reported.
yearinteger–Report year (e.g. 2023). Default: the latest year on file for the respondent.

No output schema declared.

No examples provided.

ferc1_utility_plant ~178

FERC Form 1 summary of utility plant and accumulated provisions for depreciation, amortization and depletion (Schedule 200) for one utility and report year: plant in service, construction work in progress, accumulated depreciation, by segment, in US dollars.

NameTypeReqDescription
utilitystringyesFERC Form 1 respondent: a name (e.g. "PacifiCorp") or the numeric FERC respondent id (utility_id_ferc1, e.g. 303). Find ids with ferc1_find_utility.
utility_typestring–Optional filter on the business segment the rows describe: total, electric, gas, other. Default: all segments the respondent reported.
yearinteger–Report year (e.g. 2023). Default: the latest year on file for the respondent.

No output schema declared.

No examples provided.

Install

How do I install the Ferc Form1 MCP server?

Ferc Form1 runs locally as an npm package, launched with npx -y @pipeworx/mcp-ferc-form1. 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-form1

# add to Claude Code
claude mcp add pipeworx-io-ferc-form1 -- npx -y @pipeworx/mcp-ferc-form1
Common questions

What is the Ferc Form1 MCP server?

Ferc Form1 is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ferc-form1. FERC Form 1, annual financial and operating reports of major US investor-owned electric, gas and… This page covers its npm package (@pipeworx/mcp-ferc-form1).

Is the Ferc Form1 MCP server safe to use?

Ferc Form1 scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Form1 MCP server expose?

Ferc Form1 exposes 5 tools: ferc1_find_utility, ferc1_income_statement, ferc1_income_history, ferc1_balance_sheet, ferc1_utility_plant. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

Is the Ferc Form1 MCP server still maintained?

Ferc Form1 is still listed as active in the MCP registry. We last reached this channel on 21 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 Form1 MCP server under?

Ferc Form1 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 Form1 MCP server?

VerifyMCP ran 15 checks on Ferc Form1, 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 Form1: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.