registry / hostinger-api-mcp / 3.4.1

hostinger-api-mcp@3.4.1

MCP server for Hostinger API

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Source inspection found no install hook or concrete attack behavior. The scanner’s build and child-process signals correspond to a manually invoked TypeScript build, while runtime authentication and API requests target Hostinger services.

Static reason

One or more suspicious static signals were detected.

Trigger

A user invokes the server or explicitly runs the build script.

Impact

No confirmed malicious effect or attack surface was established.

Mechanism

The server dispatches requested MCP tool calls to configured API operations; the build script invokes the TypeScript compiler.

AI rationale

Evidence

package.jsonbuild.jssrc/servers/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

The manifest exposes the server entrypoint and lists only start, build, and TypeScript start scripts; it has no install lifecycle hook.
The server handles API calls when an MCP tool is invoked and defaults API requests to the Hostinger developer API.
OAuth uses Hostinger’s authentication issuer, while API tokens are read from caller-provided environment variables.
The flagged build command runs the TypeScript compiler when explicitly invoked; no package-install behavior was identified in it.
Inspected dependency excerpts show ordinary MCP transport, HTTP client cancellation, and CORS middleware code.

Evidence against

No inspected source established credential transfer to an unrelated recipient, automatic account actions, persistence, destructive behavior, or install-time execution.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStrings

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);

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 1-56json

2 "name": "hostinger-api-mcp",

3 "version": "3.4.1",

4 "mcpName": "io.github.hostinger/hostinger-api-mcp",

5 "description": "MCP server for Hostinger API",

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

package.jsonView file

18"type": "module", "main": "./src/servers/all.js", "bin": { "hostinger-api-mcp": "./src/servers/all.js", "hostinger-agency-hosting-mcp": "./src/servers/agency-hosting.

Low

Suspicious Lifecycle Evidence

The manifest exposes the server entrypoint and lists only start, build, and TypeScript start scripts; it has no install lifecycle hook.

package.jsonView on unpkg · L18

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

Affected versions and remediation

This report applies to hostinger-api-mcp@3.4.1.

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

Review the evidence and your use of hostinger-api-mcp@3.4.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: 2026-10-21 08:02:14.167Z (UTC).

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