io.github.cyyprezz/codex-serverops-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.

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

• Credential hygiene

  warn15% of grade

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

  scripts/manual_auth_window.py: assigns a literal to PASSWORD (oper…id (len 23)) — non-provider secret literal; prefer environment intake. tests/test_auth_launcher.py: assigns a literal to token (one-…ue (len 30)) — non-provider secret literal; prefer environment intake. tests/test_config_model.py: assigns a literal to password (must…ed (len 18)) — non-provider secret literal; prefer environment intake. tests/test_product_probe_askpass.py: assigns a literal to secret (fixt…nt (len 43)) — non-provider secret literal; prefer environment intake. tests/test_redaction.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) tests/test_worker_session_auth.py: assigns a literal to token (expe…en (len 24)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. scripts/manage_test_ssh_alias.py) — the recommended intake shape.

• Permission scope

  warn15% of grade

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

  references credential paths: 4 files (scripts/cleanup_external_test_access.py, spike/askpass/probe.py, spike/docker/entrypoint.sh, +1 more) has both shell/exec and destructive filesystem writes (scripts/elevation_shell_smoke.py: subprocess.* call; scripts/product_core_smoke.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 16 files (scripts/elevation_shell_smoke.py, scripts/file_shell_smoke.py, scripts/manual_release_check.py, +13 more) discloses broad/destructive filesystem access: 7 files (scripts/product_core_smoke.py, scripts/setup_keygen_smoke.py, spike/askpass/probe.py, +4 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.cyyprezz/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

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