Sec Financial Statements
NPM · @PIPEWORX/MCP-SEC-FINANCIAL-STATEMENTS · 2 COMPONENTS
SEC Financial Statement & Notes data sets — dimensional facts + note text.
Available components
Last scanned (8 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-sec-financial-statements). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. 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 +3
- 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
- Stability: unverified → 0.23 ▲ 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-sec-financial-statements@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-sec-financial-statements |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-financial-statements/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692341449 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:62e1935327d44cdac41fcaed397a3dd9d0f857c291aec606df5d94f3d7a363ca264869419adeba621d25f9a43e9f9e1135d6476613bb95375551ddbb1 |
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 →
company_financial_facts ~237
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
fsn_coverage ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
note_text_search ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search phrase, e.g. "cross-currency interest rate swap notional". |
| tag | string | – | Optional exact note tag to restrict to, e.g. "DerivativeInstrumentsAndHedgingActivitiesDisclosureTextBlock". |
No output schema declared.
No examples provided.
tag_cross_company_screen ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Exact XBRL tag name, e.g. "Revenues" (case-sensitive). |
| version | string | – | Optional taxonomy version, e.g. "us-gaap/2026". Omit to match any version. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-sec-financial-statements
claude mcp add pipeworx-io-sec-financial-statements -- npx -y @pipeworx/mcp-sec-financial-statements
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.