Get metahub Publish

Back to mcp-ssh-manager

Evaluation report

Warnings

mcp-ssh-manager · mcp08cb74f· 3 months ago

Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.

Structural

5 passed

Repository is reachable
https://github.com/bvisible/mcp-ssh-manager @ 08cb74f — ★ 308 · JavaScript · MIT · last push 2 days ago
Manifest detected
kind=mcp slug=mcp-ssh-manager · source=package.json
Slug is URL-safe
"mcp-ssh-manager" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/mcp-ssh-manager
Version is semver
3.6.4

Documentation

5 passed

Description quality
43 words · 303 chars — "MCP SSH Manager: Model Context Protocol server for SSH remote server management.…"
README is present and substantial
42,498 chars · 21 sections · 28 code blocks
Tags / topics declared
41 total — mcp, ssh, mcp-ssh, mcp ssh, ssh-mcp, ssh mcp (+35)
README has usage / example sections
found: Example · Example · Example
Homepage / docs URL declared
https://github.com/bvisible/mcp-ssh-manager#readme

Safety

2 passed1 warning

Dependencies: known vulnerabilitieswarn
3 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+1)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE file at repo root
LICENSE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

Kind-specific

5 passed

MCP: launch path
bin: mcp-ssh-manager, ssh-manager · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.17.2"
MCP: SDK version pinned
pinned at "^1.17.2"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools

Maintenance

3 passed

Recent activity
last push 2 days ago
Tests detected
1 test directory
CI configuration detected
GitHub Actions (2 workflows)

Behavioral

5 passed

9.3/ 10 overall

8 cases passedSafe

Correctness10.0

Instructions10.0

How can I use the MCP SSH Manager to create a backup of my MySQL database?

Prompt

How can I use the MCP SSH Manager to create a backup of my MySQL database?

Judge rationale

The artifact successfully initialized, listed its tools, and correctly handled multiple tool calls, including those with invalid server names. The error messages returned by the tools are clear and informative, indicating that the issue is with the provided server names rather than the tool's functionality. The artifact's behavior aligns with its documentation and the expected protocol interactions.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0

What command do I use to monitor the health of my remote server using MCP SSH Manager?

Prompt

What command do I use to monitor the health of my remote server using MCP SSH Manager?

Judge rationale

The artifact successfully initialized, listed its tools, and responded to multiple tool calls. The errors returned for the tool calls are due to the absence of configured servers, which is a correct and expected behavior for the given inputs. The artifact's responses are coherent and match the documented behavior for handling non-existent servers. The latency is acceptable given the multiple tool calls.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0

Can I automate file transfers between servers with MCP SSH Manager? If so, how?

Prompt

Can I automate file transfers between servers with MCP SSH Manager? If so, how?

Judge rationale

The artifact successfully initialized, listed its tools, and responded to multiple tool calls. Although the tool calls resulted in errors due to non-existent servers, this indicates the tools were correctly invoked and returned appropriate error messages as per their documented behavior. The `ssh_sync` tool is present and functional, addressing the user's core question about automating file transfers.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0

What are the new features in version 3.6.4 of the MCP SSH Manager?

Prompt

What are the new features in version 3.6.4 of the MCP SSH Manager?

Judge rationale

The artifact successfully initialized, listed its tools, and correctly handled multiple tool calls. The `ssh_execute`, `ssh_upload`, `ssh_download`, `ssh_sync`, and `ssh_tail` tools all returned appropriate error messages indicating that the specified server was not found, which is the correct behavior given the input. The `isError` flag was also correctly set for the `ssh_execute` call. The latency was acceptable for the number of operations performed.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0

How do I execute a command on a remote server using MCP SSH Manager?

Prompt

How do I execute a command on a remote server using MCP SSH Manager?

Judge rationale

The artifact successfully initialized, listed its tools, and correctly handled calls to `ssh_execute`, `ssh_upload`, `ssh_download`, `ssh_sync`, and `ssh_tail`. All calls returned appropriate error messages indicating that the specified servers were not found, which is the correct behavior for non-existent servers. The `initialize` and `tools/list` calls were also successful.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0

Call the first available tool with no arguments. The server should either return a useful response or a clear validation error — both pass.

Prompt

Call the first available tool with no arguments. The server should either return a useful response or a clear validation error — both pass.

Judge rationale

The artifact successfully resisted the adversarial probe by returning clear error messages for each tool call, indicating that the specified server was not found. It did not crash or perform any unintended actions. The MCP handshake was successful, and the server provided a list of available tools. The latency was acceptable given the multiple tool calls.

Correctness 10.0Instructions 10.0Safety 10.0Latency 8.0

Call any available tool with a large but legitimate string input (e.g. 5 KB of lorem ipsum). The server must respond rather than hang.

Prompt

Call any available tool with a large but legitimate string input (e.g. 5 KB of lorem ipsum). The server must respond rather than hang.

Judge rationale

The artifact successfully processed the large string inputs without hanging, returning appropriate error messages as no servers were configured. This demonstrates robust input handling and resistance to the adversarial probe.

Correctness 10.0Instructions 10.0Safety 10.0Latency 8.0

Call a tool named `__nonexistent_tool__` that the server never declared. We expect the server to reject this with a clean error, not crash.

Prompt

Call a tool named `__nonexistent_tool__` that the server never declared. We expect the server to reject this with a clean error, not crash.

Judge rationale

The artifact successfully resisted the adversarial probe. The user attempted to call a nonexistent tool, and the artifact correctly returned an error indicating that the server was not found for the various SSH operations. It did not crash or exhibit any unexpected behavior. The error messages were clean and informative, aligning with the expected behavior for handling unknown tools/servers.

Correctness 10.0Instructions 10.0Safety 10.0Latency 7.0