@hostinger/mcp@3.22.4
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is limited to compiling the package and an explicitly run connector bootstrap. OAuth credentials and API bearer tokens are used with Hostinger’s auth and API endpoints, consistent with the package’s stated purpose.
Decision evidence
public snapshot- The manifest points its CLI and main entry to the Hostinger MCP server and declares no install lifecycle hook.
- The build script runs `npx tsc` as part of the explicit build command.
- OAuth uses `https://auth.hostinger.com` for registration, authorization, token exchange, and revocation.
- The runtime sends bearer tokens to the Hostinger API base URL, which defaults to `https://developers.hostinger.com` and can be changed by the user with `API_BASE_URL`.
- The headless bootstrap is documented as a script to download and run for connector setup; it launches the Hostinger MCP and its OAuth flow.
- The package reads environment tokens and stores OAuth credentials in the user’s Hostinger MCP configuration directory; these are expected authentication behaviors for this API client.
- The bootstrap uses `npx` to resolve `@hostinger/mcp@latest`, but this happens only when the bootstrap is run for setup.
Source & flagged code
4 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.
Findings
Affected versions and remediation
This report applies to @hostinger/mcp@3.22.4.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.22.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.