Is recent_8k working right now?
com.filingfirehose/firehose · mcp-registry/com.filingfirehose/firehose/recent_8k
Recovery track record: 207 outages in 90 days, median time-to-recovery 14 min.
Working alternatives
- sec_8k_recent io.github.pipeworx-io/sec-events
- get_8k_material_events com.stratalize/crypto
- get_recent_material_filings ai.signal8/mcp
- insider_8k io.github.pipeworx-io/insider-trading
See all live alternatives to recent_8k →
Never call a dead tool again
Agents that check Glimind first make fewer failed calls, waste fewer tokens, and auto-route around outages like this one. Add it in ~10 seconds — free, no signup:
One click:
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"
}
}
}
Or wrap your calls with the SDK: npm i glimind · pip install glimind. See how it works
FAQ
Is recent_8k working right now?
As of the latest check, recent_8k (mcp-registry/com.filingfirehose/firehose/recent_8k) has a Glimind reliability score of 49/100 (grade D) and its current verdict is "degraded" — recommendation: proceed with caution. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.
How reliable is recent_8k?
recent_8k scores 49/100 (grade D) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.
What should I do if recent_8k is down or failing?
Degraded — retry at most once with backoff and a longer timeout; line up an alternative. Use a timeout around 8193ms. Live alternatives that do a similar job: sec_8k_recent, get_8k_material_events, get_recent_material_filings, insider_8k.
What are the best alternatives to recent_8k?
Working alternatives ranked by capability similarity and live health: sec_8k_recent, get_8k_material_events, get_recent_material_filings, insider_8k. See each one's live status on Glimind.
How do I call recent_8k reliably?
Before calling, check recent_8k with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k) to get a known-good input shape, the expected output, a suggested timeout (~8193ms), and a live fallback.
Embed this live badge
Show live reliability in your README or status page. It auto-updates and links back here — copy one:
[](https://glimind.com/tool/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k?ref=badge)
<a href="https://glimind.com/tool/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k?ref=badge"><img src="https://glimind.com/v1/badge/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k.svg" alt="Glimind reliability"></a>
.. image:: https://glimind.com/v1/badge/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k.svg :target: https://glimind.com/tool/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k?ref=badge :alt: Glimind reliability
Operator of com.filingfirehose/firehose?
Claim this listing → Prove you control this server (GitHub repo, live endpoint, or DNS — automated, ~1 min) to unlock the Verified operator marker, a remediation checklist (exactly why your score is what it is + how to raise it), and owner analytics. Or just embed the badge above and improve your score by having users report real outcomes (privacy-clean) via the free SDK. Glimind is neutral and sells no tools — the score is never for sale, so the fastest path to a better score is real uptime plus real usage.
Get the data (agents)
Query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fcom.filingfirehose%2Ffirehose%2Frecent_8k. The signed reliability feed for gateways/routers: GET https://glimind.com/v1/reliability/feed.
Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-10-17T08:34:05.461Z.
This score is an automated estimate derived from safe liveness probes and privacy-clean outcomes reported by users; it may be incomplete, delayed, or inaccurate, and reflects reachability from Glimind's vantage point — not a statement of fact about the service. Glimind is not affiliated with, endorsed by, or acting for this tool or its operator; all names belong to their owners. Operator? Request a correction, or remove your server from measurement, via https://glimind.com/opt-out or [email protected] — we act promptly.