Server providing Argo CD integration for MCP clients.
Nothing to run from here
Simple Ssh is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
83/100
trust score
6
downloads a day
local
runs on your machine
136
downloads in 30d
What it does
MCP server for SSH/SFTP remote operations
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user simple-ssh-mcp '--' npx -y simple-ssh-mcp-server
# 2 — ask your agent for something these tools do
# ssh_container_list, ssh_container_logs, ssh_container_exec and 46 more
Simple Ssh costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BHAll 3 servers
bhayanak3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Simple Ssh as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user simple-ssh-mcp '--' npx -y simple-ssh-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
49 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Docker or Podman containers on the remote host with status, ports, and resource usage.
No parameter schema on file.
View Docker or Podman container logs with tail, time filtering, and pattern matching options.
No parameter schema on file.
Run a command inside a running Docker or Podman container on the remote host.
No parameter schema on file.
Run a command on a connected remote server and return stdout, stderr, and exit code. Requires a sessionId from ssh_connect.
No parameter schema on file.
Run a command with sudo privileges on the remote server. Password sent via stdin, never logged.
No parameter schema on file.
Start a long-running command in the background for async polling. Returns a jobId. Only use when user explicitly wants background/async execution.
No parameter schema on file.
Fetch output from a background job previously started with ssh_exec_background. Requires jobId.
No parameter schema on file.
List all active background jobs and their status for a specific session.
No parameter schema on file.
Stop/kill a background job previously started with ssh_exec_background. Requires a valid jobId — do NOT use for anything else.
No parameter schema on file.
Locate files on the remote server by name pattern (like Linux find). Use when asked to find, locate, or search for a file by name or path.
No parameter schema on file.
Search text patterns inside remote files using grep. Returns file paths, line numbers, and matching lines.
No parameter schema on file.
Show differences between two remote files as a unified diff.
No parameter schema on file.
Show the last N lines of a remote file (tail). Good for quick log inspection.
No parameter schema on file.
Compute a hash (md5/sha256/sha512) of a remote file to verify integrity.
No parameter schema on file.
Query the SSH MCP server internal audit logs. Filter by event type, session, host, or time range.
No parameter schema on file.
Execute the same command across multiple connected servers simultaneously. Requires multiple active sessionIds.
No parameter schema on file.
Copy a file from one remote server to another through this MCP server. Requires two active sessionIds.
No parameter schema on file.
SSH to a target host through an existing session used as a jump/bastion host. Creates a new session on the target.
No parameter schema on file.
Upload and execute a multi-line script (bash/python/etc.) on the remote server in one step.
No parameter schema on file.
Create SSH tunnel: forward a local port to a remote host:port through the SSH connection (SSH -L).
No parameter schema on file.
Create reverse SSH tunnel: forward a remote port back to a local host:port (SSH -R).
No parameter schema on file.
List all active SSH port forwards and tunnels.
No parameter schema on file.
Close an active SSH port forward by its forwardId.
No parameter schema on file.
Manage systemd services on the remote host: start, stop, restart, reload, enable, disable, status, or list all.
No parameter schema on file.
List, filter, or kill processes on the remote host. Find what is listening on a specific port.
No parameter schema on file.
View, add, or remove scheduled cron jobs on the remote host.
No parameter schema on file.
Network diagnostics on the remote host: listening ports, active connections, ping, DNS lookup, routes, interfaces.
No parameter schema on file.
Get user and group info from the remote host: whoami, list users, user details, group memberships.
No parameter schema on file.
REQUIRED FIRST STEP: Connect to a remote server via SSH using host, username, and password or key. Must be called before any other ssh_ tool.
No parameter schema on file.
Close and disconnect an active SSH session by its sessionId.
No parameter schema on file.
Show all active SSH connections with their host, user, and resource details.
No parameter schema on file.
Test if an SSH session is alive and measure its round-trip latency.
No parameter schema on file.
Capture a full system state snapshot: packages, services, ports, processes, cron, env, mounts, users. Use before changes to diff later.
No parameter schema on file.
Compare two system snapshots to show what changed between them (added/removed packages, services, ports, etc.).
No parameter schema on file.
Save or manage connection bookmarks. NOT for connecting to servers \u2014 use ssh_connect instead. Only for save/list/delete of saved profiles.
No parameter schema on file.
List directory contents on the remote server (like ls -la). Shows names, sizes, permissions.
No parameter schema on file.
Upload a local file to the remote server via SFTP. Validates file size limits.
No parameter schema on file.
Download a file from the remote server to the local machine via SFTP.
No parameter schema on file.
Read a remote file text content in-place without downloading. Good for configs and logs.
No parameter schema on file.
Create or overwrite a remote file with text content. Good for configs and scripts.
No parameter schema on file.
Delete a file or directory on the remote server. Recursive delete requires explicit opt-in.
No parameter schema on file.
Get file metadata: size, permissions, owner, timestamps of a remote file or directory.
No parameter schema on file.
Open an interactive PTY terminal for programs like mysql, python, or top. For simple one-off commands use ssh_exec instead.
No parameter schema on file.
Type text into an open interactive PTY terminal. Requires shellId from ssh_shell_open.
No parameter schema on file.
Read output from an open interactive PTY terminal. Requires shellId from ssh_shell_open.
No parameter schema on file.
Change dimensions of an open PTY terminal window. Requires shellId from ssh_shell_open.
No parameter schema on file.
Close an interactive PTY terminal. Requires shellId from ssh_shell_open.
No parameter schema on file.
List open PTY terminals for a specific session.
No parameter schema on file.
Get remote server system information: OS, CPU, memory, disk, network interfaces, and uptime.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Simple Ssh or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
BTrust score 83 / 100
Release 0.1.1 · scanned 13 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score94
Client score83
Findings2 threat · 25 capability
Capabilitycritical
Coveragesource
Verificationrepo
Surface digest2014612f0769ad1a532aac9a3074047a3ec20054ae8380224b017a209e87ce20
Score vectorthreat 94 → client 83
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | critical | capability blast radius (critical) — client exposure if the model is manipulated | −10 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. critical is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ssh_connect | no tags | |
| ssh_disconnect | no tags | |
| ssh_list_sessions | no tags | |
| ssh_session_ping | no tags | |
| ssh_exec | code-exec | code-exec: keyword "exec" in tool name |
| ssh_sudo_exec | code-exec | code-exec: keyword "exec" in tool name |
| ssh_exec_background | code-exec | code-exec: keyword "exec" in tool name |
| ssh_exec_poll | code-exec | code-exec: keyword "exec" in tool name |
| ssh_exec_poll_list | code-exec | code-exec: keyword "exec" in tool name |
| ssh_exec_cancel | code-exec | code-exec: keyword "exec" in tool name |
| ssh_shell_open | code-exec | code-exec: keyword "shell" in tool name |
| ssh_shell_write | code-exec | code-exec: keyword "shell" in tool name |
| ssh_shell_read | code-exec | code-exec: keyword "shell" in tool name |
| ssh_shell_resize | code-exec | code-exec: keyword "shell" in tool name |
| ssh_shell_close | code-exec | code-exec: keyword "shell" in tool name |
| ssh_shell_list | code-exec | code-exec: keyword "shell" in tool name |
| ssh_sftp_list | no tags | |
| ssh_sftp_upload | no tags | |
| ssh_sftp_download | untrusted-input | untrusted-input: keyword "download" |
| ssh_sftp_read | no tags | |
| ssh_sftp_write | no tags | |
| ssh_sftp_delete | no tags | |
| ssh_sftp_stat | no tags | |
| ssh_port_forward_local | no tags | |
| ssh_port_forward_remote | no tags | |
| ssh_port_forward_list | no tags | |
| ssh_port_forward_remove | no tags | |
| ssh_system_info | no tags | |
| ssh_get_logs | sensitive-source | sensitive-source: keyword "get_logs" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
ssh_sftp_download → ssh_get_logs → ssh_exec
A cross-tool exfiltration chain exists: ssh_sftp_download → ssh_get_logs → ssh_exec.
Supply chain and provenance
Integrityfirst-seen
Surface digest2014612f0769ad1a
Scanned2026-10-13
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.1. Pin a release below and the command asks for exactly that one.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Simple Ssh can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.