ssh-mcp-guard
Related Servers
Alternatives to ssh-mcp-guard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect remote servers and execute only pre-defined SSH commands, with optional HTTP checks and human-approved one-time codes required for changes.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to securely inspect remote servers by listing directories, reading configuration files, and performing authorized actions through permission controls, human-in-the-loop approvals, and audit logging. It acts as a bastion that never reveals raw SSH credentials or root passwords to the model.2MIT
- AlicenseAqualityBmaintenanceEnables AI clients to operate Linux servers over SSH through user-opened, time-limited sessions without exposing passwords, providing tools for system status, logs, file reads/writes, and shell command execution with read-only and blocked-command safeguards.64MIT
- AlicenseBqualityBmaintenanceProvides policy-driven, auditable SSH access to server fleets for AI assistants with zero-trust security controls, command whitelisting, and comprehensive audit logging to safely manage infrastructure.1330Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to inspect and manage remote hosts over SSH with tiered blast-radius containment that classifies and blocks destructive commands, plus forensic post-flight assertions that verify ports, processes, files, and HTTP health. It also provides long-running background task envelopes and atomic SFTP file editing with automatic backups, unified diffs, and one-click rollback.12MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage remote servers via SSH, including command execution, multi-host batch operations, SFTP file transfer, background job handling, DevOps diagnostics, port tunneling, and safety guardrails like high-risk command blocking and read-only mode.MIT
TDQS
Scored across 4 tools
list_hosts, run_action, and submit_approved have clear boundaries: read-only vs. approval-gated execution is explicitly spelled out. The one overlap is receipts: run_action supports gate.receipts {last} while get_receipts fetches the last receipts, saves them and verifies the chain, so an agent could plausibly pick either for 'see recent activity'.
All four names are snake_case verb_noun (list_hosts, run_action, get_receipts), matching the dominant convention. submit_approved uses a past participle rather than a noun object (submit_approval would be stricter), a minor deviation in an otherwise predictable set.
Four tools map cleanly onto the workflow stages (discover hosts, run read-only actions, execute approved actions, verify receipts) with no filler. It is on the thin side of the 3-15 range and leaves little room for auxiliary operations like approval inspection.
The core loop read-only diagnostics -> approval -> execution -> auditable receipts is fully covered, including local saving and chain verification. Gaps are modest but real: there is no way to list or poll pending approvals, and host entries cannot be added or removed, only listed.