SEC EDGAR Filings MCP server
online · 100% uptimeio.github.stagproject/sec-filings-mcp·v1.0.2·2 starsSEC EDGAR MCP: search, preview, purchase filings. x402 USDC on Polygon. xpay + Cloud Run upstream.
2 stars
Reviews
Write oneNobody has reviewed SEC EDGAR Filings MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
SEC EDGAR Filings MCP tools (3, 1 write)
write = sends, deletes, buys or postsget_filing_sampleFreeFree preview of one SEC filing (agent-friendly compact row from fi_listings_portfolio_compact). [COST: $0] Includes agent_summary and financial_metrics (CompanyFacts-derived) but NOT full alpha_signals / causality_events — those ship only via purchase_filing after x402 payment. Compare with purchase_filing: sample = evaluate quality; purchase = full evidence-backed JSON. [EXAMPLE ARGUMENTS - MINIMAL]: {} [EXAMPLE ARGUMENTS - MAXIMAL]: {"document_id": "000000708426000023"}
purchase_filingwrite actionFreePurchase and deliver one full SEC filing row from fi_listings_portfolio (MPP v1.0 x402). [COST: xpay per-call + on-chain USDC data price (see FINANCE_FILING_PRICE_USD)] Full JSON includes alpha_signals with evidence_verified causality_events and financial_metrics from SEC CompanyFacts. Do NOT return agent_bundle or internal pipeline fields. [AGENTIC WORKFLOW — mandatory 2-step 402 flow]: STEP 1: Call with document_id and network only; leave tx_hash EMPTY. STEP 2: Broadcast the exact transaction_payload on-chain (polygon USDC default). STEP 3: Call again with the same document_id, network, and confirmed tx_hash (66 chars). [EXAMPLE ARGUMENTS - MINIMAL (Step 1 — payment info)]: {"document_id": "000000708426000023", "network": "polygon"} [EXAMPLE ARGUMENTS - MAXIMAL (Step 3 — claim data)]: { "document_id": "000000708426000023", "network": "polygon", "tx_hash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef" }
search_filingsFreePRIMARY discovery tool — lightweight catalog over 10k+ SEC filings (fi_listings_portfolio). [COST: low xpay per-call fee] Does NOT return alpha_signals, causality_events, or financial_metrics (use get_filing_sample / purchase_filing). Always returns agent_readiness_score (higher = better structured data) and edgar_url. Required: at least one of ticker, form_type, company_name, fiscal_period, cik (avoids full-table scans). Agent workflow after this call: 1. Shortlist by agent_readiness_score and optional agent_one_liner 2. get_filing_sample(document_id) — free preview 3. purchase_filing(document_id) — paid full JSON (x402) [EXAMPLE ARGUMENTS - MINIMAL]: {"ticker": "AAPL", "limit": 5} [EXAMPLE ARGUMENTS - MAXIMAL]: { "ticker": "ADM", "form_type": "10-Q", "company_name": "Archer", "fiscal_period": "2026Q1", "min_agent_readiness_score": 70, "limit": 20, "offset": 0, "include_one_liner": true } [EXAMPLE ARGUMENTS - PAGINATION (page 2)]: {"ticker": "MSFT", "form_type": "10-K", "limit": 10, "offset": 10}
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 239ms (auth required)20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityauth enforced (unknown)9/15
- Maintenancelast push 120 days ago8/15
- Maintainer identityregistry namespace matches repository owner6/10
How SEC EDGAR Filings MCP compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 55% of 3,470 Web search servers
- Tools
- 3
- the typical Web search server has 5
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Web search server answers 100%
- Response time
- 167 ms
- faster than 75% of 2,238 Web search servers
- GitHub stars
- 2
- more than 70% of 1,786 Web search servers
What its tools let an agent do: 2 read · 1 change
Install SEC EDGAR Filings MCP in Claude Code, Cursor or VS Code
claude mcp add --transport http sec-filings-mcp https://sec-edgar-filings.mcp.xpay.sh/mcp
What the publisher says
From the SEC EDGAR Filings MCP repository's README, as published. We do not edit it. Read it on GitHub
sec-filings-mcp
SEC EDGAR structured filing MCP for agents: searchfilings, getfilingsample, purchasefiling. Data lives in Supabase views (filistingsportfolio, filistingsportfolio_compact) populated by the finance-factory pipeline.
Template reference: mcpserver.py (patent MCP, unmodified). Runtime: mcpserver_finance.py.
Protocol stack (MCP + A2A + x402)
Native A2A JSON-RPC task API is on the roadmap; today agents invoke via MCP Streamable HTTP. Details: docs/A2A.md.
Try first (no xpay API key)
Details: docs/TRYWITHOUTXPAY.md. xpay proxy always needs a key; per-tool $0 is allowed on xpay (docs) but is not the same as “no signup.”
Connect (production)
Register / manage on xpay.tools. Slug: sec-edgar-filings. Publisher checklist (finance collection, awesome list): docs/DISTRIBUTION.md.
Local dev
git clone https://github.com/stagproject/sec-filings-mcp.git
cd sec-filings-mcp
copy .env.example .env
# Edit .env with Supabase + x402 keys
uv sync
# Run once in Supabase SQL Editor: sql/fi_processed_transactions.sql
uv run python mcp_server_finance.py --sse
# MCP: http://127.0.0.1:8081/mcp (PORT in .env)Tests:
uv run python test_finance_mcp.py
uv run python test_finance_mcp.py --xpay-only --e2eCloud Run
gcloud run deploy sec-filings-mcp `
--source . `
--region us-central1 `
--allow-unauthenticated `
--port 8080Set env vars from .env (not committed). Do not deploy .env.cloudrun.yaml to git.
Glama
Listed at glama.ai/mcp/servers/stagproject/sec-filings-mcp — use Try in Browser for a no-key sandbox; production traffic uses xpay or Cloud Run above.
MCP Registry
io.github.stagproject/sec-filings-mcpShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
SEC EDGAR Filings MCP: common questions
- Is SEC EDGAR Filings MCP server safe?
- Mostly: it is graded B (77/100). Read the SEC EDGAR Filings MCP safety report
- How do I install SEC EDGAR Filings MCP?
- It runs remotely at sec-edgar-filings.mcp.xpay.sh. 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 EDGAR Filings MCP need an API key?
- Yes. The registry entry asks for
key. - Is SEC EDGAR Filings MCP maintained?
- The last commit was 158 days ago (2026-05-30). The latest release is v1.0.2.
- Is SEC EDGAR Filings MCP up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of SEC EDGAR Filings MCP?
- Servers from other publishers that do the same job: Tenjin MCP server, DocsMint MCP server and Kody MCP server.
- How does SEC EDGAR Filings MCP compare with other Web search MCP servers?
- safety score 77/100 (higher than 55% of 3,470 Web search servers); tools 3 (the typical Web search server has 5); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to SEC EDGAR Filings MCP
Same job from other publishers: the closest match first, then the best rated.
TenjinSearch, read & publish paid essays. Pay-per-read in USDC on Base (x402); wallet-only, no account.not reviewedEstablishedB
DocsMintCloud or self-hosted knowledge for AI agents: hybrid search, reranking, GraphRAG, scoped MCP tools.not reviewedEstablishedA
KodyYour agents' cloud for individuals and teams. Search, execute, packages, jobs, and credentials.not reviewedEstablishedA- M3 MemoryLocal-first, cloud-friendly memory — 100+ tools, 99.2% LongMemEval-S retrieval@8, hybrid search.not reviewedEstablishedA