Ext Ops Panel
Open dashboard
Comparison

Beagle Security vs npm-postinstall-attack-scanner

Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). npm-postinstall-attack-scanner is a plugin bundle for AI coding tools published by aliksir. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
MarketplaceBeagle Securitynpm-postinstall-attack-scanner
Docker MCP Catalog Listed
Version: sha256:4be5e4ae4369
Forks (GitHub): 0
Pulls (Docker Hub): 35 022
Stars (Docker Hub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
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

Beagle Security vs npm-postinstall-attack-scanner
FactBeagle Securitynpm-postinstall-attack-scanner
Marketplaces that list it11
Stars (GitHub)11
Pulls (Docker Hub) (differs)35 022No figure on Docker Hub
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/beagle-security-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)17Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/beaglesecurity/beagle-security-mcp-servergithub.com/aliksir/npm-postinstall-attack-scanner
Changes in the last 7 days00
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

Beagle Security

In its own words, on Docker MCP Catalog:

Connects with the Beagle Security backend using a user token to manage applications, run automated security tests, track vulnerabilities across environments, and gain intelligence from Application and API vulnerability data.

npm-postinstall-attack-scanner

In its own words, on Claude Code: claude-plugins-community:

Detect npm supply chain attacks that use the postinstall + hidden dependency pattern to deliver malware. Built in response to the axios maintainer account takeover (2026-03-31). Scans lockfiles, ode_modules, postinstall scripts, version ranges, and npm cache across 5 phases. Returns actionable remediation steps when issues are found.

How to run each

Beagle Security As a local MCP server: Docker image

Claude Code
claude mcp add --env "BEAGLE_SECURITY_API_TOKEN=<YOUR_BEAGLE_SECURITY_API_TOKEN>" --transport stdio beagle-security -- docker run -i --rm -e BEAGLE_SECURITY_API_TOKEN mcp/beagle-security-mcp-server

Requires: BEAGLE_SECURITY_API_TOKEN (secret)

npm-postinstall-attack-scanner As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install npm-postinstall-attack-scanner@claude-community

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

Tools each declares

The marketplaces of npm-postinstall-attack-scanner publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of npm-postinstall-attack-scanner publish no settings it asks for, so we do not compare settings.

What it can do: Beagle Security · What it can do: npm-postinstall-attack-scanner · Compare two other plugins

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/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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