@hostinger/mcp@2.12.0
MCP server for Hostinger API
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package’s active API path forwards environment or OAuth bearer credentials to a configurable destination without a destination restriction shown in that path. This warrants a warning for conditional credential exposure; the inspected build and manifest do not show a malicious install-time chain.
Decision evidence
public snapshot- The runtime accepts an operator-configured API base URL, defaulting to Hostinger’s developer API.
- An active API request obtains a bearer token and sends it to a URL built from that base; the code shown does not restrict the destination host.
- The active server entrypoint loads this runtime. Its token provider can return an environment token or a stored OAuth access token.
- The manifest points to ordinary MCP server entrypoints and declares no install lifecycle scripts.
- The flagged build script runs the TypeScript compiler and copies package files; it does not establish an install-time attack.
Source & flagged code
4 flaggedPackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18The runtime accepts an operator-configured API base URL, defaulting to Hostinger’s developer API.
src/core/runtime.jsView on unpkg · L77Findings
Affected versions and remediation
This report applies to @hostinger/mcp@2.12.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.12.0 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.