scientific-debugging vs ResiliReplay
scientific-debugging is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
scientific-debugging is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. ResiliReplay is an MCP server published by aliengineering-byte. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  ResiliReplay | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.3.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.3.2 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.1 Downloads/month (npm): 208 Downloads/week (npm): 22 Forks (GitHub): 1 Stars (GitHub): 2 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 | scientific-debuggingno longer listed · | ResiliReplay |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 2 |
| Forks (GitHub) (differs) | 5 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (resilireplay) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/aliengineering-byte/resilireplay |
| Changes in the last 7 days (differs) | 6 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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
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.
ResiliReplay
Run bounded, deterministic MCP reliability tests and generate executable regressions.
How to run each
scientific-debugging
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ResiliReplay As a local MCP server: npm package
claude mcp add --transport stdio resilireplay -- npx -y resilireplay mcp serveCommands 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: scientific-debugging · What it can do: ResiliReplay · 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.