ssh-mcp (blackaxgit/ssh-mcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

C
Limited view
69/100

ssh-mcp

Enables AI assistants to execute shell commands and transfer files via SFTP across remote servers using existing SSH configurations. It supports parallel execution on server groups and provides built-in safety warnings for potentially destructive commands.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

blackaxgit

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: SSH_MCP_HTTP_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSSH_MCP_LOG_FORMATFor production log aggregation, set =json to emit single-line JSON events:
configSSH_MCP_CONFIGCustom config path via environment variable
configXDG_CONFIG_HOME~/.config Honoured when searching for ssh-mcp/servers.toml (see [Config file location](#config-file-location)).
configSSH_MCP_HTTP_HOST127.0.0.1 Bind address for HTTP transport. Binding to any non-localhost value (e.g. 0.0.0.0) REQUIRES SSH_MCP_HTTP_TOKEN — startup aborts otherwise.
configSSH_MCP_HTTP_PORT8000 TCP port for HTTP transport.
🔐 secretSSH_MCP_HTTP_TOKENSSH_MCP_HTTP_HOST 127.0.0.1 Bind address for HTTP transport. Binding to any non-localhost value (e.g. 0.0.0.0) REQUIRES — startup aborts otherwise.
configSSH_MCP_HTTP_TOKEN_FILEReads the same auth env vars as the server (SSH_MCP_HTTP_TOKEN, , SSH_MCP_HTTP_AUTH) — never logs the token
configSSH_MCP_HTTP_STATELESSfalse Set to true for stateless sessions (recommended for load-balanced or serverless deployments). Default is stateful with server-side sessions.
configSSH_MCP_HTTP_ALLOWED_HOSTSComma-separated extra Host-header values the SDK's DNS-rebinding protection should permit (e.g. ssh-mcp.internal:,api.example.com:8000). Localhost aliases are always permitted.
configSSH_MCP_HTTP_AUTHSSH_MCP_HTTP_NETWORK_NO_AUTH — Magic-string escape hatch. Must equal literal I_ACCEPT_RCE_RISK to allow =none + non-localhost bind. Intentionally verbose so nobody sets it by accident.
configSSH_MCP_HTTP_NETWORK_NO_AUTHMagic-string escape hatch. Must equal literal I_ACCEPT_RCE_RISK to allow SSH_MCP_HTTP_AUTH=none + non-localhost bind. Intentionally verbose so nobody sets it by accident.
configSSH_MCP_TRANSPORThttp ssh-mcp
configSSH_MCP_TRANSFER_ROOT$XDG_DATA_HOME/ssh-mcp/transfers Directory SFTP transfers are confined to. Takes precedence over transfer_root in [settings]. See [Local path confinement](#security).
configXDG_DATA_HOMESSH_MCP_TRANSFER_ROOT $/ssh-mcp/transfers Directory SFTP transfers are confined to. Takes precedence over transfer_root in [settings]. See [Local path confinement](#security).
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — list_servers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_servers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_groups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

10/12 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 2/12 tool handlers wrap calls in try/catch (17%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/blackaxgit/ssh-mcp)](https://m8ven.ai/mcp/blackaxgit/ssh-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eec650b8fdfd1459c856390bc866045c3336fd3c
code hash: e71a0be8236cc3890492159e1f3ee2b2b743064b52ca431b6cccf5d7ce177959
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client