hostinger-api-mcp 1.61.0 → 1.61.2

package/CHANGELOG.md

@@ -4,6 +4,20 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v1.61.2 — 2026-09-21
+
+### Also in this release
+
+- Dependencies: `package-lock.json`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Other files: `.gitignore`
+
+## v1.61.1 — 2026-09-17
+
+### Also in this release
+
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+
 ## v1.61.0 — 2026-09-16
 
 ### Tools

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.61.0",
+  "version": "1.61.2",
   "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
   "mcpServers": {
     "hostinger": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.61.0",
+  "version": "1.61.2",
   "mcpName": "io.github.hostinger/hostinger-api-mcp",
   "description": "MCP server for Hostinger API",
   "repository": {

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/hostinger/api-mcp-server",
     "source": "github"
   },
-  "version": "1.61.0",
+  "version": "1.61.2",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "1.61.0",
+      "version": "1.61.2",
       "transport": {
         "type": "stdio"
       },

package/src/core/runtime.js

@@ -10,6 +10,8 @@ import { config as dotenvConfig } from "dotenv";
 import {
   ListToolsRequestSchema,
   CallToolRequestSchema,
+  ErrorCode,
+  McpError,
 } from "@modelcontextprotocol/sdk/types.js";
 import { OAuthProvider, getEnvToken } from "./oauth.js";
 import * as tus from "tus-js-client";
@@ -19,6 +21,19 @@ import path from "path";
 // Load environment variables
 dotenvConfig({ quiet: true });
 
+/**
+ * An upstream API call that came back as a failure. Carries the status and the
+ * API's own response body so the CallTool handler can hand both to the model.
+ */
+class ApiExecutionError extends Error {
+  constructor(status, data, message) {
+    super(message || `API request failed with status ${status}`);
+    this.name = 'ApiExecutionError';
+    this.status = status;
+    this.responseData = data;
+  }
+}
+
 const SECURITY_SCHEMES = {
   "apiToken": {
     "type": "http",
@@ -29,7 +44,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.53.0
+ * Generated from OpenAPI spec version 1.53.1
  */
 class MCPServer {
   constructor({ name, version, tools }) {
@@ -157,13 +172,17 @@ class MCPServer {
         }
       }
 
+      // An unknown tool is a protocol error, not a tool execution error: the
+      // model cannot self-correct its way out of a name the server does not
+      // have. -32602 is what the spec's example and the SDK's own McpServer
+      // use; a plain Error would go out as -32603 instead.
       if (!toolName) {
-        throw new Error(`Tool not found: ${name}`);
+        throw new McpError(ErrorCode.InvalidParams, `Tool not found: ${name}`);
       }
 
       toolDetails = this.toolList.find(t => t.name === toolName);
       if (!toolDetails) {
-        throw new Error(`Tool details not found for ID: ${toolName}`);
+        throw new McpError(ErrorCode.InternalError, `Tool details not found for ID: ${toolName}`);
       }
 
       try {
@@ -189,10 +208,32 @@ class MCPServer {
 
       } catch (error) {
         const errorMessage = error instanceof Error ? error.message : String(error);
-        const response = error.response;
         this.log('error', `Error executing tool ${name}: ${errorMessage}`);
 
-        throw error;
+        // MCP reports tool execution failures (API errors, bad input, business
+        // logic) inside the result with isError: true. Throwing here would turn
+        // them into JSON-RPC protocol errors instead, which the spec reserves
+        // for unknown tools and malformed requests — those are still thrown,
+        // above, before this try. The status stays in the text so the model can
+        // tell a retryable 429/503 from a 403 it should not retry.
+        let errorText = errorMessage;
+        if (error instanceof ApiExecutionError) {
+          const payload = error.responseData;
+          const body = payload === null || payload === undefined || payload === ''
+            ? errorMessage
+            : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
+          errorText = error.status ? `HTTP ${error.status}: ${body}` : body;
+        }
+
+        return {
+          isError: true,
+          content: [
+            {
+              type: "text",
+              text: errorText
+            }
+          ]
+        };
       }
     });
   }
@@ -2474,6 +2515,13 @@ class MCPServer {
         this.log('debug', `Retry response status: ${response.status}`);
       }
 
+      // validateStatus resolves everything under 500, so a 4xx arrives here as
+      // an ordinary response. Without this it would be returned to the model as
+      // a successful tool result whose body happens to be the API's error.
+      if (response.status >= 400) {
+        throw new ApiExecutionError(response.status, response.data);
+      }
+
       return response.data;
 
     } catch (error) {
@@ -2489,10 +2537,14 @@ class MCPServer {
           data: typeof responseData === 'object' ? JSON.stringify(responseData) : responseData
         });
 
-        // Rethrow with more context for better error handling
-        const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
-        detailedError.response = error.response;
-        throw detailedError;
+        // Structured so the CallTool handler can report this as an MCP tool
+        // execution error carrying the API's own payload. Status is 0 for a
+        // transport failure (DNS, ECONNREFUSED, timeout) — there is no response.
+        throw new ApiExecutionError(
+          responseStatus ?? 0,
+          responseData,
+          `API request failed with status ${responseStatus}: ${errorMessage}`
+        );
       }
 
       throw error;

package/src/core/runtime.ts

@@ -10,6 +10,8 @@ import { config as dotenvConfig } from "dotenv";
 import {
   ListToolsRequestSchema,
   CallToolRequestSchema,
+  ErrorCode,
+  McpError,
   Tool,
 } from "@modelcontextprotocol/sdk/types.js";
 import { OAuthProvider, getEnvToken } from "./oauth.js";
