Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/LusiyAvA/msawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/lusiyava/msaw/multi-ssh-agent-workspace)<a href="https://agentmods.dev/mcp/lusiyava/msaw/multi-ssh-agent-workspace"><img src="https://agentmods.dev/badge/mcp/lusiyava/msaw/multi-ssh-agent-workspace/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lusiyava/msaw/multi-ssh-agent-workspace"><img src="https://agentmods.dev/badge/mcp/lusiyava/msaw/multi-ssh-agent-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
multi-ssh-agent-workspace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "multi-ssh-agent-workspace": { "command": "uvx", "args": [ "multi-ssh-agent-workspace" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 8 lines scan A e0aa82d47d8b
multi-ssh-agent-workspace is an MCP server published in the GitHub repository LusiyAvA/msaw (1 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
termcp
MCP server "termcp" as configured in open-mcp-ai/Termcp. Runs in Docker (ghcr.io/open-mcp-ai/termcp:0.2.3).
remote-ssh-mcp
Persistent stateful remote SSH sessions for AI agents via MCP + OpenSSH. Runs locally from the @zyluo/remote-ssh-mcp npm package. Needs 2 environment variables to run.
deepwiki
DeepWiki's hosted MCP server: AI-generated documentation of public GitHub repositories the agent can query. Remote server at mcp.deepwiki.com.
2native-ssh-mcp
MCP server "2native-ssh-mcp" as configured in daidaiJ/2native-ssh-mcp. Launched with https://github.com/daidaiJ/2native-ssh-mcp/releases/download/v1.7.0/2native-ssh-.
ai-ops-mcp
Ai Ops MCP server. Tools: system health check, check service, security scan. Built by MEOK AI Labs. Runs locally from the ai-ops-mcp npm package.
ssh-mcp-server
MCP server providing SSH client functionality for remote Linux server management. Runs locally from the ssh-mcp-server Python package.