Hoverfly vs Shipvo
Hoverfly is an MCP server published by kapishmalik. Marketplaces we read that list it: 1 (Docker MCP Catalog). Shipvo is an MCP server published by shipvo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  Shipvo |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:80c9fb90eb15 Forks (GitHub): 3 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.0.6 Forks (GitHub): 0 Stars (GitHub): 2 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 | Shipvo |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (kapish88/hoverfly-mcp-server) | Remote server (sim.shipvo.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| 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/shipvo/shipvo |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-31 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour ago, requires authentication |
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.
Shipvo
Open a React Native app in a simulated phone: read the screen, tap, type, set device state.
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-serverShipvo As a remote MCP server
claude mcp add --transport http shipvo https://sim.shipvo.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Shipvo has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Shipvo 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: Shipvo · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.