Kpanuragh Ssh MCP Server

@kpanuragh/ssh-mcp npm v1.0.0

Published by @kpanuragh — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for SSH access - Warp-like terminal experience

Trust grade
B
89/100
Last scanned get badge →
Trust
B · 89/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 100 − adoption risk = 89/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 11 = 89. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 12

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: sftp_download → sftp_list → ssh_exec. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow sftp_download → sftp_list → ssh_exec

high Tool "ssh_exec" exposes command/code executionMTC-CAP-001

Tool "ssh_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ssh_exec

high Tool "ssh_shell_start" exposes command/code executionMTC-CAP-001

Tool "ssh_shell_start" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ssh_shell_start

high Tool "ssh_shell_send" exposes command/code executionMTC-CAP-001

Tool "ssh_shell_send" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ssh_shell_send

high Tool "ssh_shell_read" exposes command/code executionMTC-CAP-001

Tool "ssh_shell_read" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ssh_shell_read

high Tool "ssh_shell_close" exposes command/code executionMTC-CAP-001

Tool "ssh_shell_close" appears to run shell commands or evaluate code (keyword "shell" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool ssh_shell_close

medium Unconstrained command parameter "command" on "ssh_exec"MTC-CAP-006

Tool "ssh_exec" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool ssh_exec · inputSchema.properties.command

low Mutating tool "ssh_exec" declares no destructiveHintMTC-CAP-005

Tool "ssh_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_exec

low Mutating tool "ssh_shell_start" declares no destructiveHintMTC-CAP-005

Tool "ssh_shell_start" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_shell_start

low Mutating tool "ssh_shell_send" declares no destructiveHintMTC-CAP-005

Tool "ssh_shell_send" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_shell_send

low Mutating tool "ssh_shell_read" declares no destructiveHintMTC-CAP-005

Tool "ssh_shell_read" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_shell_read

low Mutating tool "ssh_shell_close" declares no destructiveHintMTC-CAP-005

Tool "ssh_shell_close" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_shell_close

Tools 11

Each tool and what it can reach — statically extracted from the published source.

  • sftp_downloadingests untrusted input
  • sftp_listreads sensitive data
  • ssh_execruns code / shell
  • ssh_shell_closeruns code / shell
  • ssh_shell_readruns code / shell
  • ssh_shell_sendruns code / shell
  • ssh_shell_startruns code / shell
  • sftp_uploadno sensitive capability
  • ssh_connectno sensitive capability
  • ssh_disconnectno sensitive capability
Show 1 more tool ↓
  • ssh_list_sessionsno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest B 89/100 12 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kpanuragh-ssh-mcp/badge.svg)](https://mcptrustchecker.com/registry/kpanuragh-ssh-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/kpanuragh-ssh-mcp"><img src="https://mcptrustchecker.com/registry/kpanuragh-ssh-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kpanuragh-ssh-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @kpanuragh/ssh-mcp --online

Use the free API → How scoring works

Other implementations of Kpanuragh Ssh 26

Independent packages implementing the same tool, scanned with the same engine. Compare all 27 side by side →

More in Developer Tools