io.github.logisky/logisheets-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

  fail25% of grade

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

  tool "open_workbook" param "name" description: names an outbound copy/exfil destination (BCC/exfil verb).

• Supply chain

  pass25% of grade

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

  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.4.0 (patch bump): new tool "open_workbook" touches a sensitive surface (email/exec/net/fs); new tool "save_workbook" touches a sensitive surface (email/exec/net/fs); new tool "export_xlsx" touches a sensitive surface (email/exec/net/fs); new tool "list_blocks" touches a sensitive surface (email/exec/net/fs); new tool "describe_block" appeared; new tool "eval_formula" appeared; new tool "create_block" touches a sensitive surface (email/exec/net/fs); new tool "convert_to_block" touches a sensitive surface (email/exec/net/fs); new tool "set_block_description" touches a sensitive surface (email/exec/net/fs); new tool "add_block_rows" touches a sensitive surface (email/exec/net/fs); new tool "delete_block_rows" touches a sensitive surface (email/exec/net/fs); new tool "move_block_row" touches a sensitive surface (email/exec/net/fs); new tool "set_block_cells" touches a sensitive surface (email/exec/net/fs); new tool "set_field_rule" touches a sensitive surface (email/exec/net/fs); new tool "create_sheet" appeared; new tool "get_cells" touches a sensitive surface (email/exec/net/fs); new tool "set_cells" touches a sensitive surface (email/exec/net/fs); new tool "list_violations" appeared; new tool "preview_changes" touches a sensitive surface (email/exec/net/fs); new tool "trace" touches a sensitive surface (email/exec/net/fs); new tool "goal_seek" touches a sensitive surface (email/exec/net/fs); new tool "chart_from_block" appeared; new tool "chart_insert" touches a sensitive surface (email/exec/net/fs); new tool "chart_list" appeared; new tool "chart_update" appeared; new tool "chart_delete" 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.