io.github.zscaler/zscaler-mcp-server

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.

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  fail15% of grade

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

  zscaler_mcp/auth.py: contains a hardcoded OpenAI API key (sk-y…re (len 23)). .env.example: contains a hardcoded OpenAI API key (sk-y…re (len 23)) — in an example/sample file; verify it is not a real key. tests/test_auth.py: assigns a literal to api_key (sk-t…45 (len 13)) — non-provider secret literal; prefer environment intake. tests/test_security.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) Reads secrets from the environment (e.g. tests/test_auth.py) — the recommended intake shape.

• Permission scope

  pass15% of grade

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

  Network egress present (pyproject declares an HTTP client dependency) — 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

  fail10% of grade

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

  vs prior 0.15.3 (patch bump): new hardcoded outbound host/BCC destination(s): 0.0.0.0, 127.0.0.1, accounts.google.com, acme.zslogin.net, acme.zsloginbeta.net, api.zscaler.com, app.example.com, auth.pingone.com, cognito-idp., evil.com, example.com, idp.example.com, login.microsoftonline.com, pillow.readthedocs.io, test-issuer.example.com, www.googleapis.com, your-idp.com, your-mcp-server.example.com.

• Transport config

  warn10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  sends telemetry to third-party SDK (posthog) — disclosure, verify opt-in; manifest/source references Analytics behavior — disclosure