@hostinger/mcp@2.10.0
MCP server for Hostinger API
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe build scanner hints are explained by an explicit build script and do not establish install-time behavior. The runtime’s unrestricted API base URL can receive an existing bearer token, which warrants a warning for conditional credential exposure rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user starts the server with an API base URL pointing outside Hostinger and invokes an API tool.
Impact
Conditional exposure of the Hostinger API token to the configured recipient; no automatic exfiltration was identified.
Mechanism
The runtime obtains an environment or OAuth token, places it in the Authorization header, and sends the request to the configured URL.
AI rationale
The build scanner hints are explained by an explicit build script and do not establish install-time behavior. The runtime’s unrestricted API base URL can receive an existing bearer token, which warrants a warning for conditional credential exposure rather than a block.
Evidence
src/core/runtime.jssrc/core/oauth.js
Network endpoints1
developers.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runtime API requests send a bearer token to the configured API base URL, which has no visible host allowlist.
- The bearer token can come from environment variables or stored OAuth credentials.
- The package defaults API requests to Hostinger’s developer API; the credential exposure requires configuring another API base URL.
- The manifest has no lifecycle hooks; its build script invokes the compiler when run.
- The build script only compiles TypeScript and copies package files.
Evidence against
- The flagged package-manager invocation occurs in the explicit build script, not an install lifecycle hook.
- The default API destination is developers.hostinger.com.
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 · L1819exec('npx tsc', (error, stdout, stderr) => {
if (error) {
console.error('Error compiling TypeScript:', error);
console.error(stderr);
process.exit(1);
}
Medium
Ai Review Evidence
The build script only compiles TypeScript and copies package files.
build.jsView on unpkg · L19package.jsonView file
Findings
3 High5 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidencebuild.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.10.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.10.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.