hostinger-api-mcp@1.56.0
MCP server for Hostinger API
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe core MCP server is consistent with a Hostinger API client, but packaged agent integration fetches and executes unpinned external code. This is a concrete dangerous capability, not sufficient evidence of intentional malware.
Decision evidence
public snapshot- A packaged agent skill directs agents to download and execute a bootstrap from a moving GitHub branch.
- That bootstrap installs and executes the unpinned latest @hostinger/mcp release through npx.
- The Gemini extension likewise launches unpinned npx code while exposing the Hostinger token environment variable.
- package.json has no preinstall, install, postinstall, or prepare hook.
- The normal MCP runtime uses authenticated Hostinger API calls only after a tool request.
- No self-dependency or hidden binary loader was found.
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.
Findings
Affected versions and remediation
This report applies to hostinger-api-mcp@1.56.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.56.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.