registry / @hostinger/mcp / 2.14.0
@hostinger/mcp@2.14.0
MCP server for Hostinger API
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged build helper compiles TypeScript and prepares a distribution directory. Runtime credential transport is part of MCP-requested API operations to a user-configurable API base that defaults to Hostinger; no separate malicious transfer behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
An MCP client requests an API operation through the execute tool.
Impact
No attack impact was identified; the inspected requests support the requested API operations.
Mechanism
The server sends the requested operation to the configured API base, which defaults to Hostinger's developer API, using its bearer token.
AI rationale
The manifest has no install lifecycle hook, and the flagged build helper compiles TypeScript and prepares a distribution directory. Runtime credential transport is part of MCP-requested API operations to a user-configurable API base that defaults to Hostinger; no separate malicious transfer behavior was identified.
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 declares only start, build, and start:ts scripts; no npm lifecycle hook is declared.
- build.js runs the TypeScript compiler and copies package files into dist.
- Runtime API requests default to Hostinger's developer API; the API base and headers can be configured by the user.
- Remote API operations run in response to an MCP execute request.
- The agency upload-credential request sends a bearer token to a URL built from the configured API base.
- The hosting upload-credential request also sends a bearer token to a URL built from the configured API base.
Evidence against
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:'
Low
Ai Review Evidence
build.js runs the TypeScript compiler and copies package files into dist.
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.14.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.14.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.