hostinger-api-mcp@1.63.4
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe unrestricted API_BASE_URL override allows runtime requests to carry bearer credentials to a configured destination, so this warrants a warning for conditional credential exposure. The default destination is package-aligned, and the flagged build command is a manually invoked compiler step rather than an install-time attack.
Decision evidence
public snapshot- The manifest declares start and build scripts but no install lifecycle hook.
- The server entry starts the runtime, which defaults its API endpoint to developers.hostinger.com and accepts an API_BASE_URL override.
- The runtime builds requests from that base, attaches a bearer token obtained through its auth flow, and sends the requests without restricting the destination.
- The build script invokes the TypeScript compiler and copies project files when run.
- The default API destination is Hostinger’s developer API, so the credential exposure depends on configuring API_BASE_URL to an unrelated destination.
- The inspected package manifest has no automatic install trigger.
Source & flagged code
4 flagged · loading sourcePackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/core/oauth.jsFindings
Affected versions and remediation
This report applies to hostinger-api-mcp@1.63.4.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.63.4 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.