Beagle Security vs Domain Security
Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). Domain Security is an MCP server published by OrtaMarco. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Domain Security |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4be5e4ae4369 Forks (GitHub): 0 Pulls (Docker Hub): 35 038 Stars (Docker Hub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.3 Downloads/month (npm): 558 Downloads/week (npm): 176 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
| Fact | Beagle Security | Domain Security |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Pulls (Docker Hub) (differs) | 35 038 | No figure on Docker Hub |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/beagle-security-mcp-server) | On your machine (domain-security-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/beaglesecurity/beagle-security-mcp-server | github.com/ortamarco/domain-security-mcp-server |
| 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
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.
Domain Security
Audit a domain's email and web security: SPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS, WHOIS. No API keys.
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)
Domain Security As a local MCP server: npm package
claude mcp add --transport stdio domain-security-mcp-server -- npx -y domain-security-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Domain Security publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Domain Security publish no settings it asks for, so we do not compare settings.
What it can do: Beagle Security · What it can do: Domain Security · 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.