io.github.SupercmoHQ/supercmo

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 "image_analysis" param "requests" description: cross-tool redirection ('instead of call…'). tool "video_analysis" param "requests" description: cross-tool redirection ('instead of call…').

• 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

  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.

  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.1.23 (patch bump): new tool "setup_status" touches a sensitive surface (email/exec/net/fs); new tool "image_generate" touches a sensitive surface (email/exec/net/fs); new tool "list_image_models" appeared; new tool "video_generate" touches a sensitive surface (email/exec/net/fs); new tool "list_video_models" appeared; new tool "audio_generate" touches a sensitive surface (email/exec/net/fs); new tool "list_audio_models" appeared; new tool "list_voices" touches a sensitive surface (email/exec/net/fs); new tool "url_extraction" touches a sensitive surface (email/exec/net/fs); new tool "image_analysis" touches a sensitive surface (email/exec/net/fs); new tool "video_analysis" touches a sensitive surface (email/exec/net/fs); new tool "social_research" touches a sensitive surface (email/exec/net/fs); new tool "list_research_sources" appeared; new tool "transcribe" touches a sensitive surface (email/exec/net/fs); new tool "video_stitch" touches a sensitive surface (email/exec/net/fs); new tool "caption_video" touches a sensitive surface (email/exec/net/fs); new tool "video_overlay" touches a sensitive surface (email/exec/net/fs); new tool "job_status" touches a sensitive surface (email/exec/net/fs); new tool "calendar_list" appeared; new tool "calendar_add" touches a sensitive surface (email/exec/net/fs); new tool "calendar_update" touches a sensitive surface (email/exec/net/fs); new tool "calendar_remove" appeared.

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