@hostinger/mcp@3.8.1
MCP server for Hostinger API
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks or concrete attack behavior. The flagged similarity hits concern Hostinger OAuth, generated MCP skills and tools, a user-run bootstrap, and a logo utility; inspected behavior aligns with those functions.
Decision evidence
public snapshot- package.json has no lifecycle hooks; its entrypoints start the Hostinger MCP server.
- OAuth uses Hostinger’s authentication issuer and sends token requests there; the issuer can also be configured.
- The generated skills and tool catalog expose Hostinger account operations through the MCP interface.
- The flagged bootstrap launches the Hostinger MCP through npx when run; it is not an install hook.
- Inspected dependencies provide MCP transport, HTTP, and CORS functionality; the cited Axios locations handle request cancellation.
Source & flagged code
9 flaggedPackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hostinger/mcp@3.8.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.8.1 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.