mcp-registry/com.filingfirehose/firehose · v1.29.0
As of 2026-10-21 00:44 UTC, the Filingfirehose Firehose MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 80.5% of Glimind's liveness checks. It had 228 outages in 90 days, with a median recovery of 15 minutes.
SEC EDGAR filings parsed: 8-K body-text classification, 13D activist tagging, S-3 ATM detection.
Point your MCP client at this streamable-http endpoint: https://filingfirehose.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
Reachable 80.5% of the time over the last 30 days; median recovery 15 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
12 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,527 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.filingfirehose%2Ffirehose/fixes
{
"name": "get_filing",
"description": "Fetch one filing by SEC accession number, regardless of recency.\n\n Useful when an agent has an accession number from a citation or earlier\n tool call and needs the parsed details.\n\n Args:\n accession_number: SEC accession in 'XXXXXXXXXX-YY-NNNNNN' format.\n\n Returns:\n JSON for the filing if found in our archive, or {\"found\": false}.\n ",
"inputSchema": {
"type": "object",
"title": "get_filingArguments",
"required": [
"accession_number"
],
"properties": {
"accession_number": {
"type": "string",
"title": "Accession Number"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_13d_filings",
"description": "Search recent SEC Schedule 13D / 13G filings from the past 72 hours.\n\n Args:\n activist: Filter to filings tagged with this activist filer name.\n Substring match, case-insensitive. Examples: 'Saba', 'Starboard',\n 'Icahn', 'Elliott', 'Pershing'.\n min_percent: Minimum percent of class disclosed.\n include_amendments: Include 13D/A and 13G/A amendments. Default True.\n include_passive_13g: Include passive Schedule 13G filings. Default False\n ",
"inputSchema": {
"type": "object",
"title": "search_13d_filingsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 25
},
"activist": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Activist",
"default": null
},
"min_percent": {
"anyOf": [
{
"type": "number"
},
{
"type": "null"
}
],
"title": "Min Percent",
"default": null
},
"include_amendments": {
"type": "boolean",
"title": "Include Amendments",
"default": true
},
"include_passive_13g": {
"type": "boolean",
"title": "Include Passive 13G",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_8k_filings",
"description": "Search recent SEC 8-K filings (current report) from the past 72 hours.\n\n Args:\n items: Comma-separated 8-K item codes to filter on. Examples: '1.05'\n (cybersecurity), '5.02' (officer departure), '8.01' (other events),\n '1.01' (material agreement). Leave None for all 8-Ks.\n suspected_buried_only: If True, return only filings where our\n body-text classifier flagged a suspected misclassification —\n i.e. cyber language under Item 8.01 that",
"inputSchema": {
"type": "object",
"title": "search_8k_filingsArguments",
"properties": {
"items": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Items",
"default": null
},
"limit": {
"type": "integer",
"title": "Limit",
"default": 25
},
"suspected_buried_only": {
"type": "boolean",
"title": "Suspected Buried Only",
"default": false
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.filingfirehose/firehose"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.filingfirehose/firehose"}) over MCP.
search_13d_filings ~294 tokenssearch_atm_offerings ~255 tokenssearch_8k_filings ~242 tokensget_filing ~163 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.filingfirehose%2Ffirehose?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.filingfirehose%2Ffirehose?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.filingfirehose%2Ffirehose.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.filingfirehose%2Ffirehose.svg :target: https://glimind.com/server/mcp-registry%2Fcom.filingfirehose%2Ffirehose?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f7693051090c8377…, first seen 2026-10-17, included at leaf 6699 of 36,176. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 00:44 UTC, the Filingfirehose Firehose MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 80.5% of Glimind's liveness checks. It had 228 outages in 90 days, with a median recovery of 15 minutes.
Filingfirehose Firehose MCP server advertises 8 tools, including get_filing, recent_13d, recent_8k, recent_atm, search_13d_filings.
Point your MCP client at this streamable-http endpoint: https://filingfirehose.com/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.