hostinger-api-mcp@2.17.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe configurable API destination and bearer-token forwarding create a conditional credential exposure risk. The default endpoints are Hostinger services, so the source supports a warning rather than a publish block.
Decision evidence
public snapshot- The runtime accepts API_BASE_URL, defaulting to Hostinger's API, without a visible destination restriction.
- The runtime sends its bearer token in the Authorization header on API requests.
- OAuth defaults to Hostinger's issuer but accepts OAUTH_ISSUER; it can return a saved access token and exchanges login codes with the selected issuer.
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.17.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.17.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.