@hostinger/mcp@3.19.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install hook, and the flagged build command only runs the TypeScript compiler. The bootstrap and OAuth behavior is tied to connecting or signing in to Hostinger, with credentials sent to Hostinger's auth service.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; its entry points start the Hostinger MCP server.
- The build script runs npx tsc as part of the explicitly named build task.
- The headless skill instructs users to download and run its bootstrap script when connecting the MCP.
- The bootstrap uses npx to resolve @hostinger/mcp@latest and checks for existing authentication before starting login.
- OAuth uses Hostinger's auth service and a localhost callback for the sign-in flow.
- Following the connection skill downloads and runs a bootstrap script and may resolve the latest package version through npx.
Source & flagged code
7 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.19.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.19.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.