hostinger-api-mcp@1.46.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe runtime permits an arbitrary API_BASE_URL and sends existing Hostinger bearer credentials to it, creating conditional credential exposure. Because the default is the intended Hostinger API and the source shows no automatic unrelated recipient, this warrants a warning rather than a block.
Decision evidence
public snapshot- The package entrypoint starts an MCP server that processes client tool requests.
- API_BASE_URL can override the Hostinger API default, and requests are built from that base URL without a destination allowlist.
- API requests obtain bearer credentials from environment variables or saved OAuth credentials.
- The runtime attaches the bearer token to the request and sends it to the constructed URL.
- The default API destination is Hostinger’s developer API; the exposure depends on an operator configuring a different destination.
- The inspected source does not show automatic credential export to a publisher-selected host; the configured default is the Hostinger API.
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.46.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.46.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.