Firewalla vs particle-webhooks
Firewalla is an MCP server published by amittell. Marketplaces we read that list it: 2 (Docker MCP Catalog, npm registry (MCP servers)). particle-webhooks is a plugin bundle for AI coding tools published by Hookdeck. 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
| Marketplace |   Firewalla | |
|---|---|---|
| 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 hookdeck/webhook-skills | Not listed | Listed Version: not stated Forks (GitHub): 17 Stars (GitHub): 98 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 | Firewalla | particle-webhooks |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 39 (worse) | 98 (better) |
| Pulls (Docker Hub) (differs) | 31 358 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 13 (worse) | 17 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/firewalla-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 12, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/amittell/firewalla-mcp-server | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-06 |
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
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.
particle-webhooks
Receive and authenticate Particle (IoT device cloud) webhooks. Use when setting up a Particle webhook integration endpoint, checking a custom Authorization or secret header, debugging 401s, parsing form-encoded or JSON device events, or handling events published from device firmware such as temperature and motion-detected.
How to run each
Firewalla As a local MCP server: Docker image
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-serverRequires: FIREWALLA_MSP_TOKEN (secret)
particle-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install particle-webhooks@webhook-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of particle-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of particle-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Firewalla · What it can do: particle-webhooks · 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.