hardened-ssh-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSH_HOME | No | Only needed in the Windows edge case described in the README. Set to your user profile directory when using Git's MSYS2-based ssh client. | |
| SSH_HOST | Yes | Remote host (IP or hostname) | |
| SSH_USER | Yes | Remote username | |
| SSH_EXECUTABLE | No | SSH executable path. Defaults to 'ssh' resolved via PATH. On Windows with MSIX-packaged clients, use Git for Windows' bundled ssh.exe. | ssh |
| SSH_IDENTITY_FILE | Yes | Absolute path to your private key | |
| SSH_KNOWN_HOSTS_FILE | No | Path to known_hosts file. See the Windows note in the README if this path contains spaces. | your normal ~/.ssh/known_hosts |
| SSH_COMMAND_TIMEOUT_MS | No | Timeout in milliseconds for the command to complete. | 30000 |
| SSH_CONNECT_TIMEOUT_SECONDS | No | Connection timeout in seconds. | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run-ssh-commandA | Run exactly one command over SSH on the fixed target ubuntu@203.0.113.10 and nothing else. This tool cannot reach any other host, cannot run local commands, and cannot touch the local filesystem directly - the only thing it can ever do is relay one command over SSH to that one account on that one machine, which is fixed by whoever deployed this server, not something you (the model) can choose. Standing rule: always show the user the exact command in chat and get their explicit go-ahead BEFORE calling this tool. Call it with confirmed=false (or omit confirmed) to preview what would run without executing anything. Only call it with confirmed=true after the user has approved this specific command in this specific turn - never assume consent from an earlier, different command. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is singular and clearly described, leaving no ambiguity.
The single tool name follows a clear verb_noun pattern (run-ssh-command), and with only one tool there are no inconsistencies to evaluate.
One tool is exactly appropriate for a server whose sole purpose is to relay one command over SSH to a fixed host. Additional tools would be unnecessary and dilute the server's focus.
The tool covers all needed operations for its domain: it can preview a command without executing and execute with user confirmation. There are no obvious gaps for the stated purpose.