io.github.Ostico/bruno-mcp-studio

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

  warn25% of grade

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

  tool "set_environment_variable" param "secret" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

• Supply chain

  warn25% of grade

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

  install hook "prepare" present and not a recognized benign build command; dependency "yaml" is edit-distance 2 from popular package "yarn" (typosquat candidate); dependency "@usebruno/query" is edit-distance 1 from popular package "jquery" (typosquat candidate)

• Credential hygiene

  pass15% of grade

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  pass15% of grade

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

  Network egress present (package.json depends on HTTP client "undici") — expected for most servers and not a finding on its own. No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  warn10% of grade

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

  vs prior 2.4.0 (minor bump): new tool "create_collection" appeared; new tool "create_environment" touches a sensitive surface (email/exec/net/fs); new tool "update_environment" touches a sensitive surface (email/exec/net/fs); new tool "set_environment_variable" appeared; new tool "remove_environment_variable" appeared; new tool "write_request" touches a sensitive surface (email/exec/net/fs); new tool "move_request" touches a sensitive surface (email/exec/net/fs); new tool "add_test_script" touches a sensitive surface (email/exec/net/fs); new tool "remove_script" touches a sensitive surface (email/exec/net/fs); new tool "delete_request" touches a sensitive surface (email/exec/net/fs); new tool "list_collections" touches a sensitive surface (email/exec/net/fs); new tool "list_requests" touches a sensitive surface (email/exec/net/fs); new tool "get_collection_stats" touches a sensitive surface (email/exec/net/fs); new tool "run_collection" touches a sensitive surface (email/exec/net/fs); new tool "read_request" touches a sensitive surface (email/exec/net/fs); new tool "read_environment" touches a sensitive surface (email/exec/net/fs); new tool "unregister_collection" touches a sensitive surface (email/exec/net/fs); new tool "delete_collection" touches a sensitive surface (email/exec/net/fs).

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