Beagle Security vs scan.mx Email Diagnostics
Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). scan.mx Email Diagnostics is an MCP server published by scan.mx. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4be5e4ae4369 Forks (GitHub): 0 Pulls (Docker Hub): 35 020 Stars (Docker Hub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 No figure published 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 | scan.mx Email Diagnostics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 35 020 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/beagle-security-mcp-server) | Remote server (api.scan.mx/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| 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 | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 11 h ago |
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.
scan.mx Email Diagnostics
Email deliverability check: MX, SPF, DKIM, DMARC, blacklists, MTA-STS, DNSSEC, BIMI. Graded, no key.
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)
scan.mx Email Diagnostics As a remote MCP server
claude mcp add --transport http diagnostics https://api.scan.mx/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only scan.mx Email Diagnostics has a remote endpoint we check. How we check endpoints
Tools each declares
Only Beagle Security has
beagle_create_applicationbeagle_create_projectbeagle_delete_applicationbeagle_delete_projectbeagle_get_applicationbeagle_get_domain_signaturebeagle_get_test_resultbeagle_get_test_statusbeagle_list_applicationsbeagle_list_projectsbeagle_list_running_testsbeagle_list_test_sessions
Show the remaining 5
beagle_modify_applicationbeagle_modify_projectbeagle_start_testbeagle_stop_testbeagle_verify_domain
Only scan.mx Email Diagnostics has
check_bimicheck_blacklistcheck_dkimcheck_dmarccheck_dnsseccheck_domaincheck_mta_stscheck_mxcheck_spf
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (scan.mx Email Diagnostics as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of scan.mx Email Diagnostics publish no settings it asks for, so we do not compare settings.
What it can do: Beagle Security · What it can do: scan.mx Email Diagnostics · 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.