hostinger-api-mcp@3.1.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or malicious runtime behavior. The flagged build script compiles TypeScript, and the OAuth and API defaults are package-aligned Hostinger services; alternate endpoints require explicit configuration.
Decision evidence
public snapshot- package.json defines start, build, and start:ts scripts, with no install lifecycle hook.
- build.js runs the TypeScript compiler for the declared build script.
- The package entrypoint starts the runtime with a generated Hostinger API tool catalog.
- OAuth defaults to auth.hostinger.com and sends refresh requests to the configured issuer's token endpoint.
- Runtime bearer tokens are sent with API requests to the configured API base URL, which defaults to developers.hostinger.com.
- OAUTH_ISSUER and API_BASE_URL can be configured to other endpoints, so an operator who deliberately changes them also changes where OAuth or API requests go.
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@3.1.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.1.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.