Ext Ops Panel
Open dashboard
Comparison

fault-tree-analysis vs io.github.praxec/fmeca

fault-tree-analysis is a plugin bundle for AI coding tools published by dunnock. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.praxec/fmeca is an MCP server published by praxec. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
Marketplacefault-tree-analysisio.github.praxec/fmeca
Community marketplace ddunnock/claude-plugins Listed
Version: 1.0.2
Forks (GitHub): 7
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
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

fault-tree-analysis vs io.github.praxec/fmeca
Factfault-tree-analysisio.github.praxec/fmeca
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/praxec/fmeca:0.2.0)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ddunnock/claude-pluginsgithub.com/praxec/fmeca
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-12

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

fault-tree-analysis

In its own words, on Community GitHub marketplaces:

Conduct Fault Tree Analysis (FTA) for system failure analysis using Boolean logic gates. Identifies minimal cut sets, single points of failure, and failure probabilities.

io.github.praxec/fmeca

In its own words, on Official MCP Registry:

Deterministic, offline FMECA MCP server: failure modes, criticality matrix, mitigations, readiness

How to run each

fault-tree-analysis As a Claude Code plugin

Claude Code
/plugin marketplace add ddunnock/claude-plugins
/plugin install fault-tree-analysis@ddunnock-claude-plugins

io.github.praxec/fmeca As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio fmeca -- docker run -i --rm ghcr.io/praxec/fmeca:0.2.0

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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: io.github.praxec/fmeca · 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.

Where the data comes from: how the catalog is built