hostinger-api-mcp@1.48.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe default API destination is Hostinger, but API_BASE_URL accepts an alternate base and the runtime forwards saved OAuth credentials to it without a destination restriction. This is a conditional credential exposure risk, so it warrants a warning rather than a block.
Decision evidence
public snapshot- The package entrypoint is the MCP server in src/servers/all.js.
- A client tool call can invoke the server's API-call handler.
- OAuth token resolution loads saved credentials and returns an unexpired access token.
- API_BASE_URL can replace the Hostinger API default.
- API request URLs are built from that configurable base.
- The bearer token is added to the request authorization header and the request is sent through Axios.
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.48.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.48.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.