FilingFirehose
REMOTE · FILINGFIREHOSE.COM · SCANNED SEP 26
SEC EDGAR filings parsed: 8-K body-text classification, 13D activist tagging, S-3 ATM detection.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 889 tokens (~222/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
How do I install the FilingFirehose MCP server?
FilingFirehose is a hosted endpoint at https://filingfirehose.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · filingfirehose.com
claude mcp add --transport http com-filingfirehose-firehose 'https://filingfirehose.com/mcp'
{
"mcpServers": {
"com-filingfirehose-firehose": {
"url": "https://filingfirehose.com/mcp"
}
}
} {
"servers": {
"com-filingfirehose-firehose": {
"type": "http",
"url": "https://filingfirehose.com/mcp"
}
}
} [mcp_servers.com-filingfirehose-firehose] url = "https://filingfirehose.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-filingfirehose-firehose": {
"type": "remote",
"url": "https://filingfirehose.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-filingfirehose-firehose --url 'https://filingfirehose.com/mcp' --transport streamable-http
mcp_servers:
com-filingfirehose-firehose:
url: "https://filingfirehose.com/mcp" {
"McpServers": {
"com-filingfirehose-firehose": {
"Transport": "http",
"Url": "https://filingfirehose.com/mcp"
}
}
} assistant mcp add com-filingfirehose-firehose -t streamable-http -u 'https://filingfirehose.com/mcp'
{
"mcpServers": {
"com-filingfirehose-firehose": {
"type": "http",
"url": "https://filingfirehose.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +30
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 25 Sept 26 −15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 21 Sept 26 +30
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 19 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
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 26 Sept 2026 · Probed https://filingfirehose.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=filingfirehose.com | CN=YE2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c3c4c726114fb9a6a01338fefa9fd4d94a |
| SANs: filingfirehose.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of filingfirehose.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| filingfirehose.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://filingfirehose.com/mcp | Verified | 200 | |
| http (plaintext) | http://filingfirehose.com/mcp | HTTPS enforced | 301 | https://filingfirehose.com/mcp |
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 →
get_filing ~97
Fetch one filing by SEC accession number, regardless of recency. Useful when an agent has an accession number from a citation or earlier tool call and needs the parsed details. Args: accession_number: SEC accession in 'XXXXXXXXXX-YY-NNNNNN' format. Returns: JSON for the filing if found in our archive, or {"found": false}.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_13d_filings ~231
Search recent SEC Schedule 13D / 13G filings from the past 72 hours. Args: activist: Filter to filings tagged with this activist filer name. Substring match, case-insensitive. Examples: 'Saba', 'Starboard', 'Icahn', 'Elliott', 'Pershing'. min_percent: Minimum percent of class disclosed. include_amendments: Include 13D/A and 13G/A amendments. Default True. include_passive_13g: Include passive Schedule 13G filings. Default False (only active 13D / 13D/A returned). limit: Max results (1-50, default 25). Returns: JSON list of filings with cusip, percent_of_class, aggregate_amount, activist_filers, and an Item 4 purpose excerpt.
| Name | Type | Req | Description |
|---|---|---|---|
| activist | – | – | – |
| include_amendments | boolean | – | – |
| include_passive_13g | boolean | – | – |
| limit | integer | – | – |
| min_percent | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_8k_filings ~262
Search recent SEC 8-K filings (current report) from the past 72 hours. Args: items: Comma-separated 8-K item codes to filter on. Examples: '1.05' (cybersecurity), '5.02' (officer departure), '8.01' (other events), '1.01' (material agreement). Leave None for all 8-Ks. suspected_buried_only: If True, return only filings where our body-text classifier flagged a suspected misclassification — i.e. cyber language under Item 8.01 that should have been 1.05, officer-departure language under 8.01 that should have been 5.02. limit: Max results (1-50, default 25). Returns: JSON-formatted list of filings. Each includes: accession_number, company_name, filed_at, filer_reported_items, detected_items, discrepancy_items (in body but not reported), and suspected_buried_events (map of reported→suspected).
| Name | Type | Req | Description |
|---|---|---|---|
| items | – | – | – |
| limit | integer | – | – |
| suspected_buried_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_atm_offerings ~184
Search recent SEC at-the-market (ATM) equity offerings from the past 72 hours. Pulls from S-3 / 424B5 family filings where our parser flagged ATM-offering indicators in the body language. Args: sales_agent: Filter by sales agent name (substring, case-insensitive). Examples: 'Cantor Fitzgerald', 'Jefferies', 'Roth Capital', 'H.C. Wainwright'. min_shelf_million_usd: Minimum shelf size in millions USD. limit: Max results (1-50, default 25). Returns: JSON list with shelf_size_usd, is_atm, sales_agents, use_of_proceeds_excerpt.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_shelf_million_usd | – | – | – |
| sales_agent | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the FilingFirehose MCP server?
FilingFirehose is an MCP server listed in the public MCP registry as com.filingfirehose/firehose. SEC EDGAR filings parsed: 8-K body-text classification, 13D activist tagging, S-3 ATM detection. This page covers its hosted endpoint (https://filingfirehose.com/mcp).
Is the FilingFirehose MCP server safe to use?
FilingFirehose scores 74 out of 100 on VerifyMCP. 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 FilingFirehose MCP server expose?
FilingFirehose exposes 4 tools: search_8k_filings, search_13d_filings, search_atm_offerings, get_filing. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.
Does the FilingFirehose MCP server require authentication?
No. We connected to FilingFirehose without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FilingFirehose MCP server still maintained?
FilingFirehose is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.