@hostinger/mcp@3.10.2
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process execution is used for TypeScript compilation and an explicitly started Hostinger connect flow. OAuth sends tokens to the configured issuer, which defaults to Hostinger, and stores credentials in the user’s Hostinger MCP config directory; no unrelated credential transfer or install-time behavior was found.
Decision evidence
public snapshot- The package metadata points its main entry and commands at Hostinger MCP server entry points.
- The build script runs `npx tsc` as a build step; package.json declares no lifecycle scripts.
- OAuth uses `https://auth.hostinger.com` by default and sends refresh tokens to that issuer’s token endpoint.
- OAuth credentials are stored under the user’s `hostinger-mcp` config directory.
- The headless bootstrap launches the published Hostinger MCP package for its connect and login flow.
- The OAuth issuer can be overridden with `OAUTH_ISSUER`, and tokens are sent to that configured issuer.
- The runtime exposes login and logout as explicit command-line options; the entry point starts the MCP server.
- No source reviewed showed credentials sent to an unrelated host or install-time network activity.
Source & flagged code
9 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.10.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.10.2 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.