hostinger-api-mcp@1.61.1
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged build execution is limited to the explicit compiler build command. Inspected OAuth and runtime request paths target Hostinger services by default and align with the package's declared API-server purpose.
Decision evidence
public snapshot- package.json exposes server entrypoints and start/build scripts, with no install lifecycle hook.
- build.js runs the TypeScript compiler when the explicit build script is invoked.
- OAuth uses Hostinger's authentication issuer for token operations.
- The runtime defaults to Hostinger's API and sends bearer credentials to the URL built from that configured API base.
- The exported tool list presents user-invoked Hostinger API operations.
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@1.61.1.
See all versions of hostinger-api-mcp for other recorded verdicts.
- Review the evidence and your use of hostinger-api-mcp@1.61.1 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.