Ext Ops Panel
Open dashboard
Comparison

Firewalla vs johto.data FAA Drone Data

Firewalla is an MCP server published by amittell. 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-26. 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

Where each is published
MarketplaceFirewallajohto.data FAA Drone Data
Docker MCP Catalog Listed
Version: sha256:af186f868759
Forks (GitHub): 13
Pulls (Docker Hub): 31 107
Stars (Docker Hub): 0
Stars (GitHub): 39
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

Firewalla vs johto.data FAA Drone Data
FactFirewallajohto.data FAA Drone Data
Marketplaces that list it11
Stars (GitHub) (differs)390 (last published figure)
Pulls (Docker Hub) (differs)31 107No figure on Docker Hub
Forks (GitHub) (differs)130 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firewalla-mcp-server)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)12, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/amittell/firewalla-mcp-servergithub.com/johtodata/johto-data-api
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-22
Endpoint at the last check (differs)no remote endpoint we checkNot 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

Firewalla

In its own words, on Docker MCP Catalog:

Real-time network monitoring, security analysis, and firewall management through 28 specialized tools. Access security alerts, network flows, device status, and firewall rules directly from your Firewalla device.

johto.data FAA Drone Data

In its own words, on Official MCP Registry:

Fresh, clean FAA drone data: Part 107 waivers and FRIA Remote ID sites as rows, with FAA doc links.

How to run each

Firewalla As a local MCP server: Docker image

Claude Code
claude mcp add --env "FIREWALLA_MSP_TOKEN=<YOUR_FIREWALLA_MSP_TOKEN>" --transport stdio firewalla-mcp-server -- docker run -i --rm -e FIREWALLA_MSP_TOKEN mcp/firewalla-mcp-server

Requires: FIREWALLA_MSP_TOKEN (secret)

johto.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

The marketplaces of johto.data FAA Drone Data publish no settings it asks for, so we do not compare settings.

What it can do: Firewalla · 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.

Where the data comes from: how the catalog is built