io.github.antonio-mello-ai/mcp-proxmox

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  pass25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  Scanned 186 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "create_container" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "configure_cloud_init" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  Network egress present (pyproject declares an HTTP client dependency) — expected for most servers and not a finding on its own. No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  fail10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 1.2.1 (patch bump): new tool "list_nodes" appeared; new tool "get_node_status" appeared; new tool "list_vms" appeared; new tool "list_containers" appeared; new tool "get_guest_status" appeared; new tool "start_guest" appeared; new tool "stop_guest" appeared; new tool "shutdown_guest" appeared; new tool "reboot_guest" appeared; new tool "list_snapshots" appeared; new tool "create_snapshot" appeared; new tool "rollback_snapshot" appeared; new tool "delete_snapshot" touches a sensitive surface (email/exec/net/fs); new tool "list_storages" appeared; new tool "list_storage_content" appeared; new tool "create_vm" appeared; new tool "create_container" appeared; new tool "clone_guest" appeared; new tool "delete_guest" touches a sensitive surface (email/exec/net/fs); new tool "list_backups" appeared; new tool "create_backup" appeared; new tool "restore_backup" touches a sensitive surface (email/exec/net/fs); new tool "exec_command" touches a sensitive surface (email/exec/net/fs); new tool "get_guest_metrics" appeared; new tool "list_tasks" appeared; new tool "list_networks" appeared; new tool "resize_guest" appeared; new tool "list_firewall_rules" appeared; new tool "add_firewall_rule" appeared; new tool "delete_firewall_rule" touches a sensitive surface (email/exec/net/fs); new tool "migrate_guest" appeared; new tool "list_templates" appeared; new tool "create_template" appeared; new tool "configure_cloud_init" touches a sensitive surface (email/exec/net/fs).

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.