io.github.n24q02m/wet-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

  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. src/wet_mcp/config.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

  fail15% of grade

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

  HIGH: executes content derived from a network response (src/wet_mcp/sources/crawler.py: passes a network response into an exec/eval call). references credential paths: src/wet_mcp/security.py: references a credential path (id_rsa) has both shell/exec and destructive filesystem writes (src/wet_mcp/server.py: subprocess.* call; src/wet_mcp/setup_tool.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: src/wet_mcp/server.py: subprocess.* call discloses shell/exec capability: src/wet_mcp/setup.py: subprocess.* call discloses broad/destructive filesystem access: src/wet_mcp/setup_tool.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/wet_mcp/sources/crawler.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

  pass10% of grade

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

  tool surface, capabilities, install scripts, and publisher unchanged vs prior version 3.9.0 (minor bump); no rug-pull drift.

• 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 tracking behavior — disclosure