hostinger-api-mcp@2.13.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged build command is part of an explicit build script, not an install lifecycle hook. Credential use follows the configured OAuth issuer and Hostinger API flow; the inspected sources show no malicious behavior.
Decision evidence
public snapshot- The manifest points to the MCP server entrypoint and defines start, build, and start:ts scripts, with no install lifecycle hook.
- The build script runs the TypeScript compiler as build work; it is not invoked by an install hook.
- OAuth defaults to Hostinger’s auth service, and an operator can explicitly configure another issuer.
- Saved refresh tokens are sent to the configured OAuth issuer as refresh-grant requests.
- Runtime API calls use a bearer token and default to Hostinger’s developer API; tool execution is handled through MCP requests.
- The all-tools module exports tool definitions as an array, including the named node-static deployment tool.
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.13.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.13.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.