Failecho MCP Server

What the code does

We read the source, 51 min ago · tools taken from the live server · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        subprocess.run(["mkfs.ext4", "-q", "-F", "-O", "^has_journal", scratch],

        self.dir = os.path.join(RUN_DIR, self.id)

    subprocess.call(list(argv), stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

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

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

[mcp_servers.failecho]
url = "https://failecho.com/mcp"

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

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

This one needs environment variables set before it will start: FAILECHO_URL (Network to relay to. Defaults to https://failecho.com/mcp; point it at your own server if you self-host.), FAILECHO_REPORTER_ID (Optional stable id for your agent. Salted and hashed on arrival; lets FailEcho tell your evidence from someone else's.). The author declared them in the registry entry; get the values from the project itself.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints