registry / hostinger-api-mcp / 3.2.0

hostinger-api-mcp@3.2.0

MCP server for Hostinger API

AI Security Review

scanned 4d ago · by lpm-firewall-ai

The manifest has no install lifecycle hook, and the flagged build command is an explicit TypeScript compilation step. Inspected runtime and OAuth code send credentials to Hostinger service endpoints and save OAuth credentials locally; no concrete attack surface was established.

Static reason

One or more suspicious static signals were detected.

Trigger

A user runs the MCP server or invokes a tool; compilation runs only when the build script is explicitly run.

Impact

Inspected behavior supports the package's stated API-client function; no unrelated credential transfer or automatic install-time action was found.

Mechanism

The runtime sends authenticated API requests to the configured API base URL, which defaults to Hostinger. OAuth uses Hostinger's issuer and stores credentials locally.

AI rationale

Evidence

package.jsonbuild.jssrc/core/tools/all.jssrc/core/runtime.jssrc/core/oauth.js

Network endpoints2

developers.hostinger.comauth.hostinger.com

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json defines start, build and start:ts scripts, with no install lifecycle hook.
build.js runs the TypeScript compiler as part of the explicit build command.
The main tool entry is a Hostinger API tool list; runtime requests use the Hostinger developer API by default.
OAuth uses Hostinger's authentication issuer, and saved credentials are written locally.

Evidence against

The scanner's child-process signal maps to the build script's compiler command and OAuth's browser-launch helper; inspected source does not show covert execution or credential export.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsMinifiedUrlStrings

ManifestNo manifest risk signals triggered.

scanned 66 file(s), 2.74 MB of source, external domains: 127.0.0.1, api-ecommerce.hostinger.com, api.ipify.org, api.mail.hostinger.com, auth.hostinger.com, checkout.hostinger.com, developers.hostinger.com, github.com, hpanel.hostinger.com, www.hostinger.com, www.monarx.com

Source & flagged code

4 flagged

build.jsView file

Lines 1-38javascript

1#!/usr/bin/env node

3import { exec } from 'child_process';

4import fs from 'fs';

High

Child Process

Package source references child process execution.

build.jsView on unpkg · L2

5import path from 'path';

6import { fileURLToPath } from 'url';

8// Get proper paths for ES modules

9const __filename = fileURLToPath(import.meta.url);

10const __dirname = path.dirname(__filename);

12// Ensure dist directory exists

13if (!fs.existsSync('./dist')) {

14 fs.mkdirSync('./dist');

15}

17// Run TypeScript compiler

18console.log('Compiling TypeScript...');

19exec('npx tsc', (error, stdout, stderr) => {

20 if (error) {

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

build.jsView on unpkg · L18

21 console.error('Error compiling TypeScript:', error);

Low

Ai Review Evidence

build.js runs the TypeScript compiler as part of the explicit build command.

build.jsView on unpkg · L17

22 console.error(stderr);

23 process.exit(1);

24 }

26 if (stdout) {

27 console.log(stdout);

28 }

30 console.log('TypeScript compilation successful');

32 // Copy .env.example to dist

33 try {

34 if (fs.existsSync('./.env.example')) {

35 fs.copyFileSync('./.env.example', './dist/.env.example');

36 console.log('Copied .env.example to dist directory');

37 }

package.jsonView file

Lines 16-56json

16 "api"

17 ],

18 "type": "module",

19 "main": "./src/servers/all.js",

20 "bin": {

21 "hostinger-api-mcp": "./src/servers/all.js",

Source & flagged code

4 flagged · loading source

build.jsView file

2L3: import { exec } from 'child_process'; L4: import fs from 'fs';

High

Child Process

Package source references child process execution.

build.jsView on unpkg · L2

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 · L18

17// Run TypeScript compiler console.log('Compiling TypeScript...'); exec('npx tsc', (error, stdout, stderr) => { if (error) { console.error('Error compiling TypeScript:'

Low

Ai Review Evidence

build.js runs the TypeScript compiler as part of the explicit build command.

build.jsView on unpkg · L17

package.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-api-mcp@3.2.0.

See all versions of hostinger-api-mcp for other recorded verdicts.

Review the evidence and your use of hostinger-api-mcp@3.2.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: 2026-10-19 06:31:04.305Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.