@hostinger/mcp@3.22.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is used for user-invoked compilation and the documented connection bootstrap. OAuth credentials are exchanged with the Hostinger issuer and bearer tokens are used for Hostinger API requests; no unrelated collection or automatic install-time action was found.
Decision evidence
public snapshot- The manifest exposes Hostinger MCP server entry points and declares start/build scripts, with no install lifecycle script.
- The build script runs the TypeScript compiler when explicitly invoked; the bootstrap runs the Hostinger MCP through npx as part of its connect flow.
- OAuth uses auth.hostinger.com by default and exchanges authorization or refresh tokens with that issuer.
- The runtime sends bearer tokens with API requests to developers.hostinger.com by default; the API base URL is configurable.
- The headless bootstrap is documented as a connect step that checks MCP availability and drives browser sign-in.
- The scanner flags child-process execution and runtime package installation, but the reviewed uses are build-time compilation and the documented connection bootstrap.
- The OAuth source reads and stores credentials for Hostinger authentication; no unrelated credential collector or foreign exfiltration host was identified.
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.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.22.1 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.