SSH MCP
Capped at 70: core tools not tested (test setup); the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm ssh-mcp 2.26.0 (MIT; repo tufantunc/ssh-mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 15 tools (14 annotated by the server: 6 read-only, 8 destructive). Real calls: 0 of 3 real function calls passed. No passing real call: needs an SSH host and config (--host/--user or config.toml); we connect to no hosts. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. No passing real call: needs an SSH host and config (--host/--user or config.toml); we connect to no hosts. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 2147 tokens, cl100k estimate (15 tools, measured 2026-11-13 UTC, version 2.26.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 5 read, 2 write (state-changing), 8 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
close-session— unclassifiedlist-connections— readlist-sessions— readopen-session— unclassifiedprivileged-command— unclassifiedread-command— readread-session-output— readreload-config— unclassifiedrun-command— unclassifiedsftp-download— unclassifiedsftp-download-file— unclassifiedsftp-list— readsftp-upload— write (state-changing)sftp-upload-file— write (state-changing)signal-process— unclassified
handshake and tools listed without a recorded key or OAuth
Score 70/100 · Tools 15 · Token cost approx. 2,147 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 2.26.0 · Package ssh-mcp · Repo tufantunc/ssh-mcp
Summary: SSH MCP completed an MCP handshake without credentials and exposed 15 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 15
- Context cost
- approx. 2147 tokens, cl100k estimate (15 tools, measured 2026-11-13 UTC, version 2.26.0; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install ssh-mcp (Node 20, Linux) succeeded in 2s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 15 tools listed in 4.3s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 875 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 2147 tokens, cl100k estimate for 15 tools · about 26% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 15 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
500263058b1d: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "ssh-mcp",
"version": "2.26.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 15,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install ssh-mcp` (Node 20, Linux) succeeded in 2s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 15 tools listed in 4.3s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 875 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y ssh-mcp
Pin the version we tested
npx -y ssh-mcp@2.26.0
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"ssh-mcp": {
"command": "npx",
"args": [
"-y",
"ssh-mcp@2.26.0"
]
}
}
}Tools listed
list-connections, list-sessions, open-session, close-session, read-session-output, read-command, run-command, privileged-command, signal-process, sftp-upload, sftp-download, sftp-list, sftp-upload-file, sftp-download-file, reload-config
Quick config
{
"mcpServers": {
"ssh-mcp": {
"command": "npx",
"args": [
"-y",
"ssh-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install ssh-mcp(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (15 in our test).
{
"mcpServers": {
"ssh-mcp": {
"command": "npx",
"args": [
"-y",
"ssh-mcp"
]
}
}
}Test history
- 2026-11-13 UTC: New
Related: Best DevOps MCP servers
FAQ
Is SSH MCP deprecated?
No. ssh-mcp was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces SSH MCP?
Nothing; SSH MCP is not deprecated as of 2026-11-13 UTC.
Does SSH MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 15 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.