
Sec Financial Statements MCP server
online · 100% uptimeSEC Financial Statement & Notes data sets — dimensional facts + note text.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Sec Financial Statements yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sec Financial Statements tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Sec Financial Statements compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,072 ms
- faster than 10% of 30,031 servers
Release history: 2 versions in the registry since 2026-09-30, latest 2026-10-29, typically one every 28 days.
Install Sec Financial Statements in Claude Code, Cursor or VS Code
claude mcp add --transport http sec-financial-statements https://gateway.pipeworx.io/sec-financial-statements/mcp
What the publisher says
From the Sec Financial Statements repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/sec-financial-statements
Dimensioned XBRL facts and tagged note text from SEC's DERA "Financial Statement and Notes" data sets — the layer beneath data.sec.gov companyfacts/frames (what edgar and sec-xbrl call), which expose undimensioned facts only. A segment-level revenue number, a geography breakdown, a footnote-tagged hedge notional — none of that is reachable through companyfacts/frames at all; it only exists in SEC's bulk data sets. Hosted, keyless to the caller.
Part of Pipeworx — an MCP gateway connecting AI agents to 1686+ live data sources.
Status at commit time: schema + tools + loader are code-complete; NO PERIOD IS LOADED YET. The
migration (supabase/migrations/219secfinancial_statements.sql) has not been applied to
production and this pack has not been deployed. See "Why this ships without data" below — this is
deliberate, not an oversight, and the next step is written down there.
Tools
name, ILIKE-matched, or a CIK). Each fact carries its period, value, unit and — when dimensioned — the segment/geography axis it belongs to, resolved through secfsndimensions rather than left as a bare hash. This is the tool that answers what companyfacts/frames structurally cannot: "Flutter Entertainment's cross-currency interest rate swap notional" is a DerivativeNotionalAmount fact dimensioned by hedge designation, not a consolidated total.
- companyfinancialfacts(company?, cik?, tag?, limit?) — dimensioned facts for one filer (give a
for ONE tag in one period, ranked — the inverse of a per-company lookup ("who reported the highest AccountsPayableCurrent this quarter").
- tagcrosscompanyscreen(tag, version?, ddate?, dimensionedonly?, limit?) — every filer's value
over tagged note/footnote text blocks — the disclosure prose behind the numbers. Searches tagged note blocks only, not full filing text; see "edgarfilingtext vs. this pack" below.
- notetextsearch(query, company?, tag?, limit?) — full-text search (Postgres english tsvector)
Call this first when a lookup returns nothing — coverage is real and finite, never silently assumed.
- fsn_coverage() — which periods are loaded and how many submissions/facts/note blocks each holds.
edgarfilingtext vs. this pack — complementary, not duplicative
edgarfilingtext (fixed 2026-09-29, fleet #2500, commit 7ab72cdca) does pipe-separated multi-phrase prose search over a filing's rendered text and attaches the one XBRL fact matched to that exact accession when a phrase reads as a financial concept. This pack is the opposite shape: a structured database of every tagged numeric fact (dimensioned included) and every tagged note text block across whichever periods are loaded, queryable by tag/company/period without needing to guess a search phrase that happens to appear verbatim in the rendered document. Use edgarfilingtext to find a fact inside one specific filing's prose; use this pack to screen across companies, pull a full dimensional breakdown, or search note text across many filings at once.
Why this ships without data
Sizes were explicitly UNVERIFIED when this pack was filed (fleet #2506) — "measure first." Measured live against the newest available period (202608notes.zip, HTTP 200, content-length: 312,729,503 compressed): ~2.46GB uncompressed across the six tables this pack loads, num.tsv alone 5,563,767 rows / 1.14GB. Loading even one period is a real, multi-GB bulk operation over SEC's shared fleet egress (CLAUDE.md, fleet #1245) — not something to run casually inside a build session. Parsing and row-mapping were validated locally against the real 202608notes.zip (every table's header/columns confirmed, dimensioned vs. undimensioned facts correctly distinguished, note text and submission rows read cleanly) — the loader is not speculative, it has been run against real SEC bytes, just not into production yet.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sec Financial Statements: common questions
- Is Sec Financial Statements MCP server safe?
- Mostly: it is graded B (73/100). Read the Sec Financial Statements safety report
- How do I install Sec Financial Statements?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Sec Financial Statements need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Sec Financial Statements maintained?
- The last commit was 34 days ago (2026-09-30). The latest release is v0.2.0.
- Is Sec Financial Statements up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Sec Financial Statements compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,072 ms (faster than 10% of 30,031 servers). Full comparison.