io.github.L337-org/docker-mcp-server

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

  unscannable25% of grade

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

  No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

• Supply chain

  fail25% of grade

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

  Python build script executes at build time: network call in build script

• Credential hygiene

  pass15% of grade

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

  Reads secrets from the environment (e.g. docker_mcp/_env.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  warn15% of grade

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

  references credential paths: docker_mcp/tools/_ssh_proxy.py: references a credential path (/.ssh/) has both shell/exec and network egress — capable of download-and-run, though no such path was observed (docker_mcp/tools/_cli.py: subprocess.* call; docker_mcp/tools/_ssh_proxy.py: outbound HTTP/socket call). discloses shell/exec capability: docker_mcp/tools/_cli.py: subprocess.* call Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• 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 2.2.4 (patch bump): new capability primitive(s) in source: http-client, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, 169.254.169.254, auth.docker.io, auth.evil.com, auth.example.com, distribution.github.io, docker-py.readthedocs.io, docs.docker.com, example.com, github.com, hub.docker.com, nodejs.org.

• Transport config

  warn10% of grade

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

  manifest/source references usage stats behavior — disclosure