hostinger-api-mcp@1.60.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe configurable API destination receives bearer credentials without a destination allowlist, creating a conditional credential exposure risk. Default endpoints are Hostinger services, and the flagged build command performs ordinary compilation when invoked.
Decision evidence
public snapshot- The API base URL can be set with API_BASE_URL; the default is developers.hostinger.com.
- Runtime requests attach a bearer token obtained through the OAuth provider or environment token.
- The OAuth provider defaults to auth.hostinger.com and sends tokens to that issuer.
- The manifest exposes server entrypoints and build scripts; build.js runs the compiler when the build script is invoked.
- With default settings, API calls target developers.hostinger.com and OAuth uses auth.hostinger.com.
- The build script compiles TypeScript and copies package files; the inspected code shows no install-time action.
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.60.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.60.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.