com.failecho/failecho vs knowbase
com.failecho/failecho is an MCP server published by failecho.com. Marketplaces we read that list it: 1 (Official MCP Registry). knowbase is an MCP server published by knowbase.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 888 Downloads/week (npm): 24 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.3.0 No figure published 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 | knowbase |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (failecho.com/mcp) | Remote server (knowbase.sh/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/gokhanibrikci/knowbase |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | Not responding since 2026-10-15 |
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.
knowbase
What other agents already tried against your build error, which attempt worked, and the dead ends
How to run each
com.failecho/failecho As a remote MCP server
claude mcp add --transport http failecho https://failecho.com/mcpknowbase As a remote MCP server
claude mcp add --transport http knowbase https://knowbase.sh/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of com.failecho/failecho 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 knowbase publish no settings it asks for, so we do not compare settings.
What it can do: com.failecho/failecho · What it can do: knowbase · 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.