registry / hostinger-api-mcp / 1.52.0

hostinger-api-mcp@1.52.0

MCP server for Hostinger API

AI Security Review

scanned 6d ago · by lpm-firewall-ai

Source inspection found expected Hostinger API and OAuth behavior, with no install-time hook or concrete attack behavior. The flagged build command is part of the explicit build script and invokes TypeScript compilation.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user starts the MCP server or invokes one of its listed API tools; the separate build command runs only when requested.

Impact

No confirmed unauthorized credential disclosure, persistence, or destructive behavior was established.

Mechanism

The server sends authenticated API requests to the configured API base URL, which defaults to Hostinger, and OAuth uses Hostinger’s auth service by default.

AI rationale

Evidence

package.jsonsrc/servers/all.jssrc/core/tools/all.jssrc/core/runtime.jssrc/core/oauth.jsbuild.js

Network endpoints2

auth.hostinger.comdevelopers.hostinger.com

Decision evidence

public snapshot

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

Evidence for AI clean decision

The manifest points to the package’s MCP server entrypoint; no install lifecycle hook is declared.
The build script explicitly runs the TypeScript compiler and copies project files into the build directory.
OAuth uses Hostinger’s auth service by default and sends authorization or refresh grant data to its token endpoint.
OAuth credentials are stored in the user configuration directory with restrictive Unix file permissions.
Runtime API requests use the Hostinger developer API by default; the configurable base URL receives the bearer token as part of ordinary API requests.
The generated tool list describes caller-requested Hostinger API operations.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

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 }

src/core/oauth.jsView file

•matchType = previous_version_dangerous_delta matchedPackage = hostinger-api-mcp@1.57.0 matchedIdentity = npm:aG9zdGluZ2VyLWFwaS1tY3A:1.57.0 similarity = 0.804 summary = stored previous version shares package body but lacks this dangerous source file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

src/core/oauth.jsView on unpkg

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.js", "hostinger-billing-mcp": "./src/servers/b

Low

Suspicious Lifecycle Evidence

The manifest points to the package’s MCP server entrypoint; no install lifecycle hook is declared.

package.jsonView on unpkg · L18

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

src/core/oauth.jsView file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

src/core/oauth.js

Findings

1 Critical3 High3 Medium5 Low

CriticalPrevious Version Dangerous Deltasrc/core/oauth.js

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@1.52.0.

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

Review the evidence and your use of hostinger-api-mcp@1.52.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-17 08:02:19.788Z (UTC).

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