@hostinger/mcp@3.20.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is confined to the explicit TypeScript build and the headless sign-in workflow. The reviewed OAuth credentials are stored in the package’s user-specific configuration directory and exchanged with Hostinger’s auth issuer, with no unrelated collector or automatic install-time behavior found.
Decision evidence
public snapshot- The package identifies itself as Hostinger’s API MCP server and exposes server entry points for that purpose.
- OAuth uses Hostinger’s auth issuer for registration, authorization and token operations.
- OAuth refresh sends the cached refresh token and client ID to the configured issuer’s token endpoint.
- OAuth credentials are stored under the user’s Hostinger MCP configuration directory; on non-Windows systems the write uses mode 0600.
- The runtime resolves a token for API requests, using the Hostinger API base URL by default.
- The flagged build script runs the TypeScript compiler as an explicit build step; the headless bootstrap’s npx calls support its sign-in flow.
- No install lifecycle scripts are declared in package.json.
- The reviewed credential flow sends OAuth tokens to the Hostinger issuer, and the API token is used by the API runtime.
- The headless bootstrap checks for existing authentication and otherwise launches the documented browser sign-in flow.
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.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.20.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.