hostinger-api-mcp@1.63.3
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe scanner’s runtime-install signal maps to a build script that invokes the TypeScript compiler, and the manifest defines no install lifecycle hook. Inspected authentication and API request paths use Hostinger defaults, while account operations run through MCP tool calls.
Decision evidence
public snapshot- The manifest defines start, build and start:ts scripts, with no install lifecycle hook.
- The flagged build command runs the TypeScript compiler as part of the build script.
- OAuth defaults to Hostinger’s auth service and sends refresh tokens to that issuer’s token endpoint.
- API requests use the configured API base, defaulting to Hostinger’s developer API, and attach the OAuth bearer token there.
- The runtime executes tools in response to MCP tool calls; the catalog marks a destructive deployment tool for user confirmation.
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.63.3.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.63.3 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.