experiment-protocol vs SmartBear MCP
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. SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-12. 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 |  SmartBear 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 |
| 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.43.0 Downloads/month (npm): 43 513 Downloads/week (npm): 13 019 Forks (GitHub): 50 Stars (GitHub): 44 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:8a64acae01b6 Forks (GitHub): 50 Pulls (Docker Hub): 15 362 Stars (Docker Hub): 0 Stars (GitHub): 44 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 · | SmartBear MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 44 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 15 362 |
| Forks (GitHub) (differs) | 5 | 50 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 160 |
| Environment variables it asks for (differs) | Not published | 17, secrets among them: 10 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/smartbear/smartbear-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (12 h ago) |
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....
-
Research technical approaches, run bounded comparisons, and deliver reusable code with reproducible tests and configurable autonomy.
-
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.
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.
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
How to run each
experiment-protocol
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SmartBear MCP As a remote MCP server
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRequires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SmartBear MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of experiment-protocol publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of experiment-protocol publish no settings it asks for, so we do not compare settings.
What it can do: experiment-protocol · What it can do: SmartBear 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 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.