hostinger-api-mcp@2.16.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe install scripts do not contain a lifecycle hook, and the flagged build command compiles TypeScript when the build script is run. Inspected OAuth and runtime requests target Hostinger services by default, with configurable destinations supplied through operator settings.
Decision evidence
public snapshot- The package manifest defines start and build commands, with no install-time hook in its scripts.
- The build script runs the TypeScript compiler as a build step.
- The main entrypoint starts the MCP server with its generated tool catalog.
- OAuth defaults to Hostinger’s authentication service and allows an operator-supplied issuer.
- OAuth refresh sends the saved refresh token to the issuer’s token endpoint.
- The runtime sends bearer tokens to requests built from the configured API base URL, which defaults to Hostinger’s developer API.
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.16.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.16.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.