Ssh Mcp Zlzero MCP Server

ssh-mcp-zlzero PyPI v0.1.4

Published by zhouxiangjing — 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.

SSH MCP Server (zlzero) - Model Context Protocol server for SSH remote system management

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 9

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

This server (without client built-ins) exposes a complete data-exfiltration chain: download_file → list_directory → execute_command. 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 download_file → list_directory → execute_command

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

Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" 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 execute_command

medium Tool "write_file" can modify the filesystemMTC-CAP-002

Tool "write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool write_file

medium Tool "append_file" can modify the filesystemMTC-CAP-002

Tool "append_file" can write, overwrite or delete files (keyword "append_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool append_file

medium Tool "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool delete_file

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

Tool "execute_command" 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 execute_command

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

Tool "write_file" 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 write_file

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

Tool "append_file" 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 append_file

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

Tool "delete_file" 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 delete_file

Tools 34

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

  • append_filewrites files
  • delete_filewrites files
  • download_fileingests untrusted input
  • execute_commandruns code / shell
  • list_directoryreads sensitive data
  • read_filereads sensitive data
  • upload_filenetwork egress
  • write_filewrites files
  • analyze_log_errorsno sensitive capability
  • check_disk_healthno sensitive capability
Show 24 more tools ↓
  • check_high_loadno sensitive capability
  • check_network_connectivityno sensitive capability
  • check_securityno sensitive capability
  • check_service_statusno sensitive capability
  • close_all_connectionsno sensitive capability
  • close_connectionno sensitive capability
  • execute_scriptno sensitive capability
  • find_processno sensitive capability
  • get_cpu_infono sensitive capability
  • get_disk_infono sensitive capability
  • get_file_infono sensitive capability
  • get_memory_infono sensitive capability
  • get_network_infono sensitive capability
  • get_open_portsno sensitive capability
  • get_system_logsno sensitive capability
  • get_system_overviewno sensitive capability
  • grep_fileno sensitive capability
  • kill_processno sensitive capability
  • list_configured_hostsno sensitive capability
  • list_processesno sensitive capability
  • manage_serviceno sensitive capability
  • search_filesno sensitive capability
  • tail_logno sensitive capability
  • test_connectionno 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
v0.1.4 latest B 89/100 9 1.13.0 2026-08-25

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/ssh-mcp-zlzero/badge.svg)](https://mcptrustchecker.com/registry/ssh-mcp-zlzero)
HTML
<a href="https://mcptrustchecker.com/registry/ssh-mcp-zlzero"><img src="https://mcptrustchecker.com/registry/ssh-mcp-zlzero/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ssh-mcp-zlzero/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 ssh-mcp-zlzero --online --registry pypi

Use the free API → How scoring works

More in Developer Tools