hostinger-api-mcp@2.9.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s default endpoints are Hostinger services, but environment-configurable destinations can receive existing bearer or refresh credentials without a source-level destination restriction. This supports a warning for conditional credential exposure, not a finding of malicious behavior.
Decision evidence
public snapshot- The runtime accepts an environment-configured API base URL, defaulting to Hostinger’s API.
- Runtime API requests build URLs from that base and attach the bearer token before sending the request.
- Bearer credentials can come from Hostinger token environment variables or OAuth; saved OAuth credentials are read from the user’s configuration directory.
- The OAuth issuer is environment-configurable, and refresh requests send the saved refresh token to its token endpoint.
- The package’s build script is explicit and runs the TypeScript compiler; it is not an install lifecycle hook.
- The configured Hostinger endpoints are the defaults, and the source shows no package-selected unrelated recipient or automatic credential transfer to a fixed third party.
- The flagged build command compiles TypeScript; package.json has no preinstall, install, or postinstall hook.
Source & flagged code
4 flagged · loading sourcePackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/core/oauth.jsFindings
Affected versions and remediation
This report applies to hostinger-api-mcp@2.9.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.9.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.