@hostinger/mcp@3.13.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install lifecycle scripts, and the flagged build command compiles TypeScript. The reviewed credential flow uses Hostinger’s OAuth service and stores credentials locally for Hostinger API access.
Decision evidence
public snapshot- The manifest has no lifecycle hooks; its scripts are explicit start and build commands.
- The build command invokes `npx tsc` to compile the project.
- OAuth defaults to Hostinger’s auth service and uses a localhost callback for sign-in.
- OAuth saves the resulting credentials in the user’s Hostinger config directory; the API base defaults to Hostinger’s developer API.
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.13.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.13.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.