Suzieq vs SSH Fleet
Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). SSH Fleet is an MCP server published by inhuman. 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 |   Suzieq |  SSH Fleet |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ea9f7d06053d Forks (GitHub): 1 Pulls (Docker Hub): 33 541 Stars (Docker Hub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 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 | SSH Fleet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 541 | 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) | On your machine (ghcr.io/inhuman/mcp-ssh-fleet:0.1.5) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 6, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/povedaaqui/suzieq-mcp | github.com/inhuman/mcp-ssh-fleet |
| Changes in the last 7 days | 0 | 0 |
| 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
Suzieq
MCP Server to interact with a SuzieQ network observability instance via its REST API.
SSH Fleet
Curated ssh_probe diagnostics and single-host ssh_exec over an allowlisted SSH fleet.
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-mcpRequires: SUZIEQ_API_KEY (secret)
SSH Fleet As a local MCP server: Docker image
claude mcp add --env "SSH_FLEET_AUTH_TOKEN=<YOUR_SSH_FLEET_AUTH_TOKEN>" --transport stdio mcp-ssh-fleet -- docker run -i --rm -e SSH_FLEET_AUTH_TOKEN -v "<YOUR_INVENTORY_PATH>:/etc/ssh-fleet/inventory.yaml:ro" -v "<YOUR_KEY_PATH>:/etc/ssh-fleet/id_ed25519:ro" ghcr.io/inhuman/mcp-ssh-fleet:0.1.5Requires: SSH_FLEET_AUTH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of SSH Fleet publish no list of tools, so we do not compare tools.
Settings each asks for
Only Suzieq asks for
SUZIEQ_API_ENDPOINTSUZIEQ_API_KEY (secret)
Only SSH Fleet asks for
SSH_FLEET_AUTH_TOKEN (secret)SSH_FLEET_CMD_TIMEOUT_SECONDSSSH_FLEET_OUTPUT_CAP_BYTESSSH_FLEET_PROBE_CONCURRENCYSSH_FLEET_PROBE_MAX_HOSTSSSH_FLEET_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Suzieq · What it can do: SSH Fleet · 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.