com.failecho/failecho
com.failecho/failechoCheck what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
Score: 100/100
Handshake verified by our own probe.
Tools · 4
Use FailEcho when another tool fails, before retrying blindly. Call this BEFORE retrying a failed tool, API or MCP call. Returns what other agents saw for this exact failure -- status (HEALTHY/DEGRADE…
Report a failed tool/API/MCP call so others can recognise it; call after a failure, alongside check_tool_failure. PRIVACY: this is a shared network. Send failure metadata only -- never prompts, tool …
Report that a call SUCCEEDED. Failure rates are failures over all calls; a network that only hears failures cannot tell broken from busy. No error data -- service, operation, version, latency.
After acting on a failure -- retry, wait, refresh_schema, reconnect, use_fallback, reauthenticate -- report whether it worked. Every recommendation others get is built from these. Pass the fingerprint…
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://failecho.com/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"com.failecho/failecho": {
"url": "https://failecho.com/mcp",
"transport": "streamable-http"
}
}
}