hostinger-api-mcp@3.6.1
MCP server for Hostinger API
AI Security Review
scanned 18h ago · by lpm-firewall-aiThe configurable destinations create a conditional credential exposure risk, so this warrants a warning. No install-time attack or unrelated default recipient was established.
Decision evidence
public snapshot- src/core/oauth.js loads saved credentials and sends a saved refresh token to the configured issuer; OAUTH_ISSUER can override the Hostinger default without binding stored credentials to that issuer.
- src/core/runtime.js obtains a bearer token for API requests and sends it to URLs built from API_BASE_URL, which can override the Hostinger default.
- package.json defines start, build, and start:ts scripts and has no install lifecycle hook.
- The default OAuth issuer and API endpoint are Hostinger services, so the exposure depends on configuring an unrelated recipient.
- The inspected source does not establish that credentials were sent to an unrelated recipient by default.
Source & flagged code
10 flagged · loading sourcePackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgFindings
Affected versions and remediation
This report applies to hostinger-api-mcp@3.6.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.6.1 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.