# Sec Financial Statements (npm · @pipeworx/mcp-sec-financial-statements)

SEC Financial Statement & Notes data sets — dimensional facts + note text.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/sec-financial-statements-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/sec-financial-statements-mcp)
- npm · `@pipeworx/mcp-sec-financial-statements`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/pipeworx-mcp-sec-financial-statements.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/pipeworx-mcp-sec-financial-statements)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-financial-statements`
- Version: `0.2.1`
- 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-05.

- **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**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-financial-statements).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 759 tokens (~189/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

## Install

### How do I install the Sec Financial Statements MCP server?

Sec Financial Statements runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-financial-statements. 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-sec-financial-statements -- npx -y @pipeworx/mcp-sec-financial-statements
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-sec-financial-statements -- npx -y @pipeworx/mcp-sec-financial-statements
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-sec-financial-statements --command npx --arg -y --arg @pipeworx/mcp-sec-financial-statements
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-sec-financial-statements:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-sec-financial-statements"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-sec-financial-statements -t stdio -c npx -a -y @pipeworx/mcp-sec-financial-statements
```

### Other

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

## 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-05 (score 82, +3)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `company_financial_facts` (~237 tokens)

Dimensioned XBRL facts for one filer — segment, geography or other axis breakdowns that data.sec.gov companyfacts/frames cannot return (those APIs expose undimensioned consolidated totals only). Give a company name (ILIKE match) or a CIK; optionally narrow to one tag (e.g. "Revenues", "LongTermDebtNoncurrent"). Returns each fact's period, value, unit, and — for a dimensioned fact — the segment/member axis it belongs to. Sourced from SEC DERA Financial Statement & Notes data sets, covering only the periods actually loaded (see fsn_coverage).

Input parameters:

- `cik` (string): SEC CIK, with or without leading zeros. Takes priority over company if both are given.
- `company` (string): Company name, matched with ILIKE (e.g. "Flutter Entertainment"). Omit if passing cik.
- `limit` (number): Max facts to return, 1-500 (default 100).
- `tag` (string): Exact XBRL tag name to filter to, e.g. "DerivativeNotionalAmount" (case-sensitive).

### `tag_cross_company_screen` (~223 tokens)

Rank every filer in a loaded period by their reported value for ONE XBRL tag — the inverse of a per-company lookup, e.g. "who reported the highest AccountsPayableCurrent this quarter". Give the exact tag name and (usually) a period-end date (ddate, YYYYMMDD). Set dimensioned_only=true to see only segment/geography-level breakdowns rather than consolidated totals.

Input parameters:

- `ddate` (string): Period-end date, YYYYMMDD (e.g. "20260630"). Omit to rank across all loaded periods for this tag.
- `dimensioned_only` (boolean): true to return only segment/geography-dimensioned rows, skipping consolidated totals.
- `limit` (number): Max filers to return, 1-500 (default 50).
- `tag` (string, required): Exact XBRL tag name, e.g. "Revenues" (case-sensitive).
- `version` (string): Optional taxonomy version, e.g. "us-gaap/2026". Omit to match any version.

### `note_text_search` (~188 tokens)

Full-text search over tagged XBRL note/footnote text blocks — the disclosure prose behind the numbers (hedge notionals, commitment schedules, related-party narrative) that companyfacts/frames never expose. Give a search phrase; optionally narrow to one company or one note tag. This searches tagged NOTE BLOCKS only, not full filing text — for phrase search over the whole filing document use edgar_filing_text instead.

Input parameters:

- `company` (string): Optional company name (ILIKE) to restrict the search to one filer.
- `limit` (number): Max matches to return, 1-100 (default 20).
- `query` (string, required): Search phrase, e.g. "cross-currency interest rate swap notional".
- `tag` (string): Optional exact note tag to restrict to, e.g. "DerivativeInstrumentsAndHedgingActivitiesDisclosureTextBlock".

### `fsn_coverage` (~53 tokens)

Which SEC Financial Statement & Notes periods are currently covered, and how many submissions/facts/note blocks each holds. Call this first if a lookup returns nothing, to confirm whether the period you need is actually covered.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Sec Financial Statements MCP server?

Sec Financial Statements is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-financial-statements. SEC Financial Statement & Notes data sets, dimensional facts + note text. This page covers its npm package (@pipeworx/mcp-sec-financial-statements).

### Is the Sec Financial Statements MCP server safe to use?

Sec Financial Statements 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 Sec Financial Statements MCP server expose?

Sec Financial Statements exposes 4 tools: company_financial_facts, tag_cross_company_screen, note_text_search, fsn_coverage. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.

### Is the Sec Financial Statements MCP server still maintained?

Sec Financial Statements 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 Sec Financial Statements MCP server under?

Sec Financial Statements declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-sec-financial-statements
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-sec-financial-statements
- Repository: https://github.com/pipeworx-io/mcp-sec-financial-statements
- Website: https://pipeworx.io/packs/sec-financial-statements
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/pipeworx-mcp-sec-financial-statements.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/pipeworx-mcp-sec-financial-statements.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-sec-financial-statements/pipeworx-mcp-sec-financial-statements