Best for
- Researchers who need AI-assisted access to U.S. public-company filings
- Users analyzing company, financial, or insider-trading data
- Financial research workflows that require precise numbers and source links
S
SEC EDGAR MCP Server
Community
Give AI assistants access to SEC EDGAR filings.
GitHub source repository ↗
59FMRS · C
This active AGPL-3.0 server provides access to company filings, financial data, and insider transactions through stdio and streamable HTTP. The source does not specify exact tool identifiers, so none are inferred.
SEC EDGAR MCP Server gives AI assistants access to public filings through the U.S. Securities and Exchange Commission EDGAR API. It covers company filings, financial statements, and insider trading data, with an emphasis on exact numeric precision. Built on edgartools, it includes SEC filing URLs for verification.
Tools
The tool list has not been reviewed yet.
Setup
Run it over stdio with Docker. The configuration must set SEC_EDGAR_USER_AGENT to a user-agent string and use docker run -i --rm. Pip, conda, and uv installation methods are also supported according to the project documentation. For platforms such as Dify, use streamable HTTP with: python -m sec_edgar_mcp.server --transport streamable-http --port 9870.
claude_desktop_config.json
{"mcpServers":{"sec-edgar-mcp":{"command":"docker","args":["run","-i","--rm","-e","SEC_EDGAR_USER_AGENT=Your Name ([email protected])","stefanoamorelli/sec-edgar-mcp:latest"]}}}
Fit and risk
Not for
- Users requiring an SEC-maintained or SEC-endorsed server
- Public HTTP deployments requiring built-in authentication
- Other data sources or financial-service capabilities not described in the source material
Required permissions
- Requires access to the SEC EDGAR API
- Requires the non-secret SEC_EDGAR_USER_AGENT environment variable
- HTTP mode should run on a controlled network because authentication is not included
Risks and side effects
- The project states that it is not affiliated with or endorsed by the U.S. Securities and Exchange Commission
- HTTP transport has no authentication and should not be exposed to untrusted networks
- SEC API access may depend on correct user-agent configuration and external service availability
- Financial and insider-trading information should be verified through the returned SEC filing URLs
Troubleshooting
- Confirm that SEC_EDGAR_USER_AGENT is set with identifiable user-agent information
- Ensure the Docker stdio configuration includes -i for MCP JSON-RPC communication
- For HTTP mode, confirm that port 9870 is reachable and the deployment uses a private network
- Check network connectivity to the SEC EDGAR API
- Verify that the selected pip, conda, or uv installation method matches the project documentation
Use cases
Look up CIKs, company information, and company facts
Retrieve 10-K, 10-Q, and 8-K filings and extract sections
Access XBRL-parsed balance sheets, income statements, and cash-flow statements
Query Form 3, 4, and 5 insider transactions
Verify results using the included SEC filing URLs
Supported clients
DifyPartial support