io.github.mlorentedev/pdf-modifier-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

  warn25% of grade

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

  tool "modify_pdf_content" description: off-vendor URL in a description (example.com); capability text should not name where data goes.

• Supply chain

  pass25% of grade

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

  repository linkage verified

• Credential hygiene

  fail15% of grade

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

  tool "read_pdf_structure" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "inspect_pdf_fonts" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "modify_pdf_content" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_pdf_hyperlinks" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "extract_embedded_fonts" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential). tool "batch_modify_pdf_content" has a secret-shaped input parameter "password" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  unscannable15% of grade

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

  No source files, package.json, or pyproject were fetched; cannot infer capability scope.

• 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.mlorentedev/[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.