@hostinger/mcp@2.17.0
MCP server for Hostinger API
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe configurable API and OAuth destinations can receive existing Hostinger credentials without a source-level host restriction, creating a conditional credential exposure risk. The defaults are Hostinger services, and the API transfer requires an invoked operation, so the evidence supports a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
The server handles an execute request while API_BASE_URL points to an untrusted destination; OAuth refresh requests use OAUTH_ISSUER.
Impact
A configured recipient could receive a Hostinger access token or refresh token.
Mechanism
The runtime attaches its bearer token to API requests without binding it to the default Hostinger host, and OAuth refresh sends the stored refresh token to the configured issuer.
AI rationale
The configurable API and OAuth destinations can receive existing Hostinger credentials without a source-level host restriction, creating a conditional credential exposure risk. The defaults are Hostinger services, and the API transfer requires an invoked operation, so the evidence supports a warning rather than a block.
Evidence
src/core/runtime.jssrc/core/oauth.js
Network endpoints2
developers.hostinger.comauth.hostinger.com
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- API_BASE_URL sets the API destination, defaulting to developers.hostinger.com; API request URLs are built from that value.
- An MCP execute request invokes an API operation that attaches the bearer token obtained by the runtime.
- Both inspected upload credential requests also attach the bearer token and send requests through the configured API destination.
- OAUTH_ISSUER can change the OAuth destination, and refresh requests send the stored refresh token to that issuer.
- The manifest has no install hook; its build script runs the TypeScript compiler when invoked.
Evidence against
- The default API and OAuth destinations are Hostinger services.
- The API credential transfer occurs when the server handles an execute request, rather than automatically during installation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
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/runtime.jsView file
79this.debug = process.env.DEBUG === "true";
this.baseUrl = process.env.API_BASE_URL || "https://developers.hostinger.com";
this.headers = this.parseH
Medium
Ai Review Evidence
API_BASE_URL sets the API destination, defaulting to developers.hostinger.com; API request URLs are built from that value.
src/core/runtime.jsView on unpkg · L79Findings
3 High5 Medium4 Low
HighChild Processbuild.js
HighShell
HighRuntime Package Installbuild.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencesrc/core/runtime.js
MediumAi Review Evidencesrc/core/runtime.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hostinger/mcp@2.17.0.
See all versions of @hostinger/mcp for other recorded verdicts.
- Review the evidence and your use of @hostinger/mcp@2.17.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.