Ext Ops Panel
Open dashboard
Comparison

Firewalla vs fortitool

Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 2 (Docker MCP Catalog, npm registry (MCP servers)). fortitool is a plugin bundle for AI coding tools published by Ali Mosajjal. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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
MarketplaceFirewallafortitool
Docker MCP Catalog Listed
Version: sha256:af186f868759
Forks (GitHub): 13
Pulls (Docker Hub): 31 358
Stars (Docker Hub): 0
Stars (GitHub): 39
Not marked · First seen
Not listed
npm registry (MCP servers) Listed
Version: 2.1.1
Downloads/month (npm): 1 420
Downloads/week (npm): 155
Forks (GitHub): 13
Stars (GitHub): 39
Not marked · First seen
Not listed
Community marketplace mosajjal/fortitool Not listed Listed
Version: 0.1.0
Forks (GitHub): 9
Stars (GitHub): 53
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 fortitool
FactFirewallafortitool
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)39 (worse)53 (better)
Pulls (Docker Hub) (differs)31 358No figure on Docker Hub
Forks (GitHub) (differs)13 (better)9 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/firewalla-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)28Not published
Environment variables it asks for (differs)12, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/amittell/firewalla-mcp-servergithub.com/mosajjal/fortitool
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-29

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.

fortitool

In its own words, on Community GitHub marketplaces:

Decrypt and unpack supported FortiGate/FortiWiFi firmware and FAZ/FMG KVM disks, with automatic format/crypto detection. Also inspect FortiGuard PKCS#7 signatures and decrypt FortiOS config secrets. One static Go binary, no runtime OS packages.

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)

fortitool As a Claude Code plugin

Claude Code
/plugin marketplace add mosajjal/fortitool
/plugin install fortitool@fortitool

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of fortitool publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of fortitool publish no settings it asks for, so we do not compare settings.

What it can do: Firewalla · What it can do: fortitool · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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