fault-tree-analysis vs Snapback
fault-tree-analysis is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
fault-tree-analysis is a plugin bundle for AI coding tools published by dunnock. No marketplace we read lists it any more. Snapback is an MCP server published by ra1labsworkx-wq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-02. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Snapback | |
|---|---|---|
| Community marketplace ddunnock/claude-plugins | Removed on 2026-10-28 Version: 1.0.2 Forks (GitHub): 7 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.8.4 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 | fault-tree-analysisno longer listed · | Snapback |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 14 | 0 |
| Forks (GitHub) (differs) | 7 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.snapback.sh/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ddunnock/claude-plugins | github.com/ra1labsworkx-wq/snapback-selfheal |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 39 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of fault-tree-analysis
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
fmeca io.github.praxec/fmeca
Deterministic, offline FMECA MCP server: failure modes, criticality matrix, mitigations, readiness
-
misakanet io.github.Ikalus1988/misakanet
Failure-memory layer for coding agents: search evidence-rated failure lessons by error text.
-
Causal DAG analysis: backdoor paths, adjustment sets, bias simulation. Validated against dagitty.
-
A causal inference plugin for AI agents. Describe a problem in plain language and it helps you choose a method, check assumptions, write the analysis in R or Python, and…
-
thinking-frameworks
Decision and analysis frameworks including OODA, SWOT, Cynefin, Red Team, Pre-mortem, WRAP, 5 Whys, and Post-mortem
-
Complete predictive maintenance toolkit for vibration analysis, bearing/gear fault diagnosis, anomaly detection, and ISO standards compliance.
What each says it does
fault-tree-analysis
Conduct Fault Tree Analysis (FTA) for system failure analysis using Boolean logic gates. Identifies minimal cut sets, single points of failure, and failure probabilities.
Snapback
Diagnose why an AI agent failed and get the verified fix instantly. Free, no token.
How to run each
fault-tree-analysis
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Snapback As a remote MCP server
claude mcp add --transport http snapback https://api.snapback.sh/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Snapback has a remote endpoint we 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
Neither one's marketplaces publish the settings it asks for.
What it can do: fault-tree-analysis · What it can do: Snapback · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.