@hostinger/mcp@3.15.1
MCP server for Hostinger API
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged process execution is limited to compiling TypeScript and opening the OAuth sign-in page. Credentials and API requests are directed to Hostinger, while account operations are dispatched in response to MCP tool calls.
Decision evidence
public snapshot- The manifest identifies this as a Hostinger API MCP server.
- The build script runs `npx tsc` as its compilation step.
- OAuth is configured for Hostinger’s auth service, and the token exchange sends OAuth grant parameters there.
- API operations run through the MCP tool-call handler, which dispatches requested operations.
- The package uses child-process execution to open a browser during OAuth login and runs a compiler in the build script.
- It stores Hostinger OAuth tokens locally and sends authenticated API requests to Hostinger.
- The bundled skills contain operational guidance for managing hosting accounts, but the package serves them as resources rather than executing them automatically.
Source & flagged code
7 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.15.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.15.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.