hostinger-api-mcp@3.2.2
MCP server for Hostinger API
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged build command is a development compilation step, and package.json contains no install lifecycle hook. Inspected runtime behavior serves user-invoked Hostinger API operations using Hostinger OAuth or caller-provided API tokens; no malicious behavior was found.
Decision evidence
public snapshot- package.json defines start and build commands but no install lifecycle hook.
- build.js runs the TypeScript compiler and prepares generated distribution files.
- The server entrypoint registers the Hostinger API tool catalog.
- API calls use a bearer token and a Hostinger API base URL by default; token values come from environment variables or the OAuth provider.
- OAuth uses Hostinger's issuer by default and saves credentials with restrictive file permissions on non-Windows systems.
Source & flagged code
4 flagged · loading sourcePackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18build.js runs the TypeScript compiler and prepares generated distribution files.
build.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to hostinger-api-mcp@3.2.2.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.2.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.