hostinger-api-mcp@3.7.1
MCP server for Hostinger API
AI Security Review
scanned 12h ago · by lpm-firewall-aiThe package does not send credentials to an unrelated publisher-selected default, and its manifest has no lifecycle hooks. However, the unrestricted API_BASE_URL override can direct existing Hostinger credentials to another host during an API call, so this warrants a warning rather than a block.
Decision evidence
public snapshot- package.json has no lifecycle hooks, and the runtime accepts API_BASE_URL while defaulting to developers.hostinger.com.
- The OAuth provider obtains bearer tokens from environment variables or the user's stored credentials.
- When an API operation runs, the runtime resolves its URL against API_BASE_URL, attaches the bearer token, and sends the request.
- The default API destination is developers.hostinger.com; forwarding to another host requires an API_BASE_URL override and an API operation.
Source & flagged code
9 flagged · loading sourcePackage 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-api-mcp@3.7.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.7.1 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.