registry / @hostinger/mcp / 3.2.2
@hostinger/mcp@3.2.2
MCP server for Hostinger API
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no install-time lifecycle hook or concrete attack behavior. The flagged build command is an explicit compiler build, and runtime authentication serves the package’s Hostinger API function.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the server entry point or explicitly invoking the build script.
Impact
No confirmed unauthorized collection, disclosure, persistence, or destructive behavior was established.
Mechanism
The server sends bearer-authenticated API requests to its configured API base URL; OAuth defaults to Hostinger’s authentication issuer.
AI rationale
Source inspection found no install-time lifecycle hook or concrete attack behavior. The flagged build command is an explicit compiler build, and runtime authentication serves the package’s Hostinger API function.
Evidence
build.jssrc/core/runtime.jssrc/core/oauth.js
Network endpoints2
developers.hostinger.comauth.hostinger.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines start, build and start:ts scripts but no install lifecycle hook.
- build.js runs the TypeScript compiler and copies package files into dist when the explicit build script is run.
- The all-server entry point starts the Hostinger API MCP server and loads its generated tool list.
- Runtime API requests use the configured API base URL, defaulting to developers.hostinger.com, and send the bearer token to that request URL.
- OAuth uses auth.hostinger.com by default and exchanges tokens with the configured issuer.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 flaggedbuild.jsView file
2L3: import { exec } from 'child_process';
L4: import fs from 'fs';
High
18console.log('Compiling TypeScript...');
L19: exec('npx tsc', (error, stdout, stderr) => {
L20: if (error) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
build.jsView on unpkg · L1819exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('Error compiling TypeScript:', error);
console.error(stderr);
process.exit(1);
Low
Ai Review Evidence
build.js runs the TypeScript compiler and copies package files into dist when the explicit build script is run.
build.jsView on unpkg · L19package.jsonView file
Findings
3 High3 Medium6 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencebuild.js
Affected versions and remediation
This report applies to @hostinger/mcp@3.2.2.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.2.2 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.