mcp-ssh-manager tested by Argusic Runner

What the test found

Installed dependencies, passed the full npm test suite (all groups Failed: 0), passed typecheck and the project's validate.sh, and the MCP server answered initialize as mcp-ssh-manager 3.8.5 (37 tools listed) and executed commands end-to-end against a local mock SSH server with success true and code 0; only the optional Bash CLI remains unlaunchable because the container lacks the system ssh binary.

npm install + npm test (all groups Failed: 0, exit 0), typecheck and validate.sh pass. Core MCP server verified end-to-end over stdio against a local ssh2 mock SSH server: initialize answered mcp-ssh-manager 3.8.5, tools/list returned 37 tools, ssh_execute returned stdout 'mock:demo:timeout 120 sh -c 'hostname'', code 0, success true. Bash ssh-manager CLI not launched: system ssh binary absent and cannot be installed without root. npm audit: 13 vulnerabilities, EBADENGINE warnings for transitive packages wanting Node >=20; these are environment/upstream notes, not verified defects.

Argusic installed mcp-ssh-manager in 12 minutes and launched it; verification reached Verified with mock services. 1 of 2 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of mcp-ssh-manager

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.