hostinger-api-mcp@2.7.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged build execution invokes the TypeScript compiler, and the inspected credential flows target Hostinger by default or a destination explicitly configured by the operator.
Decision evidence
public snapshot- The manifest points its executable entrypoints to server files and lists start, build, and start:ts scripts; it declares no install lifecycle hook.
- The build script runs the TypeScript compiler and copies project files into dist.
- OAuth defaults to Hostinger’s auth service; login and refresh send their grants to the configured issuer.
- The runtime uses the Hostinger developer API by default and attaches its bearer token to API requests; a custom base URL or OAuth issuer must be configured by the operator.
- The server entrypoint wires a generated API tool list into the runtime; the inspected tool source contains declarative operation metadata.
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.7.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.7.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.