hostinger-api-mcp@1.49.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source establishes conditional credential exposure through an unrestricted operator-configured OAuth issuer, which warrants a warning but does not show a package-selected recipient or covert transfer. The default issuer is Hostinger and the manifest has no install lifecycle hook.
Decision evidence
public snapshot- The default OAuth issuer is Hostinger, but the OAUTH_ISSUER environment variable can replace it without a destination restriction.
- When a saved access token is expired, the provider loads saved credentials and attempts a refresh using the stored refresh token.
- The refresh request sends that token in a form body to the configured issuer's token endpoint.
- Runtime API requests obtain a bearer token through the OAuth provider and attach it to the request.
- The manifest declares server entrypoints and start/build scripts, with no install lifecycle hook.
- The default issuer is https://auth.hostinger.com; exposure to another recipient requires an operator-configured issuer override.
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@1.49.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.49.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.