registry / @hostinger/mcp / 2.15.0
@hostinger/mcp@2.15.0
MCP server for Hostinger API
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete malicious behavior. The flagged child-process use is part of the explicit build script, while runtime requests and OAuth target Hostinger services by default.
Static reason
One or more suspicious static signals were detected.
Trigger
A user or MCP client invokes an API operation, or a developer runs the build script.
Impact
No confirmed unauthorized credential disclosure, install-time mutation, or other attack impact was found.
Mechanism
The runtime sends API requests using the configured base URL, which defaults to Hostinger's developer service; OAuth defaults to Hostinger's authentication service. The build script invokes the TypeScript compiler and copies files.
AI rationale
Source inspection found no install lifecycle hook or concrete malicious behavior. The flagged child-process use is part of the explicit build script, while runtime requests and OAuth target Hostinger services by default.
Evidence
package.jsonbuild.jssrc/core/runtime.jssrc/core/oauth.js
Network endpoints2
developers.hostinger.comauth.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
- The manifest defines start, build and start:ts scripts, with no install lifecycle hook.
- The flagged build script invokes the TypeScript compiler and copies package files when run.
- Runtime API requests default to developers.hostinger.com; inspected calls send requests to their configured API URLs.
- OAuth defaults to auth.hostinger.com, and operation execution is routed through MCP tool requests.
- The inspected runtime behavior shows no confirmed attack surface.
Evidence against
- The scanner flagged network access and child-process use; source inspection ties these signals to API requests and build-time compilation.
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);
console.error(stderr);
p
Low
Ai Review Evidence
The flagged build script invokes the TypeScript compiler and copies package files when run.
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.15.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.15.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.