hostinger-api-mcp@2.12.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source shows a Hostinger API integration with no install lifecycle hook, and the flagged child-process invocation is part of the explicit TypeScript build script. Authentication and API requests use Hostinger endpoints by default; no concrete attack behavior was identified.
Decision evidence
public snapshot- package.json declares server entrypoints and no install lifecycle hooks; its build command is explicit.
- src/core/tools/all.js exports a generated catalog of Hostinger API tools.
- build.js invokes the TypeScript compiler as its build step.
- OAuth defaults to auth.hostinger.com, and the token exchange posts to that issuer.
- The runtime builds API requests from its configured API base URL and attaches the bearer token to those requests.
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.12.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.12.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.