Forecall Failure KB
Known MCP tool-call failures and workarounds verified by reproduction.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://mcp.forecall.dev/mcp | registry |
|---|---|---|
| Handshake | Answers, but requires sign-in before the handshake (692 ms) | our check, 2026-10-12 |
| Registry version | 1.1.0 · active · updated 2026-10-08 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http forecall-kb https://mcp.forecall.dev/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Quiet Failures Open weekly security base rates (CC BY 4.0), plus live DMARC, takeover and WHOIS checks.
- LiquiLens — the Failure Radar Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API…
- Agent Failure Archive 186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via…
- mcp-failure-lab A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers.
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/dev.forecall/forecall-kb)<a href="https://openforallofus.com/tools/dev.forecall/forecall-kb"><img src="https://openforallofus.com/badge/dev.forecall/forecall-kb.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name dev.forecall/forecall-kb.