@@ -42,6 +44,22 @@ interface SecurityScheme {
   scheme?: string;
 }
 
+/**
+ * An upstream API call that came back as a failure. Carries the status and the
+ * API's own response body so the CallTool handler can hand both to the model.
+ */
+class ApiExecutionError extends Error {
+  public readonly status: number;
+  public readonly responseData: any;
+
+  constructor(status: number, data: any, message?: string) {
+    super(message || `API request failed with status ${status}`);
+    this.name = 'ApiExecutionError';
+    this.status = status;
+    this.responseData = data;
+  }
+}
+
 const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
   "apiToken": {
     "type": "http",
@@ -52,7 +70,7 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.53.0
+ * Generated from OpenAPI spec version 1.53.1
  */
 class MCPServer {
   private readonly name: string;
@@ -188,13 +206,17 @@ class MCPServer {
         }
       }
 
+      // An unknown tool is a protocol error, not a tool execution error: the
+      // model cannot self-correct its way out of a name the server does not
+      // have. -32602 is what the spec's example and the SDK's own McpServer
+      // use; a plain Error would go out as -32603 instead.
       if (!toolName) {
-        throw new Error(`Tool not found: ${name}`)
+        throw new McpError(ErrorCode.InvalidParams, `Tool not found: ${name}`);
       }
 
       toolDetails = this.toolList.find(t => t.name === toolName);
       if (!toolDetails) {
-        throw new Error(`Tool details not found for ID: ${toolName}`);
+        throw new McpError(ErrorCode.InternalError, `Tool details not found for ID: ${toolName}`);
       }
         
       try {
@@ -221,8 +243,31 @@ class MCPServer {
       } catch (error) {
         const errorMessage = error instanceof Error ? error.message : String(error);
         this.log('error', `Error executing tool ${toolName}: ${errorMessage}`);
-        
-        throw error;
+
+        // MCP reports tool execution failures (API errors, bad input, business
+        // logic) inside the result with isError: true. Throwing here would turn
+        // them into JSON-RPC protocol errors instead, which the spec reserves
+        // for unknown tools and malformed requests — those are still thrown,
+        // above, before this try. The status stays in the text so the model can
+        // tell a retryable 429/503 from a 403 it should not retry.
+        let errorText: string = errorMessage;
+        if (error instanceof ApiExecutionError) {
+          const payload = error.responseData;
+          const body = payload === null || payload === undefined || payload === ''
+            ? errorMessage
+            : typeof payload === 'object' ? JSON.stringify(payload) : String(payload);
+          errorText = error.status ? `HTTP ${error.status}: ${body}` : body;
+        }
+
+        return {
+          isError: true,
+          content: [
+            {
+              type: "text",
+              text: errorText
+            }
+          ]
+        };
       }
     });
   }
@@ -2524,6 +2569,13 @@ class MCPServer {
         this.log('debug', `Retry response status: ${response.status}`);
       }
 
+      // validateStatus resolves everything under 500, so a 4xx arrives here as
+      // an ordinary response. Without this it would be returned to the model as
+      // a successful tool result whose body happens to be the API's error.
+      if (response.status >= 400) {
+        throw new ApiExecutionError(response.status, response.data);
+      }
+
       return response.data;
 
     } catch (error) {
@@ -2540,10 +2592,14 @@ class MCPServer {
           data: typeof responseData === 'object' ? JSON.stringify(responseData) : String(responseData)
         });
 
-        // Rethrow with more context for better error handling
-        const detailedError = new Error(`API request failed with status ${responseStatus}: ${errorMessage}`);
-        (detailedError as any).response = axiosError.response;
-        throw detailedError;
+        // Structured so the CallTool handler can report this as an MCP tool
+        // execution error carrying the API's own payload. Status is 0 for a
+        // transport failure (DNS, ECONNREFUSED, timeout) — there is no response.
+        throw new ApiExecutionError(
+          responseStatus ?? 0,
+          responseData,
+          `API request failed with status ${responseStatus}: ${errorMessage}`
+        );
       }
 
       throw error;

package/src/servers/agency-hosting.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.61.2', tools });

package/src/servers/agency-hosting.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agency-hosting.js';
 
-startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.61.2', tools });

package/src/servers/all.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.61.2', tools });

package/src/servers/all.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.61.2', tools });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.61.2', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.61.2', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.61.2', tools });

package/src/servers/dns.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.61.2', tools });

package/src/servers/domains.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.61.2', tools });

package/src/servers/domains.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.61.2', tools });

package/src/servers/ecommerce.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.61.2', tools });

package/src/servers/ecommerce.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.61.2', tools });

package/src/servers/horizons.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.61.2', tools });

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.61.2', tools });

package/src/servers/hosting.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.61.2', tools });

package/src/servers/hosting.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/hosting.js';
 
-startServer({ name: 'hostinger-hosting-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.61.2', tools });

package/src/servers/mail.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.61.2', tools });

package/src/servers/mail.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.61.2', tools });

package/src/servers/reach.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.61.2', tools });

package/src/servers/reach.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.61.2', tools });

package/src/servers/vps.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.61.2', tools });

package/src/servers/vps.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.61.2', tools });

package/src/servers/wordpress.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.61.2', tools });

package/src/servers/wordpress.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.61.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.61.2', tools });