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

  repository linkage verified

• Credential hygiene

  warn15% of grade

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

  tests/connector-auth.test.ts: contains a hardcoded OpenAI API key (sk-c…et (len 23)) — in an example/sample file; verify it is not a real key. tests/runner.test.ts: contains a hardcoded Google API key (AIza…HI (len 39)) — in an example/sample file; verify it is not a real key. Reads secrets from the environment (e.g. tests/runner.test.ts) — 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 (src/runner.ts: imports child_process and calls exec/spawn; src/connector-auth.ts: outbound HTTP/socket call). discloses shell/exec capability: src/runner.ts: imports child_process and calls exec/spawn 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 2.27.0 (patch bump): new capability primitive(s) in source: child_process, http-client; new hardcoded outbound host/BCC destination(s): 127.0.0.1, accounts.google.com, drive.google.com, example.com, github.com, gogcli-gog-runner.fly.dev, oauth2.googleapis.com, r.test, runner.example, www.anthropic.com, www.googleapis.com, x, x.test.

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