Mmcp.market

Failecho MCP server

by failecho.com·com.failecho/failecho·v0.2.0
No reviews yet

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

A94/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

2 stars595 downloads/wk

Reviews

Write one

Nobody has reviewed Failecho yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Failecho tools (4)

write = sends, deletes, buys or posts
  • check_tool_failureFree

    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 recovery actions that worked with success rates, and one `recommendation` (or `skip` when nothing tried recently has worked; null when evidence is thin -- a real answer). Works on your own history before anyone else joins. Free, anonymous, stores nothing, never rate limited.

  • report_recovery_outcomeFree

    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_failure; one outcome per attempt.

  • report_tool_failureFree

    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 response bodies, headers, cookies, API keys, tokens, emails or user content. Error text is normalized server-side and the raw string discarded. A stable reporter_id (hashed, never stored raw) makes you one reporter instead of anonymous noise. Writes are rate limited per client.

  • report_tool_successFree

    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.

Public scan report

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned; 3 source files scanned25/25
  • Live reliabilityremote reachable in 536ms20/20
  • Tool poisoning4 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Failecho repository's README, as published. We do not edit it. Read it on GitHub

Failure intelligence for AI agents and autonomous software. Before you retry, check the echo.

Website · Connect an agent · API reference · Live network · llms.txt

FailEcho is a live cross-agent failure intelligence network. AI agents share privacy-safe tool failures and recovery outcomes so other agents can avoid repeating the same bad retry.

One real run of examples/liveagent/rundemo.py, paced for reading. Reproduce it with the commands in docs/record-the-demo.md.

Contents

Start here

Connect something

How it works

Run and operate it

Agent A fails.
FailEcho learns.

Agent B encounters the same failure.
It sees what actually worked for other agents.

Agent B benefits from evidence it never generated itself.

Connect in one minute

Easiest: let the agent do it. Paste this at whatever you are running -- Claude Code, Claude Desktop, Cursor, Codex, your own harness:

Read https://failecho.com/llms.txt and set yourself up to use FailEcho.

It reads the machine-readable guide and configures itself. No account, no API key, nothing to sign up for. Everything below is the same thing done by hand.

MCP endpoint

https://failecho.com/mcp

Most MCP clients take this config block:

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

In Claude Code that file is .mcp.json; Cursor uses .cursor/mcp.json and drops the type; VS Code uses .vscode/mcp.json and calls the top-level key servers. The endpoint never changes. The setup page has the table.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

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

Failecho: common questions

Is Failecho MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Failecho safety report
How do I install Failecho?
It runs remotely at failecho.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Failecho need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is Failecho maintained?
The last commit was in the last day (2026-09-19). The latest release is v0.2.0.
Is Failecho up?
100% of our last 7 checks got an answer. We check remote servers about four times a day.

More from failecho.com →