experiment-protocol vs Verdict QA
experiment-protocol is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
experiment-protocol is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Verdict QA is an MCP server published by ArtJack. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-05. 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 |  Verdict QA | |
|---|---|---|
| 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.93.1 Downloads/month (PyPI): 3 838 Downloads/week (PyPI): 1 067 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.93.1 Downloads/month (PyPI): 3 838 Downloads/week (PyPI): 1 067 Forks (GitHub): 0 Stars (GitHub): 4 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 · | Verdict QA |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 4 |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release (differs) | Not published | 2026-10-30 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (verdict-qa-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/artjack/verdict |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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.
-
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis....
-
verification-methodology
Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Use before declaring an artifact, implementation, or claim…
-
performance-optimization
Optimize software performance through user-journey baselines, profiling, representative benchmarks, controlled experiments, and field verification. Use when asked to make an…
-
Hypothesis-driven data analysis workflow and catalog MCP server
-
Research harness: delegate to Codex, track memory across sessions, drive the full survey→ideation→experiment→publication pipeline.
-
verification-and-validation
Prove a result is trustworthy: stability, convergence, manufactured solutions, and pre/post-flight validation.
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.
Verdict QA
Read-only MCP server over Verdict QA state: verdicts, findings, flaky quarantine, history.
How to run each
experiment-protocol
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Verdict QA As a local MCP server: PyPI package
claude mcp add --transport stdio verdict -- uvx verdict-qa-mcpCommands 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: Verdict QA · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.