hostinger-api-mcp@3.4.0
MCP server for Hostinger API
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe runtime forwards its Hostinger bearer token to any endpoint selected through API_BASE_URL, with no recipient binding in the request path. Because this requires a configured alternate endpoint and an invoked operation, the evidence supports a warning rather than a publish block.
Decision evidence
public snapshot- runtime.js accepts API_BASE_URL and defaults it to https://developers.hostinger.com.
- oauth.js obtains a bearer token from environment configuration or OAuth, loads saved credentials, and defaults its OAuth issuer to auth.hostinger.com.
- runtime.js builds operation URLs from the configured base, adds the bearer token to Authorization, and sends the request with axios.
- An MCP client must invoke execute to reach the operation request path.
- package.json lists start, build, and start:ts scripts; build.js runs npx tsc.
- The cited skills.js and skills.ts locations describe optional project or global Cursor configuration for the user to register.
- The default API URL and OAuth issuer are Hostinger endpoints; the credential exposure requires configuring a different API_BASE_URL.
- The manifest has no install lifecycle script, and the operation request requires an MCP client call.
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/skills.jsFindings
Affected versions and remediation
This report applies to hostinger-api-mcp@3.4.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@3.4.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.