io.github.Creed-Space/vcp-mcp

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

  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

  warn15% of grade

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

  src/vcp/mcp_server.py: assigns a literal to token (fami…de (len 17)) — non-provider secret literal; prefer environment intake. src/vcp/mcp_server.py: assigns a literal to token (comp…EC (len 33)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. src/vcp/mcp_server.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  discloses broad/destructive filesystem access: src/vcp/hub/install.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/vcp/hub/publish.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) 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 0.7.0 (minor bump): new capability primitive(s) in source: child_process, dynamic-eval, fs-write, http-client, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, attacker.invalid, evil.example.invalid, example.com, example.invalid, github.com, raw.githubusercontent.com, user, valuecontextprotocol.org.

• 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.