@hostinger/mcp@3.10.1
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process execution is a build-time TypeScript compile, and the OAuth flow uses Hostinger’s auth service. The server sends credentials to its configured Hostinger API base URL as part of user-requested API operations; no unrelated credential flow or install-time behavior was found.
Decision evidence
public snapshot- The package identifies itself as Hostinger’s MCP server.
- The main entry starts the MCP server and delegates to its runtime and tool definitions.
- OAuth sign-in and sign-out run only when the corresponding CLI flags are supplied.
- OAuth endpoints use Hostinger’s auth service, and the server sends bearer tokens to its configured Hostinger API base URL.
- The build script runs `npx tsc` to compile TypeScript.
- The package uses network access, OAuth credentials, and filesystem writes, but the inspected flows match its Hostinger API server purpose.
- The headless bootstrap invokes this package through `npx` when explicitly run; it is not an install lifecycle hook.
Source & flagged code
9 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.10.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.10.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.