Hoverfly vs johto.data FAA Drone Data
Hoverfly is an MCP server published by kapishmalik. Marketplaces we read that list it: 1 (Docker MCP Catalog). johto.data FAA Drone Data is an MCP server published by johtodata.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  johto.data FAA Drone Data |
|---|---|---|
| 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: 1.0.2 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) 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 | johto.data FAA Drone Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 | 0 (last published figure) |
| Forks (GitHub) (differs) | 3 | 0 (last published figure) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (kapish88/hoverfly-mcp-server) | Remote server (mcp.apify.com) |
| 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/johtodata/johto-data-api |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-22 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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.
johto.data FAA Drone Data
Fresh, clean FAA drone data: Part 107 waivers and FRIA Remote ID sites as rows, with FAA doc links.
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-serverjohto.data FAA Drone Data
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only johto.data FAA Drone Data has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of johto.data FAA Drone Data 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: johto.data FAA Drone Data · 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.