Ext Ops Panel
Open dashboard
Comparison

Beagle Security vs server-healthcheck

Beagle Security is an MCP server published by beaglesecurity. Marketplaces we read that list it: 1 (Docker MCP Catalog). server-healthcheck is a plugin bundle for AI coding tools published by EvilFreelancer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 Securityserver-healthcheck
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
Community marketplace evilfreelancer/rpa-skills Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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 server-healthcheck
FactBeagle Securityserver-healthcheck
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Pulls (Docker Hub) (differs)35 086No 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/evilfreelancer/server-healthcheck
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-18

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.

server-healthcheck

In its own words, on Community GitHub marketplaces:

Check whether a host or a whole namespace of a fleet harness repository is healthy, read-only: a POSIX pass over boot history, clock, units, disks, OOM, containers, resolvers, ports, NVIDIA and Intel Arc GPUs and PCIe AER, drift against the host card, stacks against the mirror, and functional probes of every service, rolled up into healthy, warming up, degraded, broken or unreachable.

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)

server-healthcheck As a Claude Code plugin

Claude Code
/plugin marketplace add evilfreelancer/rpa-skills
/plugin install server-healthcheck@rpa-skills

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

Tools each declares

The marketplaces of server-healthcheck publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of server-healthcheck publish no settings it asks for, so we do not compare settings.

What it can do: Beagle Security · What it can do: server-healthcheck · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built