experiment-protocol vs Chrome DevTools MCP
experiment-protocol is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
experiment-protocol is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Chrome DevTools MCP is an MCP server published by ChromeDevTools. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot, Community GitHub marketplaces, Claude Code: claude-plugins-community). 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 | ||
|---|---|---|
| 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: 1.11.0 Downloads/month (npm): 7 493 150 Downloads/week (npm): 1 060 392 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 1.11.0 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 1.0.1 Forks (GitHub): 6 984 Stars (GitHub): 53 815 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.6.0 Forks (GitHub): 6 984 Stars (GitHub): 53 815 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 | experiment-protocolno longer listed · | Chrome DevTools MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 5 |
| Stars (GitHub) (differs) | 8 | 53 815 |
| Forks (GitHub) (differs) | 5 | 6 984 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (chrome-devtools-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 8 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/chromedevtools/chrome-devtools-mcp |
| Changes in the last 7 days (differs) | 4 | 16 |
| 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 experiment-protocol
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Hypothesis-driven data analysis workflow and catalog MCP server
-
A research companion based on Karl Popper's philosophy of falsification that interrogates your hypotheses to find what would prove them wrong. It acts like an adversarial…
-
Know exactly where your system breaks before you ship. Scans codebases, traces service calls, and simulates what happens when real users hit your system. Finds bottlenecks, cost…
-
Run bounded, deterministic MCP reliability tests and generate executable regressions.
What each says it does
experiment-protocol
Pre-registers a performance study, numerical comparison, parameter sweep, or benchmark: thresholds, tolerances, environment pins, and verdict conditions locked into the validation contract before any measurement. Not for diagnosing a stalled bug; use scientific-debugging.
Chrome DevTools MCP
MCP server for Chrome DevTools
How to run each
experiment-protocol
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Chrome DevTools MCP As a local MCP server: npm package
claude mcp add --transport stdio chrome-devtools-mcp -- npx -y chrome-devtools-mcp
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: experiment-protocol · What it can do: Chrome DevTools 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/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.