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.Areso/safe-ssh-mcp

PYPI · SAFE-SSH-MCP

A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands

Available components

+18 this week 77 Trust /100

Last scanned (11 hours ago)

Scores higher than 70% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 21 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 Areso/safe-ssh-mcp). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-or-later).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability50
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 8488 tokens (~151/item across 56 items; 56 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 56 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

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

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.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.2.1 → 0.2.3 functional
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 +10
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → 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 Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.1.15 → 0.2.0 functional
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
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 pypi/safe-ssh-mcp@0.2.3

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Areso/safe-ssh-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Areso/safe-ssh-mcp/.github/workflows/publish.yml@refs/tags/v0.2.3
Rekor log index 3952430926
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:0dbbc28267b97e7ad51844264302183a71fbc59f9bd894456979b4561798faf6

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 21 packages
Packages resolved 21
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 56 exposed · ~8,488 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
get_service_logs_from_journalctl ~141

Gets recent journald logs for a specific systemd service. Optional since limits them to a time window: '30 min ago', '2 hours ago', 'today', 'yesterday' or 'YYYY-MM-DD HH:MM:SS' (the last `lines` entries within it are returned).

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
linesinteger––
password–––
portinteger––
servicestringyes–
since–––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_sshd_effective_config ~138

Collects the effective sshd configuration (sshd -T) from a remote Linux host via SSH. Shows the final values after defaults, includes and Match blocks are applied. Requires root, since sshd -T reads the host keys: when the login user is not root, the command is run through passwordless sudo or doas (sudo -n / doas -n).

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_systemd_list_all ~82

Lists all systemd units. USE THIS TOOL to check for running, stopped, or FAILED daemon/service/unit.

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_systemd_list_failed ~79

Lists failed systemd units. USE THIS TOOL to check for FAILED daemons/services/units.

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_systemd_list_timers ~75

Lists all systemd timers. USE THIS TOOL to check for timers.

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_systemd_status ~130

Gets the detailed status, logs, and error messages for a SPECIFIC systemd daemon/service/unit. daemon is a unit name such as nginx, sshd.service or user@1000.service: ASCII letters, digits and . - _ @ : only, starting with a letter or digit, at most 255 characters.

NameTypeReqDescription
accept_new_hostkeyboolean––
daemonstringyes–
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_top ~191

Collects top's snapshot from a remote Linux host via SSH (top -b -n 2 -d 1 -c -w 512). Takes two samples 1 second apart and returns the second one, so CPU usage is the current one (the first sample of top shows averages since boot). The output is cut to the first 30 lines: the summary and the top CPU consumers. On BusyBox hosts (Alpine), where top has no -c / -w, the output is plain `top -b -n 1`, cut to 30 lines too: its first line starts with '# BusyBox' and the columns differ.

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_uptime ~69

Collects uptime from a remote Linux host via SSH

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_vmstat ~172

Samples system activity for 4 seconds with vmstat (5 reports, 1 second apart): run queue and blocked processes (r, b), memory, swap-in/out (si, so), block I/O (bi, bo), interrupts and context switches (in, cs) and the CPU split (us, sy, id, wa, st). USE THIS TOOL to see what the host is doing right now: swapping, I/O wait, CPU saturation. The FIRST report line is the average since boot - judge the current state by the other four.

NameTypeReqDescription
accept_new_hostkeyboolean––
hoststringyes–
key_path–––
password–––
portinteger––
timeoutinteger––
userstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.Areso/safe-ssh-mcp server?

io.github.Areso/safe-ssh-mcp runs locally as a PyPI package, launched with uvx safe-ssh-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · safe-ssh-mcp

# add to Claude Code
claude mcp add areso-safe-ssh-mcp -- uvx safe-ssh-mcp
Common questions

What is the io.github.Areso/safe-ssh-mcp server?

io.github.Areso/safe-ssh-mcp is listed in the public MCP registry as io.github.Areso/safe-ssh-mcp. A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands. This page covers its PyPI package (safe-ssh-mcp).

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

io.github.Areso/safe-ssh-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. 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.Areso/safe-ssh-mcp server expose?

io.github.Areso/safe-ssh-mcp exposes 56 tools: get_disk_free, get_inode_usage, get_disk_usage, get_list_of_files, get_list_of_files_with_filter, and 51 more. Their descriptions and schemas cost roughly 8,488 tokens of context every time the server is loaded.

Is the io.github.Areso/safe-ssh-mcp server still maintained?

io.github.Areso/safe-ssh-mcp 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.Areso/safe-ssh-mcp server under?

io.github.Areso/safe-ssh-mcp declares the AGPL-3.0-or-later 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.Areso/safe-ssh-mcp server?

VerifyMCP ran 16 checks on io.github.Areso/safe-ssh-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.