Hoverfly vs scenario-testing
Hoverfly is an MCP server published by kapishmalik. Marketplaces we read that list it: 1 (Docker MCP Catalog). scenario-testing is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Hoverfly |  scenario-testing |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:80c9fb90eb15 Forks (GitHub): 3 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: dbb92f1 Forks (GitHub): 8 Stars (GitHub): 97 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 | Hoverfly | scenario-testing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (worse) | 97 (better) |
| Forks (GitHub) (differs) | 3 (worse) | 8 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (kapish88/hoverfly-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/kapishmalik/hoverfly-mcp-server | github.com/2389-research/claude-plugins |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Hoverfly
A Model Context Protocol (MCP) server that exposes Hoverfly as a programmable tool for AI assistants like Cursor, Claude, GitHub Copilot, and others supporting MCP. It enables dynamic mocking of third-party APIs to unblock development, automate testing, and simulate unavailable services during integration.
scenario-testing
End-to-end testing with real dependencies - no mocks allowed; scenarios with real data are the only source of truth
How to run each
Hoverfly As a local MCP server: Docker image
claude mcp add --transport stdio hoverfly-mcp-server -- docker run -i --rm kapish88/hoverfly-mcp-serverscenario-testing As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install scenario-testing@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of scenario-testing 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: Hoverfly · What it can do: scenario-testing · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.