@hostinger/mcp@3.28.2
MCP server for Hostinger API
AI Security Review
scanned 9h ago · by lpm-firewall-aiThe manifest has no install hooks, and the reviewed shell execution is limited to the explicit TypeScript build and a user-run bootstrap invoking this package. OAuth targets Hostinger's authentication service; the alleged foreign credential redirect was not present in the inspected source.
Decision evidence
public snapshot- The manifest points to the Hostinger MCP server entry points and declares no install lifecycle scripts.
- The build script runs `npx tsc` only when the build command is run; it does not run as an install hook.
- The bootstrap uses npx to invoke this package and checks for its own Hostinger token or cached Hostinger OAuth credentials.
- OAuth endpoints use the Hostinger authentication issuer; no foreign credential destination was identified in the reviewed source.
Source & flagged code
8 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.28.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.28.2 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.