hostinger-api-mcp@2.15.0
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution is part of the explicit build command and runs the TypeScript compiler. OAuth and API traffic follow the package’s Hostinger authentication and API flows; no concrete malicious behavior was found.
Decision evidence
public snapshot- The manifest points to the server entrypoint and defines a build script, with no install lifecycle hook.
- The build script runs the TypeScript compiler and handles build output.
- The OAuth provider defaults to Hostinger’s authentication service; an alternate issuer must be configured explicitly.
- OAuth token exchange posts authorization data to the configured issuer.
- The server exposes catalogued tools and executes operations only in response to tool calls.
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.15.0.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@2.15.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.