registry / @hostinger/mcp / 2.11.0
@hostinger/mcp@2.11.0
MCP server for Hostinger API
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe flagged process execution belongs to an explicit build script, and there is no install lifecycle hook. The inspected runtime behavior aligns with a Hostinger API client and does not establish malicious activity.
Static reason
One or more suspicious static signals were detected.
Trigger
A user starts the MCP server and invokes an API tool; the compiler command runs only when the user runs the build script.
Impact
No confirmed attack surface was established from the inspected behavior.
Mechanism
The runtime builds API request URLs from API_BASE_URL, defaulting to the Hostinger developer API, and attaches the bearer token to those requests.
AI rationale
The flagged process execution belongs to an explicit build script, and there is no install lifecycle hook. The inspected runtime behavior aligns with a Hostinger API client and does not establish malicious activity.
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has start and build scripts but no install lifecycle hook.
- build.js invokes the TypeScript compiler as part of the explicit build script.
- src/core/runtime.js defaults API requests to https://developers.hostinger.com.
- The runtime constructs API URLs from that base and sends its bearer token in the request authorization header.
- The main entrypoint starts the Hostinger API server; runtime defaults to stdio on localhost.
Evidence against
- The runtime supports an API base URL supplied through API_BASE_URL, and sends authentication to URLs built from it.
- build.js invokes npx tsc, but package.json exposes this only through the explicit build script.
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 · L1817// Run TypeScript compiler
console.log('Compiling TypeScript...');
exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('Error compiling TypeScript:', error);
co
Low
Ai Review Evidence
build.js invokes the TypeScript compiler as part of the explicit build script.
build.jsView on unpkg · L17package.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@2.11.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.11.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.