hostinger-api-mcp@3.0.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the flagged build command is part of an explicit build script. Inspected OAuth and API requests use Hostinger defaults and are tied to sign-in or MCP tool operations; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json lists start, build, and TypeScript start scripts, with no install lifecycle hook.
- The bundled catalog exposes named Hostinger MCP tools; the runtime runs operations in response to MCP tool calls.
- build.js runs the TypeScript compiler as an explicit build step.
- OAuth uses the Hostinger authentication service by default; saved-token refreshes go to the configured issuer.
- Runtime API calls attach a bearer token to requests built from the configurable API base.
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@3.0.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.0.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.