io.github.rnaga/wp-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

  warn25% of grade

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

  dependency "enquirer" is edit-distance 1 from popular package "inquirer" (typosquat candidate); dependency "@rnaga/wp-node" is edit-distance 2 from popular package "ts-node" (typosquat candidate)

• Credential hygiene

  warn15% of grade

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

  proxy/config.js: assigns a literal to password (REMO…RD (len 15)) — non-provider secret literal; prefer environment intake. cli/remote-connector/index.js: assigns a literal to password (/aut…rd (len 14)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. config.js) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (cli/http.cli.js: imports child_process; http/auth/providers/auth0-provider.js: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (cli/http.cli.js: imports child_process; config.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: cli/http.cli.js: imports child_process discloses shell/exec capability: cli/remote-connector/index.js: imports child_process discloses shell/exec capability: cli/local.cli.js: imports child_process discloses broad/destructive filesystem access: config.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) 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 1.0.8 (patch bump): new capability primitive(s) in source: child_process, fs-write, http-client; new hardcoded outbound host/BCC destination(s): accounts.google.com, api.github.com, auth, datatracker.ietf.org, github.com, oauth2.googleapis.com, www.googleapis.com.

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