hostinger-api-mcp@2.10.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged child-process use is limited to the build compiler and browser launch, while the inspected credential flows target Hostinger services by default. No install-time attack, hidden credential export, or unrelated mutation was found.
Decision evidence
public snapshot- The manifest exposes the server entrypoints and defines a build script that invokes build.js; it has no install lifecycle hook.
- The build script runs the TypeScript compiler and copies build files, with no package installation or unrelated project mutation in the inspected source.
- OAuth defaults to Hostinger’s authentication service, sends token requests to the configured issuer, and launches the browser using a fixed platform command.
- The runtime defaults API requests to Hostinger’s API and sends bearer tokens with those requests; the base URL can be changed through an operator-set environment variable.
- The all-tools entrypoint starts the Hostinger MCP server with its generated tool catalog.
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@2.10.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.10.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.