hostinger-api-mcp 0.2.6 → 0.2.7

package/README.md

@@ -741,7 +741,7 @@ Skip this verification when using Hostinger's free subdomains (*.hostingersite.c
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/domains/verify-ownership`
 
-#### hosting_listNode.jsBuildsV1
+#### hosting_listNodeJSBuildsV1
 
 Retrieve a paginated list of Node.js build processes for a specific website.
 
@@ -752,7 +752,7 @@ Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs`
 - **Method**: `GET`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds`
 
-#### hosting_createNode.jsBuildFromArchiveV1
+#### hosting_createNodeJSBuildFromArchiveV1
 
 Upload a project archive, auto-detect build settings, and immediately start a Node.js build.
 
@@ -778,7 +778,7 @@ the `Get Node.js Build Logs` endpoint.
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive`
 
-#### hosting_getNode.jsBuildLogsV1
+#### hosting_getNodeJSBuildLogsV1
 
 Retrieve logs from a specific Node.js build process.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "MCP server for Hostinger API",
   "repository": {
     "type": "git",

package/src/core/runtime.js

@@ -29,7 +29,7 @@ const SECURITY_SCHEMES = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 0.18.0
+ * Generated from OpenAPI spec version 0.18.1
  */
 class MCPServer {
   constructor({ name, version, tools }) {

package/src/core/runtime.ts

@@ -47,7 +47,7 @@ const SECURITY_SCHEMES: Record<string, SecurityScheme> = {
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 0.18.0
+ * Generated from OpenAPI spec version 0.18.1
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -1764,7 +1764,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_listNode.jsBuildsV1",
+    "name": "hosting_listNodeJSBuildsV1",
     "description": "Retrieve a paginated list of Node.js build processes for a specific website.\n\nEach build represents a single run of the Node.js build pipeline. Use the `states`\nquery parameter to filter results by build state (pending, running, completed, failed).\nUse the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
@@ -1815,7 +1815,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_createNode.jsBuildFromArchiveV1",
+    "name": "hosting_createNodeJSBuildFromArchiveV1",
     "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
@@ -1899,7 +1899,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_getNode.jsBuildLogsV1",
+    "name": "hosting_getNodeJSBuildLogsV1",
     "description": "Retrieve logs from a specific Node.js build process.\n\nTo stream live output while a build is running, poll this endpoint repeatedly\nwhile the build state is `running`, passing the previously returned `lines` count\nas `from_line` to fetch only new output since the last call.\nLog content may contain ANSI escape sequences (color codes).",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs",

package/src/core/tools/all.ts

@@ -1774,7 +1774,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_listNode.jsBuildsV1",
+    "name": "hosting_listNodeJSBuildsV1",
     "description": "Retrieve a paginated list of Node.js build processes for a specific website.\n\nEach build represents a single run of the Node.js build pipeline. Use the `states`\nquery parameter to filter results by build state (pending, running, completed, failed).\nUse the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
@@ -1825,7 +1825,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_createNode.jsBuildFromArchiveV1",
+    "name": "hosting_createNodeJSBuildFromArchiveV1",
     "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
@@ -1909,7 +1909,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_getNode.jsBuildLogsV1",
+    "name": "hosting_getNodeJSBuildLogsV1",
     "description": "Retrieve logs from a specific Node.js build process.\n\nTo stream live output while a build is running, poll this endpoint repeatedly\nwhile the build state is `running`, passing the previously returned `lines` count\nas `from_line` to fetch only new output since the last call.\nLog content may contain ANSI escape sequences (color codes).",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs",

package/src/core/tools/hosting.js

@@ -734,7 +734,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_listNode.jsBuildsV1",
+    "name": "hosting_listNodeJSBuildsV1",
     "description": "Retrieve a paginated list of Node.js build processes for a specific website.\n\nEach build represents a single run of the Node.js build pipeline. Use the `states`\nquery parameter to filter results by build state (pending, running, completed, failed).\nUse the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
@@ -785,7 +785,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_createNode.jsBuildFromArchiveV1",
+    "name": "hosting_createNodeJSBuildFromArchiveV1",
     "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
@@ -869,7 +869,7 @@ export default [
     "group": "hosting"
   },
   {
-    "name": "hosting_getNode.jsBuildLogsV1",
+    "name": "hosting_getNodeJSBuildLogsV1",
     "description": "Retrieve logs from a specific Node.js build process.\n\nTo stream live output while a build is running, poll this endpoint repeatedly\nwhile the build state is `running`, passing the previously returned `lines` count\nas `from_line` to fetch only new output since the last call.\nLog content may contain ANSI escape sequences (color codes).",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs",

package/src/core/tools/hosting.ts

@@ -744,7 +744,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_listNode.jsBuildsV1",
+    "name": "hosting_listNodeJSBuildsV1",
     "description": "Retrieve a paginated list of Node.js build processes for a specific website.\n\nEach build represents a single run of the Node.js build pipeline. Use the `states`\nquery parameter to filter results by build state (pending, running, completed, failed).\nUse the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds",
@@ -795,7 +795,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_createNode.jsBuildFromArchiveV1",
+    "name": "hosting_createNodeJSBuildFromArchiveV1",
     "description": "Upload a project archive, auto-detect build settings, and immediately start a Node.js build.\n\nThis is the recommended single-step approach for deploying a Node.js application.\nThe archive is uploaded to the website's file storage, build settings are auto-detected\nfrom the package.json inside the archive, and the build process starts automatically.\nOptional override fields take precedence over auto-detected values.\nMaximum archive size is 50MB.\n\nBefore archiving, exclude `node_modules/` and any build output directories\n(e.g. `dist/`, `.next/`, `build/`) — they are not needed because the build\nprocess runs the install step automatically, and including them unnecessarily\nincreases the archive size. This also helps keep the archive well under the 50MB limit.\n\nExample (zip):\n```\nzip -r archive.zip . --exclude \"node_modules/*\" --exclude \"dist/*\"\n```\n\nThe returned build `uuid` can be used to poll progress and retrieve logs via\nthe `Get Node.js Build Logs` endpoint.",
     "method": "POST",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/from-archive",
@@ -879,7 +879,7 @@ const tools: OpenApiTool[] = [
     "group": "hosting"
   },
   {
-    "name": "hosting_getNode.jsBuildLogsV1",
+    "name": "hosting_getNodeJSBuildLogsV1",
     "description": "Retrieve logs from a specific Node.js build process.\n\nTo stream live output while a build is running, poll this endpoint repeatedly\nwhile the build state is `running`, passing the previously returned `lines` count\nas `from_line` to fetch only new output since the last call.\nLog content may contain ANSI escape sequences (color codes).",
     "method": "GET",
     "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/builds/{uuid}/logs",

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: '0.2.6', tools });
+startServer({ name: 'hostinger-api-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-api-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '0.2.7', 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: '0.2.6', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '0.2.7', tools });

package/types.d.ts

@@ -1142,7 +1142,7 @@ Each build represents a single run of the Node.js build pipeline. Use the `state
 query parameter to filter results by build state (pending, running, completed, failed).
 Use the `uuid` from a build to poll its output via the `Get Node.js Build Logs` endpoint.
    */
-  "hosting_listNode.jsBuildsV1": {
+  "hosting_listNodeJSBuildsV1": {
     params: {
       /**
        * username parameter
@@ -1190,7 +1190,7 @@ zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"
 The returned build `uuid` can be used to poll progress and retrieve logs via
 the `Get Node.js Build Logs` endpoint.
    */
-  "hosting_createNode.jsBuildFromArchiveV1": {
+  "hosting_createNodeJSBuildFromArchiveV1": {
     params: {
       /**
        * username parameter
@@ -1244,7 +1244,7 @@ while the build state is `running`, passing the previously returned `lines` coun
 as `from_line` to fetch only new output since the last call.
 Log content may contain ANSI escape sequences (color codes).
    */
-  "hosting_getNode.jsBuildLogsV1": {
+  "hosting_getNodeJSBuildLogsV1": {
     params: {
       /**
        * username parameter