
FilingFirehose
com.filingfirehosev0.1.0Updated Sep 29, 2026
SEC EDGAR filings parsed: 8-K body-text classification, 13D activist tagging, S-3 ATM detection.
Installation
In SourceWeft
- Open FilingFirehose in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"firehose": {
"type": "http",
"url": "https://filingfirehose.com/mcp"
}
}
}README
filing-firehose
Python client for the FilingFirehose SEC EDGAR API — body-text-parsed 8-Ks (with buried-event detection), activist-tagged Schedule 13D/G filings, and ATM offerings extracted from S-3 / 424B5 prospectus supplements.
Install
Quick start
The free public tier returns the last 72 hours of filings — no API key required:
For the full historical archive, get an API key at filingfirehose.com:
Async
Why this client
The wedge: most SEC filings APIs trust the filer-reported item codes on
8-K filings. We body-text-classify every filing and surface a
suspected_buried_events field flagging when the body language doesn't match
the filer's claimed item codes. From a 21-day analysis of 4,251 8-Ks,
7.3% of Item 8.01 filings contain language suggesting a more specific item
should have been used — including buried cyber incidents (1.05), officer
departures (5.02), and material agreements (1.01).
License
MIT.
Source: README.md at commit 16fe79e
Tools
0Version history
1- v0.1.0LatestSep 16, 2026