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.the-nine-nation/remote-ssh-mcp

NPM · @ZYLUO/REMOTE-SSH-MCP

Persistent stateful remote SSH sessions for AI agents via MCP + OpenSSH.

0 this week 81 Trust /100

Last scanned (19 hours ago)

Scores higher than 69% of npm servers

Category Cloud Infrastructure

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 895 tokens (~127/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 3 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 25 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed npm/@zyluo/remote-ssh-mcp@0.2.0

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 →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~657 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
ssh_close ~47

Close the remote shell and SSH connection, clean its private temporary directory, and invalidate the id. Close a dirty session and call ssh_open for a clean environment.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

ssh_hosts ~94

List allowed OpenSSH Host aliases discovered from the local ssh_config (and explicit allowlist). Returns only safe connection metadata: alias, hostname, user, port, proxy_jump. Never returns private keys, IdentityFile paths, agent sockets, or ProxyCommand. Pass reload=true after editing ~/.ssh/config to re-parse without restarting the MCP server. Use an alias from this list with ssh_open.

NameTypeReqDescription
reloadboolean––

No output schema declared.

No examples provided.

ssh_interrupt ~50

Send Ctrl-C to the current foreground process group and wait for the shell protocol to recover. The session is kept only when recovery is confirmed. Returns nothing_to_interrupt when idle.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

ssh_list ~46

List all live sessions with host, cwd, state, last exit code, idle time, idle-reap countdown, and connection capacity. Use this to recover valid ids; never invent one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ssh_open ~82

Open a new persistent remote bash shell for an allowed ssh_config Host alias from ssh_hosts. Each call creates a clean session with a new id. Credentials come only from local OpenSSH configuration/agent; passwords and private keys are never accepted as arguments and must not be read from disk by the model.

NameTypeReqDescription
hoststringyes–
namestring––

No output schema declared.

No examples provided.

ssh_peek ~149

Observe the current foreground command and its latest output without starting another command. When status=running, optional wait_sec (default 0) long-polls this MCP call until the command finishes or the wait expires—prefer a positive wait_sec over busy-looping. wait_sec never stops the remote command. Returns the newest lines in chronological order, limited independently for stdout and stderr; lines defaults to 50 and is capped to protect model context. Use after ssh_run returns status=running. When idle, returns immediately with cwd, last exit code, and the latest lines from the completed command.

NameTypeReqDescription
idstringyes–
linesinteger––
wait_secnumber––

No output schema declared.

No examples provided.

ssh_run ~189

Start a non-interactive command in the same persistent shell identified by id. cwd and environment changes persist. The call waits at most wait_sec (default 10 seconds); if the command is still active it returns status=running without stopping it. Commands have no automatic execution timeout by default. Only an explicitly provided timeout_sec sends Ctrl-C at that deadline. Never retry a running command: poll with ssh_peek(wait_sec=...) so the MCP call blocks until idle or the wait expires; do not spam peeks with wait_sec=0. Call ssh_interrupt to stop it, or open another session for concurrent work. Only one foreground command may run per id. Do not use vim, top, password prompts, or other interactive TUI/input flows.

NameTypeReqDescription
commandstringyes–
idstringyes–
timeout_secnumber––
wait_secnumber––

No output schema declared.

No examples provided.

Install

How do I install the io.github.the-nine-nation/remote-ssh-mcp server?

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

npm · @zyluo/remote-ssh-mcp

# add to Claude Code
claude mcp add the-nine-nation-remote-ssh-mcp -- npx -y @zyluo/remote-ssh-mcp
Common questions

What is the io.github.the-nine-nation/remote-ssh-mcp server?

io.github.the-nine-nation/remote-ssh-mcp is listed in the public MCP registry as io.github.the-nine-nation/remote-ssh-mcp. Persistent stateful remote SSH sessions for AI agents via MCP + OpenSSH. This page covers its npm package (@zyluo/remote-ssh-mcp).

Is the io.github.the-nine-nation/remote-ssh-mcp server safe to use?

io.github.the-nine-nation/remote-ssh-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.the-nine-nation/remote-ssh-mcp server expose?

io.github.the-nine-nation/remote-ssh-mcp exposes 7 tools: ssh_hosts, ssh_open, ssh_run, ssh_peek, ssh_interrupt, and 2 more. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

Is the io.github.the-nine-nation/remote-ssh-mcp server still maintained?

io.github.the-nine-nation/remote-ssh-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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.the-nine-nation/remote-ssh-mcp server under?

io.github.the-nine-nation/remote-ssh-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.