registry / hostinger-api-mcp / 2.0.0

hostinger-api-mcp@2.0.0

MCP server for Hostinger API

AI Security Review

scanned 6d ago · by lpm-firewall-ai

Inspected source shows no lifecycle hook and no malicious behavior. The flagged process execution is tied to the explicit build command and requested browser-based OAuth login, while authentication and API calls target Hostinger services.

Static reason

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

Trigger

The user runs the package server, requests OAuth login, or explicitly runs the build script.

Impact

These inspected behaviors support the package's stated API-client function; no unrelated credential transfer or hidden install-time action was found.

Mechanism

OAuth exchanges login credentials with Hostinger; API requests use the configured Hostinger API base URL. The build script runs the TypeScript compiler, and OAuth may open the authorization page in a browser.

AI rationale

Evidence

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

Network endpoints3

auth.hostinger.comdevelopers.hostinger.com127.0.0.1

Decision evidence

public snapshot

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

Evidence for AI clean decision

package.json defines start and build scripts, with no install lifecycle hook.
The build script invokes the TypeScript compiler as part of the package's explicit build command.
OAuth defaults to Hostinger's authorization service and exchanges the browser authorization code there.
OAuth launches the authorization URL in the browser when login is requested.
The runtime defaults API requests to Hostinger's developer API and sends the bearer token in the request authorization header.
The package entrypoint starts the Hostinger API MCP server with its generated tools.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsMinifiedUrlStrings

ManifestNo manifest risk signals triggered.

scanned 58 file(s), 2.27 MB of source, external domains: 127.0.0.1, api.mail.hostinger.com, auth.hostinger.com, developers.hostinger.com, github.com, hpanel.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);

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.589 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

35"scripts": { "start": "node src/servers/all.js", "build": "node build.js", "start:ts": "npx tsc && node dist/src/servers/all.js" }, "dependencies": { "@modelcon

Low

Suspicious Lifecycle Evidence

package.json defines start and build scripts, with no install lifecycle hook.

package.jsonView on unpkg · L35

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

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

Review the evidence and your use of hostinger-api-mcp@2.0.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:03:33.815Z (UTC).

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