hostinger-api-mcp@2.5.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged install and process-execution signals do not establish malicious behavior: the manifest has no lifecycle hook, and build.js runs the compiler under an explicit build script. Inspected authentication and API requests are consistent with the Hostinger client’s stated function; the configurable issuer and API base URL do not alone establish credential exfiltration.
Decision evidence
public snapshot- The manifest defines start, build, and start:ts scripts but no install lifecycle hook.
- The flagged build command runs TypeScript compilation as an explicit build script.
- The OAuth code exchanges tokens with the configured issuer, defaulting to Hostinger’s authentication service.
- Runtime API requests are initiated by MCP tool calls and send bearer credentials to the configured API base URL, which defaults to Hostinger’s developer API.
- The all-server entrypoint loads the generated tool catalog and starts the 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.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.5.1 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.