hostinger-api-mcp@1.47.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source supports a credential-forwarding warning because operator-configured destinations are not checked against the Hostinger service. The defaults are Hostinger-aligned, and the transfer requires tool use or credential refresh, so the evidence does not establish a malicious default export.
Decision evidence
public snapshot- The runtime accepts API_BASE_URL, defaults it to Hostinger, and builds API request URLs from that setting without a destination check.
- Saved Hostinger access tokens are returned for API calls; saved refresh tokens are posted to the configured OAuth issuer.
- API requests attach the bearer token and send the request through Axios.
- Requests are activated by an MCP caller invoking a tool.
- The manifest exposes the server entrypoints and lists start and build scripts; the build script runs the TypeScript compiler.
- The tool list describes Hostinger API operations, and the OAuth issuer defaults to Hostinger.
- The default API and OAuth destinations are Hostinger endpoints.
- The manifest declares no install lifecycle hook; the flagged build command is reached through the build script.
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.47.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.47.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.