Suzieq vs server-healthcheck
Suzieq is an MCP server published by PovedaAqui. 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-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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ea9f7d06053d Forks (GitHub): 1 Pulls (Docker Hub): 33 585 Stars (Docker Hub): 1 Stars (GitHub): 4 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
| Fact | Suzieq | server-healthcheck |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 585 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/suzieq-mcp) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/povedaaqui/suzieq-mcp | github.com/evilfreelancer/server-healthcheck |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-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
Suzieq
MCP Server to interact with a SuzieQ network observability instance via its REST API.
server-healthcheck
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
Suzieq As a local MCP server: Docker image
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcp
Requires: SUZIEQ_API_KEY (secret)
server-healthcheck As a Claude Code plugin
/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: Suzieq · 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.