hostinger-api-mcp@2.18.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install hook or fixed third-party credential recipient. However, API_BASE_URL has no destination allowlist, and runtime requests attach the OAuth bearer token to URLs built from it, leaving conditional credential exposure unresolved.
Decision evidence
public snapshot- The manifest exposes start and build scripts but has no install lifecycle hook.
- The build script runs the TypeScript compiler when invoked; it does not run an install command.
- OAuth can return a saved access token, and runtime requests attach that bearer token to their URL.
- The API base defaults to Hostinger but can be replaced through API_BASE_URL without a destination allowlist.
- The runtime includes multiple specialized API request paths that send bearer tokens to URLs built from the configured API base.
- The default API and OAuth destinations are Hostinger services, and the package’s listed tools describe Hostinger account operations.
- API requests are issued through MCP tool handlers; no automatic credential transfer to a fixed unrelated host was identified.
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.18.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.18.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.