@hostinger/mcp@3.14.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is an explicit build step, and the reviewed OAuth flow sends Hostinger tokens to the configured Hostinger issuer. No install-time behavior or unrelated automatic credential transfer was identified.
Decision evidence
public snapshot- The manifest points to MCP server entry points and declares start/build scripts, with no install lifecycle script.
- build.js runs the TypeScript compiler as part of the explicit build script.
- OAuth uses Hostinger’s auth host for registration, token exchange and refresh.
- OAuth credentials are stored in the user’s Hostinger MCP configuration directory.
- The bootstrap helper is a separate skill script; it checks for existing auth and starts login only when the helper runs.
- The MCP server handles API credentials and performs account operations, which are expected capabilities for a Hostinger API server.
- The OAuth issuer can be overridden with OAUTH_ISSUER, so deployments can direct OAuth to a configured issuer.
Source & flagged code
7 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.14.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.14.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.