hostinger-api-mcp@1.50.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged build command is an explicit TypeScript build step. Inspected runtime and OAuth code use Hostinger service defaults for user-requested API operations and standard authentication; the configuration overrides do not establish a package-selected credential recipient.
Decision evidence
public snapshot- The manifest exposes server entrypoints and start/build scripts, with no install lifecycle hook.
- The build script runs the TypeScript compiler when invoked by the build script; it does not install dependencies or run at package install time.
- The generated tool list describes Hostinger account operations, and runtime execution routes them from MCP tool-call requests.
- OAuth uses Hostinger’s auth service by default and exchanges authorization or refresh tokens with the configured issuer.
- Runtime API requests use the Hostinger developers API by default and send bearer tokens to routes constructed from that API base URL.
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.50.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.50.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.