Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

NPM · @ROOTPILOT/MCP-SSH-DIAGNOSE

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

0 this week 81 Trust /100

Last scanned (7 hours ago)

Scores higher than 69% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 34 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability88
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 292 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 23 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 18 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@rootpilot/mcp-ssh-diagnose@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 100 packages
Packages resolved 100
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~292 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
collect ~84

Run up to 8 whitelisted commands on a host and return their (redacted, truncated) output. Use get_whitelist to see valid keys. Keys outside the whitelist are rejected.

NameTypeReqDescription
containerstring–container name, required by container-scoped keys
hoststringyeshost name from list_hosts
keysarrayyeswhitelisted command keys

No output schema declared.

No examples provided.

collect_base ~58

Shortcut: run the base group (docker_ps, df, df_inode, free, uptime, dmesg_oom, docker_daemon) — a cheap first look at a host.

NameTypeReqDescription
hoststringyeshost name from list_hosts

No output schema declared.

No examples provided.

container_deep_dive ~55

Shortcut: for one container, run docker_logs, docker_inspect (redacted), container_state and docker_stats.

NameTypeReqDescription
containerstringyescontainer name
hoststringyeshost name from list_hosts

No output schema declared.

No examples provided.

get_whitelist ~45

Return every command this server can run: key, purpose, shell template, and whether it needs a container argument. This is the complete set — nothing outside it can be executed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_hosts ~50

List the hosts defined in your hosts.json, with an optional reachability probe (TCP + SSH banner). Returns names to use with the other tools.

NameTypeReqDescription
probeboolean–also test SSH reachability

No output schema declared.

No examples provided.

Install

How do I install the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server?

io.github.Easton-OU/rootpilot-ssh-diagnose runs locally as an npm package, launched with npx -y @rootpilot/mcp-ssh-diagnose. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @rootpilot/mcp-ssh-diagnose

# add to Claude Code
claude mcp add easton-ou-rootpilot-ssh-diagnose -- npx -y @rootpilot/mcp-ssh-diagnose
Common questions

What is the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server?

io.github.Easton-OU/rootpilot-ssh-diagnose is an MCP server listed in the public MCP registry as io.github.Easton-OU/rootpilot-ssh-diagnose. Read-only SSH server diagnostics via a fixed 38-command whitelist; secrets redacted, no write path. This page covers its npm package (@rootpilot/mcp-ssh-diagnose).

Is the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server safe to use?

io.github.Easton-OU/rootpilot-ssh-diagnose scores 81 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server expose?

io.github.Easton-OU/rootpilot-ssh-diagnose exposes 5 tools: list_hosts, get_whitelist, collect, collect_base, container_deep_dive. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.

Is the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server still maintained?

io.github.Easton-OU/rootpilot-ssh-diagnose is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Easton-OU/rootpilot-ssh-diagnose MCP server under?

io.github.Easton-OU/rootpilot-ssh-diagnose declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.