@hostinger/mcp@3.10.4
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install lifecycle scripts, and the reported build, OAuth, bootstrap, and logo kit behavior matches its stated Hostinger MCP and headless setup purpose. The source shows no unsolicited credential transfer, unrelated collection, or default account actions.
Decision evidence
public snapshot- The package identifies itself as a Hostinger API MCP server; its entry points run the server, and package scripts define no install lifecycle hook.
- The build script runs the TypeScript compiler and copies project files into dist; it does not send host or project data.
- OAuth uses Hostinger's auth issuer and a localhost callback, and stores credentials in the user's Hostinger MCP config directory.
- The added logo kit loads opentype.js from the current working directory and provides font and SVG layout utilities.
- The headless bootstrap runs only when invoked; it launches the MCP through npx and supports the documented browser sign-in flow.
- The source reads API tokens and OAuth credentials, but uses them for Hostinger API authentication and the Hostinger OAuth flow.
- The build script invokes npx tsc, but only as an explicit build command; no install hook runs it automatically.
- The headless skill downloads and runs a bootstrap script, but its instructions describe the step and its sign-in behavior to the user.
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.10.4.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.10.4 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.