scientific-debugging vs io.github.microsoft/playwright-mcp
scientific-debugging is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
scientific-debugging is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. io.github.microsoft/playwright-mcp is an MCP server published by microsoft. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-official, Cursor: cursor/plugins, Docker MCP Catalog). As of our marketplace pass on 2026-10-19. 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 |  io.github.microsoft/playwright-mcp | |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 0.0.82 Downloads/month (npm): 31 345 222 Downloads/week (npm): 6 403 349 Forks (GitHub): 3 283 Stars (GitHub): 38 368 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: not stated Forks (GitHub): 4 548 Stars (GitHub): 42 948 Not marked · First seen |
| Cursor: cursor/plugins | Not listed | Listed Version: 1.0.0 Forks (GitHub): 1 268 Stars (GitHub): 12 913 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:8771dc4666e7 Forks (GitHub): 3 283 Pulls (Docker Hub): 2 508 393 Stars (Docker Hub): 38 Stars (GitHub): 38 368 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 · | io.github.microsoft/playwright-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 4 |
| Stars (GitHub) (differs) | 8 | 42 948 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 2 508 393 |
| Forks (GitHub) (differs) | 5 | 4 548 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@playwright/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 23 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/microsoft/playwright-mcp |
| Changes in the last 7 days (differs) | 4 | 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.
-
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…
-
misakanet io.github.Ikalus1988/misakanet
Failure-memory layer for coding agents: search evidence-rated failure lessons by error text.
-
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.
-
Read-only MCP server over Verdict QA state: verdicts, findings, flaky quarantine, history.
-
Capture, replay, and debug failures with portable, executable bug artifacts
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.
io.github.microsoft/playwright-mcp
Playwright Tools for MCP
How to run each
scientific-debugging
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.microsoft/playwright-mcp As a local MCP server: npm package
claude mcp add --transport stdio playwright-mcp -- npx -y @playwright/mcpCommands 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: scientific-debugging · What it can do: io.github.microsoft/playwright-mcp · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.