Ext Ops Panel
Open dashboard
Comparison

sentry vs scientific-debugging

sentry is a plugin bundle for AI coding tools published by getsentry. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). scientific-debugging is a plugin bundle for AI coding tools published by iowarp. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacesentryscientific-debugging
Claude Code: claude-plugins-official Listed
Version: 1.4.0
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Community marketplace iowarp/clio-kit Not listed Listed
Version: 0.3.1
Forks (GitHub): 5
Stars (GitHub): 8
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

sentry vs scientific-debugging
Factsentryscientific-debugging
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)4 (worse)8 (better)
Forks (GitHub) (differs)1 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.sentry.dev/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not published
Licence (differs)MITApache-2.0
Repository (differs)github.com/getsentry/plugin-claudegithub.com/iowarp/clio-coder
Changes in the last 7 days22
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)Responded 32 h ago, requires a keyno remote endpoint we check

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

sentry

In its own words, on Claude Code: claude-plugins-official:

Sentry error monitoring integration. Access error reports, analyze stack traces, search issues by fingerprint, and debug production errors directly from your development environment.

scientific-debugging

In its own words, on Community GitHub marketplaces:

Diagnoses stalled or cross-system failures and wrong, NaN, nondeterministic, or unexpectedly slow scientific results through falsifiable hypotheses across distinct fault classes, with evidence-cited verdicts before any fix. Not for designing benchmarks or pre-registered experiments; use experiment-protocol.

How to run each

sentry As a Claude Code plugin

Claude Code
/plugin install sentry@claude-plugins-official

scientific-debugging As a Claude Code plugin

Claude Code
/plugin marketplace add iowarp/clio-kit
/plugin install scientific-debugging@clio-kit

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

Only sentry 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: sentry · What it can do: scientific-debugging · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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