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.

EDGAR Filings

PYPI · EDGAR-FILINGS-MCP · SCANNED SEP 21

SEC 10-K/10-Q symbols, segment revenue, BDC non-accrual, and Form 4 lines with citations.

Available components

65 Trust /100
Trust breakdown (7 categories)

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 7 of 62 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 518 tokens (~129/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the EDGAR Filings MCP server?

EDGAR Filings runs locally as a PyPI package, launched with uvx edgar-filings-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · edgar-filings-mcp

# add to Claude Code
claude mcp add dxfory-edgar-mcp -- uvx edgar-filings-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dxfory-edgar-mcp": {
      "command": "uvx",
      "args": [
        "edgar-filings-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dxfory-edgar-mcp": {
      "command": "uvx",
      "args": [
        "edgar-filings-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dxfory-edgar-mcp -- uvx edgar-filings-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dxfory-edgar-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "edgar-filings-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dxfory-edgar-mcp --command uvx --arg edgar-filings-mcp
# ~/.hermes/config.yaml
mcp_servers:
  dxfory-edgar-mcp:
    command: "uvx"
    args: ["edgar-filings-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dxfory-edgar-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "edgar-filings-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dxfory-edgar-mcp -t stdio -c uvx -a edgar-filings-mcp
// mcp.json
{
  "mcpServers": {
    "dxfory-edgar-mcp": {
      "command": "uvx",
      "args": [
        "edgar-filings-mcp"
      ]
    }
  }
}
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.

  • 21 Sept 26 65

    First indexed and scored.

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 Sept 2026 · Analysed pypi/edgar-filings-mcp@1.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 62 packages
Packages resolved 62
Stale 6
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~408 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_bdc_nonaccrual ~115

Non-accrual investments from a BDC 10-K or 10-Q, cited to the filing. Use this instead of guessing private-credit quality. ticker_or_cik must be an SEC BDC (814- filer) such as ARCC. Operating companies like NVDA raise. Non-accrual is the filer's tagged status, not Fitch PCDR and not PIK.

NameTypeReqDescription
accession
formstring
ticker_or_cikstringyes

No output schema declared.

No examples provided.

get_form4 ~67

Recent Form 4 insider filings: who, role, activity, and transaction lines. limit: 1-20 filings, newest first. P/S are open_market true; A/M/F are false.

NameTypeReqDescription
limitinteger
ticker_or_cikstringyes

No output schema declared.

No examples provided.

get_segment_revenue ~109

Dimensioned XBRL revenue facts from a 10-K or 10-Q (product, business, geographic axes). This is filing data, not a consolidated income statement. ticker_or_cik: ticker like NVDA or a CIK. accession: optional filing accession; default is the latest of `form`. form: 10-K (default) or 10-Q.

NameTypeReqDescription
accession
formstring
ticker_or_cikstringyes

No output schema declared.

No examples provided.

get_trading_symbols ~117

Every dei:TradingSymbol fact on a 10-K or 10-Q, plus the legacy entity_info ticker scalar. Use this when you need the common stock ticker versus preferred, notes, or dual-class symbols. ticker_or_cik: ticker like NVDA or a CIK. accession: optional filing accession; default is the latest of `form`. form: 10-K (default) or 10-Q.

NameTypeReqDescription
accession
formstring
ticker_or_cikstringyes

No output schema declared.

No examples provided.

Common questions

What is the EDGAR Filings MCP server?

EDGAR Filings is an MCP server listed in the public MCP registry as io.github.Dxfory/edgar-mcp. SEC 10-K/10-Q symbols, segment revenue, BDC non-accrual, and Form 4 lines with citations. This page covers its PyPI package (edgar-filings-mcp).

Is the EDGAR Filings MCP server safe to use?

EDGAR Filings scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 EDGAR Filings MCP server expose?

EDGAR Filings exposes 4 tools: get_trading_symbols, get_segment_revenue, get_bdc_nonaccrual, get_form4. Their descriptions and schemas cost roughly 408 tokens of context every time the server is loaded.

Is the EDGAR Filings MCP server still maintained?

EDGAR Filings is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.