# com.failecho/failecho (pypi · failecho-mcp)

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

- Trust score: 47/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `failecho.com`: 70/100, [markdown](https://verifymcp.io/servers/com-failecho-failecho/failecho.md), [page](https://verifymcp.io/servers/com-failecho-failecho/failecho)
- npm · `failecho-mcp`: 40/100, [markdown](https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp.md), [page](https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp)
- pypi · `failecho-mcp`: 47/100 (this document), [markdown](https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2.md), [page](https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2)

## Channel facts

- Registry: `pypi`
- Package: `failecho-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package declared that it provides tools, but our sandbox run could not list them.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 3 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the com.failecho/failecho MCP server?

com.failecho/failecho runs locally as a PyPI package, launched with uvx failecho-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-failecho-failecho -- uvx failecho-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-failecho-failecho": {
      "command": "uvx",
      "args": [
        "failecho-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-failecho-failecho": {
      "command": "uvx",
      "args": [
        "failecho-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-failecho-failecho -- uvx failecho-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-failecho-failecho": {
      "type": "local",
      "command": [
        "uvx",
        "failecho-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-failecho-failecho --command uvx --arg failecho-mcp
```

### Hermes

```yaml
mcp_servers:
  com-failecho-failecho:
    command: "uvx"
    args: ["failecho-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-failecho-failecho": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "failecho-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-failecho-failecho -t stdio -c uvx -a failecho-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-failecho-failecho": {
      "command": "uvx",
      "args": [
        "failecho-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 47, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-14 (score 44, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 29)

First indexed and scored.

## MCP tools (0)

The sandbox run completed and this package exposed no tools.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2#diagnostics

## Score history

- 2026-09-21: 47
- 2026-09-20: 44
- 2026-09-19: 44
- 2026-09-18: 44
- 2026-09-17: 44
- 2026-09-16: 44
- 2026-09-15: 44
- 2026-09-14: 44
- 2026-09-13: 29

## Common questions

### What is the com.failecho/failecho MCP server?

com.failecho/failecho is an MCP server listed in the public MCP registry as com.failecho/failecho. Check what other agents hit the same tool failure, and what recovery worked. Ask before retrying. This page covers its PyPI package (failecho-mcp).

### Is the com.failecho/failecho MCP server safe to use?

com.failecho/failecho scores 47 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.failecho/failecho MCP server expose?

com.failecho/failecho exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

### Is the com.failecho/failecho MCP server still maintained?

com.failecho/failecho is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the com.failecho/failecho MCP server under?

com.failecho/failecho declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/failecho-mcp/
- Socket report: https://socket.dev/pypi/package/failecho-mcp
- Repository: https://github.com/FailEcho/failecho
- Website: https://failecho.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/com-failecho-failecho/failecho-mcp-2