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

  package name "@wdio/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "yazl" is edit-distance 2 from popular package "yarn" (typosquat candidate)

• 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. lib/server.js) — 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.

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (lib/server.js: imports child_process and calls exec/spawn; lib/server.js: outbound HTTP/socket call). discloses shell/exec capability: lib/server.js: imports child_process and calls exec/spawn discloses shell/exec capability: lib/show-trace.js: imports child_process and calls exec/spawn discloses dynamic code execution: lib/server.js: uses new Function(…) 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 3.11.0 (minor bump): new capability primitive(s) in source: child_process, dynamic-eval, http-client; new hardcoded outbound host/BCC destination(s): api-cloud.browserstack.com, api., api.browserstack.com, api.eu-central-1.saucelabs.com, api.lambdatest.com, api.testingbot.com, cloud.example.com, downloads.lambdatest.com, github.com, local-downloads.browserstack.com, manual-api.lambdatest.com, player.vibium.dev, saucelabs.com, testingbot.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.