io.github.hostinger/hostinger-api-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.

  repository linkage verified

• Credential hygiene

  pass15% of grade

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

  Reads secrets from the environment (e.g. src/core/oauth.js) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  fail15% of grade

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

  HIGH: shell/exec capability AND network egress together — download-and-execute risk (build.js: imports child_process and calls exec/spawn; src/core/runtime.js: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (build.js: imports child_process and calls exec/spawn; build.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: build.js: imports child_process and calls exec/spawn discloses shell/exec capability: src/core/oauth.js: imports child_process and calls exec/spawn discloses shell/exec capability: src/core/oauth.ts: imports child_process and calls exec/spawn discloses broad/destructive filesystem access: build.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: src/core/runtime.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename) discloses broad/destructive filesystem access: src/core/runtime.ts: destructive/writing fs.* call (write/unlink/rm/chmod/rename) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  pass10% of grade

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

  tool surface, capabilities, install scripts, and publisher unchanged vs prior version 1.8.1 (patch bump); no rug-pull drift.

• Transport config

  fail10% of grade

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

  source performs runtime self-update / download-and-execute (bypasses version_behavior); manifest/source references tracking behavior — disclosure