hostinger-api-mcp@1.51.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe default endpoints are Hostinger services, but API_BASE_URL and OAUTH_ISSUER accept alternate destinations without binding the credentials to those services. Because runtime calls can send existing bearer or refresh tokens there, this is a conditional credential exposure risk warranting a warning.
Decision evidence
public snapshot- The OAuth issuer can be replaced through OAUTH_ISSUER, and the default is Hostinger’s authentication service.
- When saved credentials need refreshing, the refresh token is sent to the configured issuer without a destination allowlist.
- API_BASE_URL can replace the Hostinger API default; runtime requests attach the bearer token and send to that URL when a tool is called.
- The token transfer is conditional on runtime authentication or a tool request; the manifest has no install lifecycle hook, and the build script invokes the TypeScript compiler.
- The defaults point to Hostinger services, and the endpoint overrides require explicit environment configuration.
- The package manifest exposes runtime server commands but no preinstall, install, or postinstall command.
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.51.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.51.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.