A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands
MCPpedia last refreshed this data
io.github.Areso/safe-ssh-mcp is an MCP server that a secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 85/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-areso-safe-ssh-mcp": {
"args": [
"safe-ssh-mcp"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A secured scoped SSH MCP server for executing safe read-only diagnostic DevOps / SysOps commands
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
uvx 'safe-ssh-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked safe-ssh-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops / security
MCP server for using the GitLab API
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Areso/safe-ssh-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A secure and scoped SSH MCP server for executing read-only diagnostic commands over SSH.
In this project, "safe" refers specifically to host safety: the server is designed to prevent modifications to the remote system and reduce the risk of operational harm. It does NOT attempt to guarantee that command output cannot be misused by external agents.
The core philosophy behind this MCP server is safety first. Instead of providing an AI agent with an unrestricted bash shell, this server exposes only carefully curated, read-only commands for system diagnostics and monitoring.
A few examples from each group; <...> marks a validated parameter.
Disk and filesystems
df -hfind <path> -mindepth 1 -maxdepth 1 -exec du -sh -- {} + 2>/dev/null | sort -rh | head -n 20findmnt (or cat /proc/mounts)CPU, memory and processes
top -b -n 1 -cvmstat 1 5cat /proc/pressure/{cpu,io,memory}Systemd and logs
systemctl list-units --state=failed --no-pagersystemctl status <daemon>journalctl -p warning -n <lines> --no-pagerdmesgNetwork
ss -tulpnip route show and ip -6 route showgetent ahosts <name> or dig <name> <record_type>nc -vz -w 3 <target_host> <target_port>Docker
docker ps --alldocker logs --tail <lines> <container>docker stats --no-streamKubernetes
kubectl get events --sort-by=.lastTimestampkubectl logs --tail=<lines> --namespace=<namespace> <pod>crictl ps --allSystem, logins and crashes
cat /etc/os-releasedpkg-query -W (with source package), rpm -qa or /lib/apk/db/installed (with origin)lastb -F -n <lines>coredumpctl list --no-pagerClick to open full list of available tools
okay, could u check disk usage on /root/ path with help of safe-ssh-mcp server on a remote myserver.mydomain.pro using root and /Users/myUser/.ssh/id_rsa to login?
The server supports SSH account-password authentication and private-key
authentication. Configure the private-key passphrase source in
mcp_config.ini:
# ENV_VAR (SSH_KEY_PASSPHRASE) or KEYCHAIN (ssh-agent)
ssh_key_passphrase_method=ENV_VAR
SSH account password: provide password to the MCP tool. Do not use this
for a private-key passphrase.
Unprotected SSH key: use key_path. The default ENV_VAR setting also
supports unprotected keys; SSH_KEY_PASSPHRASE is not required.
Passphrase-protected SSH key from an environment variable: leave
ssh_key_passphrase_method=ENV_VAR, set SSH_KEY_PASSPHRASE in the
environment that starts the MCP server, and provide key_path.
export SSH_KEY_PASSPHRASE='your-key-passphrase'
safe-ssh-mcp
macOS Keychain / SSH agent: set
ssh_key_passphrase_method=KEYCHAIN, then unlock the key in the same user
session that starts the MCP server. The server receives SSH signatures from
ssh-agent; it does not read the key passphrase or the key_path.
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
#