io.github.ciscoriordan/parsec-edgar

parsec-edgar: SEC EDGAR filings

Is the parsec-edgar MCP server down? Yes. It has given no valid answer since 2026-11-10: crashed on start.

Search SEC EDGAR, list company filings, and read 10-K, 10-Q and 8-K filings one Item at a time

crashed on start down since 2026-11-10 · probed 2026-11-15 · unchanged since 2026-11-13

MCP error -32000: Connection closed
error: the SEC requires a User-Agent with a name and contact email, e.g. "Example Corp admin@example.com"

Run it: uvx parsec-edgar@0.2.1 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/ciscoriordan/parsec-edgar
Registry: active, updated 2026-11-12 · registry entry

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

io.github.christianclaudio/taxcode · alive
Argus — Testing for Coding Agents io.github.chriswu727/argus · alive
Sibyl — Deep Research MCP io.github.chriswu727/sibyl · alive
OptiVibe io.github.chuang44-tiff/optivibe-mcp · alive
ClaimIDX io.github.claimidx/claimidx · crashed on start
io.github.clarenceh/expenselm-mcp-server · alive
Clay Seal io.github.clayseal/clayseal · crashed on start
SAM.gov Opportunities io.github.clean-data-labs-org/samgov-opportunities · alive

Servers that mention parsec or filings or edgar.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

No valid answer since 2026-11-10, in every probe since then.
The process exited on start before it answered initialize. The error output is above.