Ext Ops Panel
Open dashboard
Comparison

Firewalla vs app.deviceshelf/deviceshelf-server

Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 1 (Docker MCP Catalog). app.deviceshelf/deviceshelf-server is an MCP server published by deviceshelf.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceFirewallaapp.deviceshelf/deviceshelf-server
Docker MCP Catalog Listed
Version: sha256:af186f868759
Forks (GitHub): 13
Pulls (Docker Hub): 31 051
Stars (Docker Hub): 0
Stars (GitHub): 39
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.9.82
No figure published
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 app.deviceshelf/deviceshelf-server
FactFirewallaapp.deviceshelf/deviceshelf-server
Marketplaces that list it11
Stars (GitHub) (differs)39No figure on GitHub
Pulls (Docker Hub) (differs)31 051No figure on Docker Hub
Forks (GitHub) (differs)13No figure on GitHub
Last release (differs)Not published2026-10-24
Where it runs (differs)On your machine (mcp/firewalla-mcp-server)On your machine (ghcr.io/wealthwallet/deviceshelf-server:1.9.82)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)12, secrets among them: 11, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/amittell/firewalla-mcp-serverNot stated
Changes in the last 7 days (differs)06
First seen2026-10-112026-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

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.

app.deviceshelf/deviceshelf-server

In its own words, on Official MCP Registry:

Query and troubleshoot your local network in plain language: 37 tools, strictly local, no cloud.

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)

app.deviceshelf/deviceshelf-server

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.

Tools each declares

The marketplaces of app.deviceshelf/deviceshelf-server publish no list of tools, so we do not compare tools.

Settings each asks for

Only Firewalla asks for

  • FIREWALLA_BOX_ID
  • FIREWALLA_MSP_ID
  • FIREWALLA_MSP_TOKEN (secret)
  • LOG_LEVEL
  • MCP_CACHE_ENABLED
  • MCP_CACHE_TTL
  • MCP_DEBUG_MODE
  • MCP_RATE_LIMIT_MAX_REQUESTS
  • MCP_RATE_LIMIT_WINDOW
  • MCP_READ_ONLY_MODE
  • MCP_WAVE0_ENABLED
  • NODE_ENV

Only app.deviceshelf/deviceshelf-server asks for

  • DEVICESHELF_API_PORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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