hostinger-api-mcp@2.17.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source supports a warning because an unrestricted API_BASE_URL override can receive a Hostinger bearer token during an invoked operation. The default destination is Hostinger, and the override requires operator configuration, so the inspected behavior does not establish a hidden export or justify blocking publication.
Decision evidence
public snapshot- The runtime accepts API_BASE_URL from the environment and otherwise uses Hostinger's developer API.
- Authentication supplies an environment token or a cached OAuth access token.
- An invoked execute operation is routed to the API request handler.
- The handler builds the request URL from the configured base URL and attaches the bearer token before sending it.
- The manifest lists start and build scripts, with no install lifecycle script.
- The default API destination and OAuth issuer are Hostinger endpoints; the alternate API destination is used only when configured by the operator.
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@2.17.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.17.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.