@hostinger/mcp@3.21.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is limited to TypeScript compilation and launching the OAuth browser. Tokens are acquired through Hostinger OAuth and used for API requests, with no install hook or unrelated exfiltration found.
Decision evidence
public snapshot- The manifest exposes start/build scripts but no install lifecycle hooks.
- OAuth defaults to Hostinger’s authorization service and uses its OAuth endpoints.
- OAuth sign-in opens a browser and uses a localhost callback with PKCE.
- Stored credentials are reused or refreshed through the OAuth flow.
- API bearer tokens are sent with requests to the configured Hostinger API base URL.
- The build script runs the TypeScript compiler and writes build output.
- The scanner’s child-process and shell flags correspond to the build compiler and browser launcher; neither executes concealed remote code.
- The bootstrap’s npx invocation is part of an optional headless sign-in workflow, not an install hook or package startup action.
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.21.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.21.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.