hostinger-api-mcp@2.13.0
MCP server for Hostinger API
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged build subprocess runs the compiler only when the build command is invoked. Inspected authentication and API requests follow the configured service endpoints and caller-requested MCP operations; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json points to the server entrypoint and defines only start, build, and TypeScript start scripts, with no install lifecycle hook.
- build.js invokes the TypeScript compiler when the build script runs.
- The tool catalog includes a read-only VPS lookup operation; runtime operations execute in response to MCP tool calls.
- OAuth uses Hostinger’s issuer by default, with an issuer override supplied through an environment variable.
- OAuth credentials are stored under the user’s config directory; Unix writes request restrictive file permissions.
- Runtime API requests use the configured API base, defaulting to Hostinger, and attach the bearer token to the request for the caller-invoked operation.
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.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.13.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.