Failecho MCP server

Failecho is an MCP server with 4 tools an agent can call, among them check_tool_failure, report_recovery_outcome, report_tool_failure. It answers at https://failecho.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 3 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.

Status

Answering

Tools

Official

yes, served from failecho.com

Reliability

3 of 6 checks

Response time

254 ms

Transport

streamable HTTP

Last checked

19 October 2026

Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.

Description as the publisher wrote it.

The 4 tools Failecho offers

Tool	What it does
`check_tool_failure`	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/DEGRADED/MAJOR/INSUFFICIENT_DATA), counts, the Inputs: service, operation, error_type, error_message, error_code, version
`report_recovery_outcome`	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 from check_tool_failure or report_tool_ Inputs: fingerprint, action, successful, reporter_id
`report_tool_failure`	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 arguments, tool results, request or respo Inputs: service, operation, error_type, error_message, error_code, version
`report_tool_success`	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. Inputs: service, operation, version, schema_hash, latency_ms, reporter_id

Add Failecho to your AI client

Every block below points at https://failecho.com/mcp. Pick your client and copy.

Claude Code: one command in your terminal

claude mcp add --transport http failecho https://failecho.com/mcp

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "failecho": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://failecho.com/mcp"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "failecho": {
      "type": "http",
      "url": "https://failecho.com/mcp"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "failecho": {
      "serverUrl": "https://failecho.com/mcp"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: Failecho
version: 0.0.1
schema: v1
mcpServers:
  - name: Failecho
    type: streamable-http
    url: https://failecho.com/mcp

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "failecho": {
      "httpUrl": "https://failecho.com/mcp"
    }
  }
}

Codex CLI: MCP server config

{
  "mcpServers": {
    "failecho": {
      "type": "http",
      "url": "https://failecho.com/mcp"
    }
  }
}

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Ffailecho.com%2Fmcp&type=streamable_http&id=failecho&name=Failecho

Is Failecho up right now?

It answered our last check on 19 October 2026 in 254 ms. Over 6 checks since 10 September 2026 it answered 3. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Failecho

Monitor3 tools RECOVER — Decide Safely After a Failed Machine Action1 tools AgentRank5 tools Gtm Tools4 tools notslop8 tools Agent Enhancer Utilities0 tools

Questions about Failecho

Is there an official Failecho MCP server?

Yes. It is published by failecho.com and served from failecho.com, the vendor's own domain: https://failecho.com/mcp.

How many tools does Failecho have?

4, as returned by the server's own tools/list on 25 September 2026: check_tool_failure, report_recovery_outcome, report_tool_failure, report_tool_success.

Is Failecho down?

It answered our last check on 19 October 2026 in 254 ms. Over 6 checks since 10 September 2026 it answered 3.

How do I add Failecho to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://failecho.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Failecho need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: com.failecho. Endpoint host: failecho.com. ARD identifier: urn:air:com.failecho:mcp:failecho. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.