hostinger-api-mcp@2.5.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged child-process use is in an explicitly invoked build script that runs the TypeScript compiler, not an install hook. Inspected OAuth and API requests are aligned with Hostinger services by default, and no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest points to the MCP server entrypoint and defines a build command, with no install lifecycle hook shown.
- The build script runs the TypeScript compiler and copies package files into dist when invoked.
- OAuth defaults to Hostinger’s issuer; an issuer override must come from the caller or environment.
- The OAuth login exchanges its authorization code at the configured issuer, while runtime API requests use the configured API base URL and bearer token.
- The server entrypoint loads the tool catalog and starts the Hostinger API MCP server.
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.5.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.5.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.