Ext Ops Panel
Open dashboard
Comparison

problem-definition vs culprit

problem-definition is a plugin bundle for AI coding tools published by dunnock. Marketplaces we read that list it: 1 (Community GitHub marketplaces). culprit is an MCP server published by noordeen123. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceproblem-definitionculprit
Community marketplace ddunnock/claude-plugins Not seen in the last pass
Version: 1.0.2
Forks (GitHub): 7
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 102
Downloads/week (PyPI): 49
Forks (GitHub): 1
Stars (GitHub): 6
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

problem-definition vs culprit
Factproblem-definitionculprit
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)6 (worse)
Forks (GitHub) (differs)7 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (culprit)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/ddunnock/claude-pluginsgithub.com/noordeen123/culprit
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11

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

problem-definition

In its own words, on Community GitHub marketplaces:

Guide RCCA/8D problem definition using 5W2H and IS/IS NOT analysis. Transforms failure data into precise, measurable problem statements without embedded cause or solution.

culprit

In its own words, on Official MCP Registry:

Deterministic, offline root-cause analysis and pre-commit fix verification for coding agents.

How to run each

problem-definition As a Claude Code plugin

Claude Code
/plugin marketplace add ddunnock/claude-plugins
/plugin install problem-definition@ddunnock-claude-plugins

culprit As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio culprit -- uvx --from "culprit[mcp]" culprit-mcp culprit

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: problem-definition · What it can do: culprit · 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