MCP.Market

Remote SSH MCP server

by the-nine-nation·io.github.the-nine-nation/remote-ssh-mcp·v0.2.0·1 stars
No reviews yet

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

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed Remote SSH yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Remote SSH tools (7, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • ssh_close

    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.

  • ssh_hosts

    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.

  • ssh_interruptwrite action

    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.

  • ssh_list

    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.

  • ssh_open

    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.

  • ssh_peek

    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; l

  • ssh_runwrite action

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan23 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Remote SSH compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
34
more than 23% of 12,191 servers with a package

What its tools let an agent do: 5 read · 2 change

Install Remote SSH in Claude Code, Cursor or VS Code

Runs npx -y @zyluo/remote-ssh-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add remote-ssh-mcp -- npx -y @zyluo/remote-ssh-mcp
Add to Cursor

What the publisher says

From the Remote SSH repository's README, as published. We do not edit it. Read it on GitHub

Remote SSH MCP

Persistent, stateful remote Bash sessions for AI agents via the Model Context Protocol

Why · Features · How it works · Tools · Quick start · Config · Security · 简体中文

Why Remote SSH MCP?

Most agents reach remote machines like this:

bash → ssh host "cmd" → disconnect → repeat

Every call pays the same tax:

Remote SSH MCP turns a long-lived remote Bash into first-class MCP tools. One session ID keeps working directory, environment variables, and shell side effects. Open a new session when you need a clean environment.

Why pick this over one-shot ssh in bash?

Concrete gains for agent workflows (multi-step remote work: deploy, debug, build, inspect logs):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Remote SSH: common questions

Is Remote SSH MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Remote SSH safety report
How do I install Remote SSH?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Remote SSH need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Remote SSH maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v0.2.0.
How does Remote SSH compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.