hostinger-api-mcp@2.3.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe source forwards saved access and refresh tokens to configurable destinations without host allowlisting, so an alternate configuration can expose credentials. The default destinations are Hostinger and no install-time transfer is present, supporting a warning rather than a block.
Decision evidence
public snapshot- The OAuth provider loads and saves user credentials, then supplies an access token for authenticated requests.
- API requests use an environment-configurable base URL that defaults to Hostinger; source does not restrict the override to Hostinger hosts.
- Authenticated API request handlers send bearer tokens to URLs built from that configurable base URL; the MCP entrypoint exposes these actions through client tool requests.
- The OAuth issuer is also environment-configurable, and the provider sends a stored refresh token to that issuer during refresh.
- The manifest has no install lifecycle hook, and its build script runs the TypeScript compiler.
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.3.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.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.