# Ferc Form1 (npm · @pipeworx/mcp-ferc-form1)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ferc-form1/ferc-form1-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ferc-form1/ferc-form1-mcp)
- npm · `@pipeworx/mcp-ferc-form1`: 69/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1.md), [page](https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ferc-form1`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add pipeworx-io-ferc-form1 -- npx -y @pipeworx/mcp-ferc-form1
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-ferc-form1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ferc-form1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-ferc-form1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ferc-form1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-ferc-form1 -- npx -y @pipeworx/mcp-ferc-form1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-ferc-form1": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-ferc-form1"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ferc-form1 --command npx --arg -y --arg @pipeworx/mcp-ferc-form1
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-ferc-form1:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-ferc-form1"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-ferc-form1": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-ferc-form1"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-ferc-form1 -t stdio -c npx -a -y @pipeworx/mcp-ferc-form1
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ferc-form1": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ferc-form1"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-16 (score 69, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 54)

First indexed and scored.

## MCP tools (5)

### `ferc1_find_utility` (~109 tokens)

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.

Input parameters:

- `limit` (integer): Max matches to return (default 20, max 100).
- `query` (string, required): Part of the utility name, e.g. "PacifiCorp" or "duke energy".

### `ferc1_income_statement` (~200 tokens)

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.

Input parameters:

- `utility` (string, required): FERC 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_type` (string): Optional filter on the business segment the rows describe: total, electric, gas, other. Default: all segments the respondent reported.
- `year` (integer): Report year (e.g. 2023). Default: the latest year on file for the respondent.

### `ferc1_income_history` (~168 tokens)

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.

Input parameters:

- `income_type` (string): Line item name, e.g. operating_revenues (default), net_income_loss, utility_operating_expenses, depreciation_expense.
- `utility` (string, required): FERC 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_type` (string): Segment: total (default), electric, gas, other.

### `ferc1_balance_sheet` (~146 tokens)

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.

Input parameters:

- `utility` (string, required): FERC 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.
- `year` (integer): Report year (e.g. 2023). Default: the latest year on file for the respondent.

### `ferc1_utility_plant` (~178 tokens)

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.

Input parameters:

- `utility` (string, required): FERC 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_type` (string): Optional filter on the business segment the rows describe: total, electric, gas, other. Default: all segments the respondent reported.
- `year` (integer): Report year (e.g. 2023). Default: the latest year on file for the respondent.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 54

## 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-ferc-form1
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ferc-form1
- Repository: https://github.com/pipeworx-io/mcp-ferc-form1
- Website: https://pipeworx.io/packs/ferc-form1
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ferc-form1/pipeworx-mcp-ferc-form1
