hostinger-api-mcp@2.4.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or concrete attack behavior. The flagged command execution is used by the manual build script and browser-based OAuth flow; authenticated runtime operations are dispatched in response to explicit MCP requests.
Decision evidence
public snapshot- package.json declares start and build scripts, with no install lifecycle hook.
- src/core/tools/all.js contains generated Hostinger API operation definitions; runtime execution requires an explicit execute call.
- OAuth uses auth.hostinger.com, while API requests use the configured API base URL, defaulting to developers.hostinger.com.
- build.js invokes TypeScript compilation as the declared build task.
- The scanner flags runtime shell execution, but the inspected build script uses it only to run the TypeScript compiler; OAuth browser launching is part of the sign-in flow.
- The inspected credential flow sends OAuth codes and tokens to the configured Hostinger issuer, and runtime bearer tokens accompany API requests to the configured API base URL.
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.4.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.4.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.