hostinger-api-mcp@2.14.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install hook or concrete attack behavior. The scanner’s build and child-process signals correspond to the explicit TypeScript build script and the OAuth browser-launch flow, while runtime requests target the configured Hostinger API and OAuth services.
Decision evidence
public snapshot- package.json exposes server entrypoints and only start, build, and start:ts scripts; it defines no install lifecycle hook.
- build.js runs TypeScript compilation as part of the explicit build script and copies package files.
- OAuth defaults to Hostinger’s auth service; changing the issuer requires an explicit constructor value or OAUTH_ISSUER setting.
- OAuth uses the issuer’s token endpoint, and runtime API calls send bearer tokens to the configured API base URL, which defaults to Hostinger’s developers API.
- The API catalog is reached through the MCP execute operation; no attack behavior was identified in the inspected sources.
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.14.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.14.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.