hostinger-api-mcp@3.3.0
MCP server for Hostinger API
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source supports a conditional credential exposure warning: an unrestricted API_BASE_URL can redirect requests that carry a Hostinger access token. The Hostinger default, absence of install hooks, and explicit build behavior do not establish a covert attack or malicious intent.
Decision evidence
public snapshot- The runtime accepts API_BASE_URL and defaults to the Hostinger API host.
- Authenticated API requests use a bearer token in the Authorization header and build their URL from the configured base.
- The OAuth provider reuses a saved access token; the runtime obtains tokens through that provider.
- The Cursor instructions describe optional user configuration, not an automatic configuration write.
- The manifest has no install lifecycle hook; its build script runs the TypeScript compiler.
- The bootstrap invokes the Hostinger package through npx as part of its sign-in flow.
- The default API destination is Hostinger, and the reviewed code does not show an automatic transfer to a fixed unrelated host.
- The package has no install lifecycle hook; the flagged build command is an explicit build step.
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.
Findings
Affected versions and remediation
This report applies to hostinger-api-mcp@3.3.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.3.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.