com.failecho/failecho vs io.github.carbaj03/retry-trace
com.failecho/failecho is an MCP server published by failecho.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.carbaj03/retry-trace is an MCP server published by carbaj03. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.failecho/failecho |  io.github.carbaj03/retry-trace |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 191 Downloads/week (npm): 66 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.failecho/failecho | io.github.carbaj03/retry-trace |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (failecho.com/mcp) | Remote server (retry.agentlife.app/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/failecho/failecho | github.com/carbaj03/retry-trace |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | Status out of date: last check 42 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.failecho/failecho
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
io.github.carbaj03/retry-trace
Inspect external HTTPS 429/503 retries with server-recorded attempts, Retry-After and arrival times.
How to run each
com.failecho/failecho As a remote MCP server
claude mcp add --transport http failecho https://failecho.com/mcpio.github.carbaj03/retry-trace As a remote MCP server
claude mcp add --transport http retry-trace https://retry.agentlife.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.carbaj03/retry-trace publish no settings it asks for, so we do not compare settings.
What it can do: com.failecho/failecho · What it can do: io.github.carbaj03/retry-trace · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.