security-watchdog vs Desktop Commander
security-watchdog is a plugin bundle for AI coding tools published by Entelligentsia. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 6 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). 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
| Marketplace |  security-watchdog |   Desktop Commander |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.2.0 Forks (GitHub): 1 263 Stars (GitHub): 10 129 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 966 995 Downloads/week (npm): 159 845 Forks (GitHub): 1 263 Stars (GitHub): 10 129 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 263 Stars (GitHub): 10 129 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:5df787069e37 Forks (GitHub): 1 263 Pulls (Docker Hub): 240 008 Stars (Docker Hub): 22 Stars (GitHub): 10 129 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 263 Stars (GitHub): 10 129 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 | security-watchdog | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 6 (better) |
| Stars (GitHub) (differs) | 3 (worse) | 10 129 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 240 008 |
| Forks (GitHub) (differs) | 1 (worse) | 1 263 (better) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@wonderwhy-er/desktop-commander) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 26 |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | 7 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/entelligentsia/skillforge | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-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
security-watchdog
> Automatic security scanner for Claude Code plugins — detects new or updated extensions at session start and scans them for prompt injection, malicious hook scripts, and data exfiltration. ## The Problem LLM extension ecosystems are a novel attack surface. Traditional security tooling does not cover two threats unique to AI extensions: - **Host attacks** — hook scripts run shell commands automatically on session start, with full user privileges - **Mind attacks** — skill and command files are injected directly into the model's reasoning context, enabling prompt injection No existing security scanner understands these threat classes. Security Watchdog is purpose-built for them. ## How It Works ``` You run: /plugin install someone/new-plugin ↓ Next session starts (SessionStart hook fires) ↓ check-new-plugins.sh diffs installed_plugins.json against a snapshot from the previous session ↓ New/updated plugin detected ↓ Injects into session context: "SECURITY WATCHDOG ALERT: forge@forge was installed. Run /scan-plu
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
security-watchdog As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install security-watchdog@claude-communityDesktop Commander As a local MCP server: npm package
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commanderCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of security-watchdog 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: security-watchdog · What it can do: Desktop Commander · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.