hostinger-api-mcp@1.63.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiInspected source shows no install-time hook or concealed credential transfer: the flagged build command runs the TypeScript compiler, and OAuth exchanges tokens with its configured issuer. Runtime bearer tokens are used for API requests to the configured API base URL, while tool operations are user-invoked; the static hints alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the all-server entrypoint and defines start, build, and TypeScript start scripts; it has no install lifecycle hook.
- build.js runs the TypeScript compiler and copies package files into dist.
- src/core/tools/all.js describes Hostinger API operations, including a deployment operation that warns it overwrites website contents and asks for user confirmation.
- OAuth uses Hostinger’s authentication service by default, supports an explicitly configured issuer, and exchanges a user authorization code for tokens there.
- OAuth credentials are loaded from and saved to a per-user configuration directory; runtime requests send the bearer token to the configured API base URL.
- The all-server entrypoint starts the MCP runtime with the package’s tool list and instructions.
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@1.63.2.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.63.2 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.