hostinger-api-mcp@1.60.2
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged build script runs TypeScript compilation when manually invoked, and the manifest has no install lifecycle hook. Runtime API calls follow client tool requests and use the configured API base URL, which defaults to Hostinger; no publisher-selected credential recipient or other attack was identified.
Decision evidence
public snapshot- The manifest points to the server entrypoint and lists no install lifecycle hook.
- The build script runs TypeScript compilation when invoked.
- Tools are executed in response to MCP client requests.
- OAuth defaults to Hostinger and can use an explicitly configured issuer.
- API requests use the configured API base URL, defaulting to Hostinger, and attach the bearer token for authentication.
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@1.60.2.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.60.2 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.