Ext Ops Panel
Open dashboard
Comparison

io.github.Easton-OU/rootpilot-ssh-diagnose vs SSH Fleet

io.github.Easton-OU/rootpilot-ssh-diagnose is an MCP server published by Easton-OU. Marketplaces we read that list it: 1 (Official MCP Registry). 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-26. 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
Marketplaceio.github.Easton-OU/rootpilot-ssh-diagnoseSSH Fleet
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 205
Downloads/week (npm): 37
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
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

io.github.Easton-OU/rootpilot-ssh-diagnose vs SSH Fleet
Factio.github.Easton-OU/rootpilot-ssh-diagnoseSSH Fleet
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@rootpilot/mcp-ssh-diagnose)On your machine (ghcr.io/inhuman/mcp-ssh-fleet:0.1.5)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 06, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/easton-ou/rootpilot-mcpgithub.com/inhuman/mcp-ssh-fleet
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.Easton-OU/rootpilot-ssh-diagnose

In its own words, on Official MCP Registry:

Read-only SSH server diagnostics via a fixed 38-command whitelist; secrets redacted, no write path.

SSH Fleet

In its own words, on Official MCP Registry:

Curated ssh_probe diagnostics and single-host ssh_exec over an allowlisted SSH fleet.

How to run each

io.github.Easton-OU/rootpilot-ssh-diagnose As a local MCP server: npm package

Claude Code
claude mcp add --env "RP_HOSTS=<YOUR_RP_HOSTS>" --transport stdio rootpilot-ssh-diagnose -- npx -y @rootpilot/mcp-ssh-diagnose

Requires: RP_HOSTS

SSH Fleet As a local MCP server: Docker image

Claude Code
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.5

Requires: 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

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.Easton-OU/rootpilot-ssh-diagnose asks for

  • RP_HOSTS
  • RP_PROBE_URL

Only SSH Fleet asks for

  • SSH_FLEET_AUTH_TOKEN (secret)
  • SSH_FLEET_CMD_TIMEOUT_SECONDS
  • SSH_FLEET_OUTPUT_CAP_BYTES
  • SSH_FLEET_PROBE_CONCURRENCY
  • SSH_FLEET_PROBE_MAX_HOSTS
  • SSH_FLEET_TRANSPORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.Easton-OU/rootpilot-ssh-diagnose · What it can do: SSH Fleet · Compare two other plugins

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.

Where the data comes from: how the catalog is built