@hostinger/mcp@3.25.0
MCP server for Hostinger API
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected execution and credential flows match the package’s stated purpose as a Hostinger API MCP server. The scanner’s build and download leads resolve to a compiler invocation and documented, user-followed setup instructions; no unrelated credential transport or automatic install behavior was found.
Decision evidence
public snapshot- The package manifest points to the Hostinger MCP server and declares no lifecycle scripts.
- build.js runs the TypeScript compiler when the build script is explicitly invoked; it does not download or execute remote code.
- The server uses developers.hostinger.com by default, with API_BASE_URL allowing a user-configured service endpoint.
- API requests are constructed from the configured base URL and operation path.
- A skill documents downloading a bootstrap script from the package’s own GitHub repository as a user-followed setup step.
Source & flagged code
4 flaggedPackage 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.
Findings
Affected versions and remediation
This report applies to @hostinger/mcp@3.25.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.25.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.