Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SEC EDGAR Filings MCP

REMOTE · SEC-FILINGS-MCP-1065601264332.US-CENTRAL1.RUN.APP · 2 COMPONENTS

SEC EDGAR MCP: search, preview, purchase filings. x402 USDC on Polygon. xpay + Cloud Run upstream.

0 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1090 tokens (~363/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff32d6b409d15d5965b05873a7c72e0
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sec-filings-mcp-1065601264332.us-central1.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp Verified 200
http (plaintext) http://sec-filings-mcp-1065601264332.us-central1.run.app/mcp HTTPS enforced 302 https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp
MCP tools · 3 exposed · ~1,001 tokens

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 →

Tool Tokens
get_filing_sample ~150

Free 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"}

NameTypeReqDescription
document_id––document_id from search_filings. Defaults to demo ADM 10-Q (000000708426000023).
NameTypeReqDescription
resultstringyes–

No examples provided.

purchase_filing ~321

Purchase 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" }

NameTypeReqDescription
document_idstringyesdocument_id from search_filings or get_filing_sample.
network––Blockchain network. Default polygon (USDC). Also supports base.
tx_hash––Transaction hash. LEAVE EMPTY on first call to receive 402 payment instructions.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_filings ~530

PRIMARY 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}

NameTypeReqDescription
cik––SEC CIK prefix (digits, e.g. 0000320193).
company_name––Substring match on company_name (e.g. Apple, Archer-Daniels).
fiscal_period––Fiscal period label (e.g. 2026Q1, 2025FY).
form_type––SEC form: 10-K, 10-Q, 8-K, etc.
include_one_liner––If true, adds agent_one_liner (~1 sentence) per row for triage without calling get_filing_sample. Slightly heavier response.
limit––Page size (1–100). Default 10 keeps payloads small for LLM context.
min_agent_readiness_score––Minimum agent_readiness_score (0–100). Use 70+ for production-quality rows.
offset––Skip rows for pagination (e.g. 10 for page 2 when limit=10).
ticker––Ticker prefix, case-insensitive (e.g. AAPL, MSFT). At least one filter required.
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the SEC EDGAR Filings MCP server?

SEC EDGAR Filings MCP is a hosted endpoint at https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · sec-filings-mcp-1065601264332.us-central1.run.app

# add to Claude Code
claude mcp add --transport http stagproject-sec-filings-mcp 'https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp'
Common questions

What is the SEC EDGAR Filings MCP server?

SEC EDGAR Filings MCP is listed in the public MCP registry as io.github.stagproject/sec-filings-mcp. SEC EDGAR MCP: search, preview, purchase filings. x402 USDC on Polygon. xpay + Cloud Run upstream. This page covers its hosted endpoint (https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp).

Is the SEC EDGAR Filings MCP server safe to use?

SEC EDGAR Filings MCP scores 76 out of 100 on VerifyMCP. 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 EDGAR Filings MCP server expose?

SEC EDGAR Filings MCP exposes 3 tools: search_filings, get_filing_sample, purchase_filing. Their descriptions and schemas cost roughly 1,001 tokens of context every time the server is loaded.

Does the SEC EDGAR Filings MCP server require authentication?

No. We connected to SEC EDGAR Filings MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SEC EDGAR Filings MCP server still maintained?

SEC EDGAR Filings MCP 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 did VerifyMCP test on the SEC EDGAR Filings MCP server?

VerifyMCP ran 12 checks on SEC EDGAR Filings MCP, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SEC EDGAR Filings MCP: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.