Beagle Security vs Abnormal Security MCP
Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). Abnormal Security MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
| Marketplace |  Beagle Security |  Abnormal Security MCP |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 0.1.3 Forks (GitHub): 12 Stars (GitHub): 59 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 | Beagle Security | Abnormal Security MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 59 (better) |
| Pulls (Docker Hub) (differs) | 35 022 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 0 (worse) | 12 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/beagle-security-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/abnormal-v0.1.3/abnormal-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/beaglesecurity/beagle-security-mcp-server | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
Beagle Security
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.
Abnormal Security MCP
Abnormal Security email threats, cases, and reporting in your terminal and your AI agents.
How to run each
Beagle Security As a local MCP server: Docker image
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-serverRequires: BEAGLE_SECURITY_API_TOKEN (secret)
Abnormal Security MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install abnormal@msp-skillsRequires: ABNORMAL_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Abnormal Security MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Beagle Security asks for
BEAGLE_SECURITY_API_TOKEN (secret)
Only Abnormal Security MCP asks for
ABNORMAL_API_TOKEN (secret)ABNORMAL_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Beagle Security · What it can do: Abnormal Security MCP · 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. 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.