@hostinger/mcp@3.20.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reviewed source supports the package’s stated purpose: serving Hostinger API tools with OAuth credentials sent to Hostinger’s authentication and API services. The flagged process execution is a TypeScript build step, and the package declares no install lifecycle scripts.
Decision evidence
public snapshot- The package entry points start Hostinger MCP servers; package metadata declares no install or postinstall hook.
- OAuth defaults to auth.hostinger.com and uses its registration, authorization, token and revocation endpoints.
- OAuth credentials are saved under the hostinger-mcp config directory; token use follows the Hostinger OAuth flow.
- The runtime API base defaults to developers.hostinger.com and can be overridden with API_BASE_URL.
- The flagged build command runs npx tsc to compile TypeScript and copies package files into dist.
- The headless bootstrap helper invokes npx to resolve @hostinger/mcp@latest when that helper is explicitly run.
- The package exposes account management tools, which can make changes when a user invokes them.
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.20.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.20.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.