io.github.stefanoamorelli/sec-edgar-mcp
io.github.stefanoamorelli/sec-edgar-mcp
Is the io.github.stefanoamorelli/sec-edgar-mcp MCP server down? Yes. It has given no valid answer since 2026-10-19: install failed.
SEC EDGAR MCP server that provides access to the US public filings through the US SEC EDGAR API
install failed down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
error: Failed to install entrypoints for `sec-edgar-mcp`
- Run it
- uvx sec-edgar-mcp@1.0.5 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/stefanoamorelli/sec-edgar-mcp
- Registry
- active, updated 2025-09-09 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.stasxr/palanit-core · crashed on start
- io.github.statwonk/decern · needs mcp<2
- CogniRelay io.github.stef-k/cognirelay · not probed
- EduPage Keyring io.github.stefanbackor/edupage-keyring-mcp · needs args
- RLM Tools io.github.stefanoshea/rlm-tools · needs mcp<2
- Azure Verified Modules (AVM) MCP Server io.github.stefanstranger/avm-mcp-server · needs mcp<2
- Stockfish MCP io.github.stepbot/stockfish-mcp · needs args
- io.github.sterion66/godot · alive
Servers that mention edgar.
- ai.smithery/plainyogurt21-sec-edgar-mcp · not found
- app.vercel.auditflag-lac/auditflag · alive
- app.vercel.filingcheck-bot/filingcheck · alive
- Sivut SEC Crypto Filing Radar co.sivut.pay/sec-crypto-filing-radar · no DNS
- Data APIs SEC Event Intelligence API com.data-apis.api/sec-event-intelligence · server error
- Filings Intel MCP com.datakoot/sec-edgar-filings · alive
- com.edgethirteen.www/numbercheck · alive
- com.edgethirteen.www/us-diligence · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-19, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.