@hostinger/mcp@3.20.4
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged build script performs compilation only when manually run, and the changed OAuth code implements Hostinger's browser-based login and token flow with issuer validation. No install-time activity or unrelated credential transmission was found.
Decision evidence
public snapshot- The package starts a Hostinger API MCP server through its declared entry points.
- OAuth uses Hostinger's auth issuer by default and restricts overrides to HTTPS origins or loopback HTTP.
- OAuth exchanges authorization codes and refresh tokens with the configured issuer; the login path uses a browser callback and PKCE.
- API bearer tokens are attached to requests made by the MCP runtime.
- The flagged build script runs TypeScript compilation when explicitly invoked as the build script.
- No install lifecycle script is declared in package.json.
- OAuth credentials are stored for this package under the user's hostinger-mcp configuration directory.
- The headless bootstrap is an explicit connect helper and launches the package's own MCP binary for login.
- No unrelated credential collection, external collector, or concealed execution behavior was identified.
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.20.4.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.20.4 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.