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.jordanburke/ssh-client-mcp-server

NPM · SSH-CLIENT-MCP-SERVER

MCP server for executing shell commands on remote hosts via SSH.

0 this week 78 Trust /100

Last scanned (12 hours ago)

Scores higher than 59% 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 Security99
  • 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
  • 9 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to jordanburke/ssh-client-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 346 tokens (~57/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 15 Nov 26 +29
    • Injection markers: unverified → pass ▲ security
    • Known CVEs: partial → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Dependency health: partial → 0.91 functional
    • Package version: 1.6.1 → 1.6.2 functional
  • 14 Nov 26 0
    • Known CVEs: pass → partial ▼ security
    • Dependency health: 0.91 → partial functional
    • Package version: 1.6.0 → 1.6.1 functional
  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 5 Nov 26 0
    • Dependency health: 0.84 → 0.91 ▲ functional
    • Package version: 1.5.1 → 1.6.0 functional
  • 12 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 22 Nov 2026 · Analysed npm/ssh-client-mcp-server@1.6.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo jordanburke/ssh-client-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/jordanburke/ssh-client-mcp-server/.github/workflows/publish.yml@refs/tags/v1.6.2
Rekor log index 3891947781
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:508e90321d9ac68fceb8a12db40d8a68936d7b3125158790947a35b416fa55ab4b856577da213171e0f76a06089bdf2cf36a90a4ea8ca75061ae9e24c

Background: How many MCP packages publish verified provenance →

Dependencies 34 packages
Packages resolved 34
Stale 9
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~333 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
exec ~37

Execute a shell command on the remote SSH server and return the output.

NameTypeReqDescription
commandstringyesShell command to execute on the remote SSH server

No output schema declared.

No examples provided.

info ~28

Returns identity and build information for this server (name, version, build commit, runtime, capability counts)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tmux_keys ~80

Send control/special keys to a tmux session (e.g. C-c to interrupt, Escape, Up). Use tmux_send for ordinary text.

NameTypeReqDescription
keysarrayyestmux key names, e.g. ['C-c'] or ['Escape']
sessionstring–tmux session name (defaults to --tmux-session)

No output schema declared.

No examples provided.

tmux_list ~27

List live tmux sessions on the remote host. Returns a JSON array of session names.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tmux_read ~68

Capture the recent output (pane transcript) of a tmux session on the remote host.

NameTypeReqDescription
linesinteger–Lines of scrollback to capture (default 200; capped at 2000)
sessionstring–tmux session name (defaults to --tmux-session)

No output schema declared.

No examples provided.

tmux_send ~93

Type text into a persistent tmux session on the remote host (creates the session if it does not exist). Use to dispatch work to a long-running interactive process such as a coding agent.

NameTypeReqDescription
inputstringyesText to type into the session
sessionstring–tmux session name (defaults to --tmux-session)
submitboolean–Press Enter after the text (default true)

No output schema declared.

No examples provided.

Install

How do I install the io.github.jordanburke/ssh-client-mcp-server server?

io.github.jordanburke/ssh-client-mcp-server runs locally as an npm package, launched with npx -y ssh-client-mcp-server, plus the required --host, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ssh-client-mcp-server

# add to Claude Code
claude mcp add jordanburke-ssh-client-mcp-server -- npx -y ssh-client-mcp-server

Incomplete: the registry marks --host as required and gives no value we can show, so it is not in this command. Add it before you run it.

Common questions

What is the io.github.jordanburke/ssh-client-mcp-server server?

io.github.jordanburke/ssh-client-mcp-server is listed in the public MCP registry as io.github.jordanburke/ssh-client-mcp-server. MCP server for executing shell commands on remote hosts via SSH. This page covers its npm package (ssh-client-mcp-server).

Is the io.github.jordanburke/ssh-client-mcp-server server safe to use?

io.github.jordanburke/ssh-client-mcp-server scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.jordanburke/ssh-client-mcp-server server expose?

io.github.jordanburke/ssh-client-mcp-server exposes 6 tools: info, exec, tmux_list, tmux_send, tmux_read, tmux_keys. Their descriptions and schemas cost roughly 333 tokens of context every time the server is loaded.

Is the io.github.jordanburke/ssh-client-mcp-server server still maintained?

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

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

What did VerifyMCP test on the io.github.jordanburke/ssh-client-mcp-server server?

VerifyMCP ran 15 checks on io.github.jordanburke/ssh-client-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.jordanburke/ssh-client-mcp-server: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.