@hostinger/mcp@3.21.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install lifecycle hooks, and the flagged shell use is limited to explicit compilation or the optional connection workflow. OAuth credentials flow to Hostinger's OAuth issuer and configured Hostinger API; no unrelated exfiltration or unrequested account action was found.
Decision evidence
public snapshot- The manifest defines start and build commands but no install lifecycle hooks.
- build.js runs `npx tsc` as an explicit build step; it does not run on install or import.
- OAuth uses Hostinger's auth.hostinger.com issuer and stores Hostinger OAuth credentials for later use.
- The API defaults to developers.hostinger.com; bearer tokens are attached to requests sent to the configured API base URL.
- The headless bootstrap resolves and invokes this package's own `@hostinger/mcp@latest` binary when the connect workflow runs.
- No package code was identified that sends credentials to an unrelated host or performs account actions without a tool request.
- The flagged shell execution is limited to TypeScript compilation; the headless bootstrap is part of the package's connect workflow.
Source & flagged code
5 flaggedPackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hostinger/mcp@3.21.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.21.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.