Safe Ssh MCP Server

safe-ssh-mcp PyPI v0.1.14

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

A secure and scoped SSH MCP server for executing safe read-only diagnostic commands over SSH

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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
A Why this grade threat 100 − adoption risk = 99/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 − 1 = 99. 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
−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 1

low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/test_run_ssh_command.py)MTC-SRC-006

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_run_ssh_command.py:54`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: key_file = tmp_path / "id_rsa" key_file.write_text("fake-key") mocker.patch("mcp_ssh.os.path.expanduser

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_run_ssh_command.py

Tools 24

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

  • get_crontab_tasksno sensitive capability
  • get_current_datetimeno sensitive capability
  • get_disk_freeno sensitive capability
  • get_disk_usageno sensitive capability
  • get_distroname_versionno sensitive capability
  • get_dmesgno sensitive capability
  • get_docker_ps_allno sensitive capability
  • get_free_memoryno sensitive capability
  • get_inode_usageno sensitive capability
  • get_is_installedno sensitive capability
Show 14 more tools ↓
  • get_list_of_filesno sensitive capability
  • get_list_of_files_with_filterno sensitive capability
  • get_listening_socketsno sensitive capability
  • get_lsblkno sensitive capability
  • get_memory_pressureno sensitive capability
  • get_ps_aux_top_cpu_consumersno sensitive capability
  • get_ps_aux_top_mem_consumersno sensitive capability
  • get_service_logs_from_journalctlno sensitive capability
  • get_systemd_list_allno sensitive capability
  • get_systemd_list_failedno sensitive capability
  • get_systemd_list_timersno sensitive capability
  • get_systemd_statusno sensitive capability
  • get_topno sensitive capability
  • get_uptimeno sensitive capability

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.14 latest A 99/100 1 1.12.1 2026-07-27

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

Use the free API → How scoring works

More in Analytics & Monitoring