registry / @hostinger/mcp / 3.25.1
@hostinger/mcp@3.25.1
MCP server for Hostinger API
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reviewed behavior matches a Hostinger API MCP server: runtime credentials support requests to the Hostinger API, and the flagged shell execution is a manually invoked build step for TypeScript compilation. The skills file is served as MCP content rather than run as package code.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The server starts when the user launches its command or imports its entry point; API operations run when requested through MCP.
Impact
No malicious credential collection, unrelated data transfer, or unauthorized action was found.
Mechanism
The runtime sends authenticated API requests to Hostinger's API, using the configured base URL or developers.hostinger.com by default.
AI rationale
The reviewed behavior matches a Hostinger API MCP server: runtime credentials support requests to the Hostinger API, and the flagged shell execution is a manually invoked build step for TypeScript compilation. The skills file is served as MCP content rather than run as package code.
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package entry point starts the Hostinger API MCP server and loads its tools and skills.
- Runtime API requests use developers.hostinger.com by default; API_BASE_URL can override it.
- The runtime obtains a bearer token through its OAuth provider for API requests.
- build.js invokes npx tsc only when the build script is run; package.json declares no lifecycle scripts.
- The large skills file is served as MCP skill content.
Evidence against
- The build script executes a child process, but only for the TypeScript compiler when manually run.
- Runtime API calls use bearer credentials, but are directed to the configured Hostinger API endpoint.
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 · L18src/core/skills.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @hostinger/mcp@3.24.0
matchedIdentity = npm:QGhvc3Rpbmdlci9tY3A:3.24.0
similarity = 0.866
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.
Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltasrc/core/skills.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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @hostinger/mcp@3.25.1.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@3.25.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.