Beagle Security vs TLS Radar
Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). TLS Radar is an MCP server published by tlsradar.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  TLS Radar |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:4be5e4ae4369 Forks (GitHub): 0 Pulls (Docker Hub): 35 086 Stars (Docker Hub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.1 Forks (GitHub): 0 Stars (GitHub): 3 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 | TLS Radar |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 3 (better) |
| Pulls (Docker Hub) (differs) | 35 086 | No figure on Docker Hub |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/beagle-security-mcp-server) | Remote server (tlsradar.com/api/v1/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 | MIT | MIT |
| Repository (differs) | github.com/beaglesecurity/beagle-security-mcp-server | github.com/tls-radar/tlsradar-claude-plugin |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (5 days 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.
TLS Radar
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
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)
TLS Radar As a remote MCP server
claude mcp add --transport http tlsradar https://tlsradar.com/api/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TLS Radar has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of TLS Radar publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of TLS Radar publish no settings it asks for, so we do not compare settings.
What it can do: Beagle Security · What it can do: TLS Radar · 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.