Cygnus Ssh MCP Server

cygnus-ssh-mcp PyPI v1.5.1

Published by cygnussystems — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Reads a sensitive credential path or dumps the environment (src/cygnus_ssh_mcp/server.py)MTC-SRC-006

In the server's implementation (`src/cygnus_ssh_mcp/server.py:319`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: key file (e.g., ~/.ssh/id_rsa)")] = None, key_passphrase: Annotated[Optional[str], Field(description="Passphrase fo

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/cygnus_ssh_mcp/server.py

medium Tool "ssh_dir_batch_delete_files" can modify the filesystemMTC-CAP-002

Tool "ssh_dir_batch_delete_files" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool ssh_dir_batch_delete_files

low Mutating tool "ssh_dir_batch_delete_files" declares no destructiveHintMTC-CAP-005

Tool "ssh_dir_batch_delete_files" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool ssh_dir_batch_delete_files

Tools 46

Each tool and what it can reach — statically extracted from the published source.

  • ssh_dir_batch_delete_fileswrites files
  • ssh_dir_list_files_basicreads sensitive data
  • list_toolsno sensitive capability
  • ssh_archive_createno sensitive capability
  • ssh_archive_extractno sensitive capability
  • ssh_cmd_check_statusno sensitive capability
  • ssh_cmd_clear_historyno sensitive capability
  • ssh_cmd_historyno sensitive capability
  • ssh_cmd_killno sensitive capability
  • ssh_cmd_outputno sensitive capability
Show 36 more tools ↓
  • ssh_cmd_runno sensitive capability
  • ssh_conn_add_hostno sensitive capability
  • ssh_conn_connectno sensitive capability
  • ssh_conn_host_infono sensitive capability
  • ssh_conn_is_connectedno sensitive capability
  • ssh_conn_statusno sensitive capability
  • ssh_conn_verify_sudono sensitive capability
  • ssh_dir_calc_sizeno sensitive capability
  • ssh_dir_copyno sensitive capability
  • ssh_dir_deleteno sensitive capability
  • ssh_dir_list_advancedno sensitive capability
  • ssh_dir_mkdirno sensitive capability
  • ssh_dir_removeno sensitive capability
  • ssh_dir_search_files_contentno sensitive capability
  • ssh_dir_search_globno sensitive capability
  • ssh_dir_transferno sensitive capability
  • ssh_file_copyno sensitive capability
  • ssh_file_delete_line_by_contentno sensitive capability
  • ssh_file_find_lines_with_patternno sensitive capability
  • ssh_file_get_context_around_lineno sensitive capability
  • ssh_file_insert_lines_after_matchno sensitive capability
  • ssh_file_moveno sensitive capability
  • ssh_file_readno sensitive capability
  • ssh_file_replace_lineno sensitive capability
  • ssh_file_replace_line_multino sensitive capability
  • ssh_file_statno sensitive capability
  • ssh_file_transferno sensitive capability
  • ssh_file_writeno sensitive capability
  • ssh_host_disconnectno sensitive capability
  • ssh_host_listno sensitive capability
  • ssh_host_removeno sensitive capability
  • ssh_host_updateno sensitive capability
  • ssh_host_use_configno sensitive capability
  • ssh_task_killno sensitive capability
  • ssh_task_launchno sensitive capability
  • ssh_task_statusno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.1 latest A 96/100 3 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cygnus-ssh-mcp/badge.svg)](https://mcptrustchecker.com/registry/cygnus-ssh-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/cygnus-ssh-mcp"><img src="https://mcptrustchecker.com/registry/cygnus-ssh-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cygnus-ssh-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cygnus-ssh-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools