Inspektor Gadget vs scientific-debugging
scientific-debugging is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). scientific-debugging is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-28. 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 |  Inspektor Gadget | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a54c99a50a81 Forks (GitHub): 6 Pulls (Docker Hub): 13 655 Stars (Docker Hub): 2 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-kit | Not listed | Removed on 2026-10-16 Version: 0.3.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
| Community marketplace iowarp/clio-coder | Not listed | Removed on 2026-10-23 Version: 0.3.2 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
| Fact | Inspektor Gadget | scientific-debuggingno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 28 | 8 |
| Pulls (Docker Hub) (differs) | 13 655 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/inspektor-gadget) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 37 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/inspektor-gadget/ig-mcp-server | github.com/iowarp/clio-coder |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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 scientific-debugging
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
misakanet io.github.Ikalus1988/misakanet
Failure-memory layer for coding agents: search evidence-rated failure lessons by error text.
-
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
-
Agent Trace Triage is a Claude Code plugin for developers building agentic AI systems (LangGraph, CrewAI, custom tool loops, MCP agents). When an agent run fails, stuck in a loop…
-
Universal expert problem-solving agent specializing in complex debugging, mysterious runtime behavior, integration issues, and multi-layered technical challenges across any…
-
Diagnose why an AI agent failed and get the verified fix instantly. Free, no token.
-
Flaky test detection, root cause analysis, and fix suggestions for development teams.
What each says it does
Inspektor Gadget
AI interface to troubleshoot and observe Kubernetes/Container workloads.
scientific-debugging
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
Inspektor Gadget As a local MCP server: Docker image
claude mcp add --transport stdio inspektor-gadget -- docker run -i --rm mcp/inspektor-gadgetscientific-debugging
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of scientific-debugging publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Inspektor Gadget · What it can do: scientific-debugging · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.