@hostinger/mcp@3.17.3
MCP server for Hostinger API
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution belongs to the build compiler or an explicitly run connection bootstrap. The inspected OAuth flow targets Hostinger, and the package declares no install lifecycle hook.
Decision evidence
public snapshot- package.json declares start, build and start:ts scripts, with no install lifecycle script.
- build.js runs the TypeScript compiler and copies package files into dist.
- OAuth defaults to auth.hostinger.com and defines Hostinger OAuth registration, authorization, token and revocation routes.
- OAuth exchanges an authorization code and PKCE verifier with the configured issuer as part of sign-in.
- The headless bootstrap selects npx to invoke @hostinger/mcp@latest when the bootstrap is run.
- src/core/skills.js contains agent skill instructions for connecting to the Hostinger MCP.
- The OAuth credentials are stored for Hostinger MCP use; the inspected code does not send them to an unrelated host.
- The bootstrap and its npx invocation are part of an explicit connection flow, not an install hook.
- The build script's shell execution is limited to running the TypeScript compiler.
Source & flagged code
7 flaggedPackage source invokes a package manager install command at runtime.
build.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
build.jsView on unpkgFindings
Affected versions and remediation
This report applies to @hostinger/mcp@3.17.3.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.17.3 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.