hostinger-api-mcp 1.7.1 → 1.8.0

package/README.md

@@ -49,14 +49,14 @@ pnpm update -g hostinger-api-mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (217 total)
+- `hostinger-api-mcp` — unified server with every tool (219 total)
 - `hostinger-agency-hosting-mcp` — 14 tools for agency-hosting
 - `hostinger-billing-mcp` — 7 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
 - `hostinger-domains-mcp` — 19 tools for domains
 - `hostinger-ecommerce-mcp` — 12 tools for ecommerce
 - `hostinger-horizons-mcp` — 2 tools for horizons
-- `hostinger-hosting-mcp` — 46 tools for hosting
+- `hostinger-hosting-mcp` — 48 tools for hosting
 - `hostinger-reach-mcp` — 12 tools for reach
 - `hostinger-vps-mcp` — 62 tools for vps
 - `hostinger-wordpress-mcp` — 35 tools for wordpress
@@ -1211,6 +1211,49 @@ has no effect. Returns success even when the website has no server process to re
 - **Method**: `POST`
 - **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/server/restart`
 
+#### hosting_listNode_jsVulnerabilitiesV1
+
+Lists known npm package vulnerabilities detected on a Node.js website, enriched with
+advisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from
+the most severe to the least severe, then by publish date (newest first). Use the
+`severities` query parameter to filter.
+
+Vulnerabilities with `is_patchable` set to `true` can be auto-fixed via the
+`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with
+updated package versions. Auto-fix is only available for websites deployed from a
+connected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to
+`true` are already included in an open patch pull request; while any patch pull
+request is open, new patch requests for this website are rejected until it is merged
+or closed.
+
+Data comes from periodic dependency scans, so it may lag behind the latest deployment.
+An empty list means the most recent scan found no vulnerabilities; it does not
+guarantee the current deployment is vulnerability-free. Available on Business and
+Cloud Hosting plans.
+
+- **Method**: `GET`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities`
+
+#### hosting_patchNode_jsVulnerabilitiesV1
+
+Patches the selected Node.js vulnerabilities by updating the affected package versions
+in `package.json` and opening a GitHub pull request in the connected repository. The
+customer reviews and merges the pull request; merging triggers the automatic deployment.
+
+Auto-fix is only available for websites deployed from a connected GitHub repository.
+Websites deployed from an archive have no auto-fix path and return a 404. The Hostinger
+GitHub App needs write access to the repository; without it the request fails with a
+403 explaining the missing permission.
+
+Only vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable
+IDs in the selection are skipped; the pull request covers the patchable subset, listed
+in `patched_vulnerability_ids`. Selections without any patchable vulnerability are
+rejected with a 422. Only one patch pull request can be open at a time per website;
+close or merge it before patching again. Available on Business and Cloud Hosting plans.
+
+- **Method**: `POST`
+- **Path**: `/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch`
+
 #### hosting_listOrdersV1
 
 Retrieve a paginated list of orders accessible to the authenticated client.

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.7.1",
+  "version": "1.8.0",
   "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.7.1",
+  "version": "1.8.0",
   "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.7.1",
+  "version": "1.8.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "hostinger-api-mcp",
-      "version": "1.7.1",
+      "version": "1.8.0",
       "transport": {
         "type": "stdio"
       },

package/src/core/runtime.js

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

package/src/core/runtime.ts

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

package/src/core/tools/all.js

@@ -3288,6 +3288,88 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsVulnerabilitiesV1",
+    "description": "Lists known npm package vulnerabilities detected on a Node.js website, enriched with\nadvisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from\nthe most severe to the least severe, then by publish date (newest first). Use the\n`severities` query parameter to filter.\n\nVulnerabilities with `is_patchable` set to `true` can be auto-fixed via the\n`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with\nupdated package versions. Auto-fix is only available for websites deployed from a\nconnected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to\n`true` are already included in an open patch pull request; while any patch pull\nrequest is open, new patch requests for this website are rejected until it is merged\nor closed.\n\nData comes from periodic dependency scans, so it may lag behind the latest deployment.\nAn empty list means the most recent scan found no vulnerabilities; it does not\nguarantee the current deployment is vulnerability-free. Available on Business and\nCloud Hosting plans.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "severities": {
+          "type": "array",
+          "description": "Severities to filter by",
+          "items": {
+            "type": "string",
+            "description": "severities parameter",
+            "enum": [
+              "low",
+              "moderate",
+              "high",
+              "critical",
+              "unknown"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_patchNode_jsVulnerabilitiesV1",
+    "description": "Patches the selected Node.js vulnerabilities by updating the affected package versions\nin `package.json` and opening a GitHub pull request in the connected repository. The\ncustomer reviews and merges the pull request; merging triggers the automatic deployment.\n\nAuto-fix is only available for websites deployed from a connected GitHub repository.\nWebsites deployed from an archive have no auto-fix path and return a 404. The Hostinger\nGitHub App needs write access to the repository; without it the request fails with a\n403 explaining the missing permission.\n\nOnly vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable\nIDs in the selection are skipped; the pull request covers the patchable subset, listed\nin `patched_vulnerability_ids`. Selections without any patchable vulnerability are\nrejected with a 422. Only one patch pull request can be open at a time per website;\nclose or merge it before patching again. Available on Business and Cloud Hosting plans.",
+    "method": "POST",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "vulnerability_ids": {
+          "type": "array",
+          "description": "List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.",
+          "items": {
+            "type": "string",
+            "description": "vulnerability_ids parameter"
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "vulnerability_ids"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listOrdersV1",
     "description": "Retrieve a paginated list of orders accessible to the authenticated client.\n\nThis endpoint returns orders of your hosting accounts as well as orders\nof other client hosting accounts that have shared access with you.\n\nUse the available query parameters to filter results by order statuses\nor specific order IDs for more targeted results.",

package/src/core/tools/all.ts

@@ -3302,6 +3302,88 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsVulnerabilitiesV1",
+    "description": "Lists known npm package vulnerabilities detected on a Node.js website, enriched with\nadvisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from\nthe most severe to the least severe, then by publish date (newest first). Use the\n`severities` query parameter to filter.\n\nVulnerabilities with `is_patchable` set to `true` can be auto-fixed via the\n`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with\nupdated package versions. Auto-fix is only available for websites deployed from a\nconnected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to\n`true` are already included in an open patch pull request; while any patch pull\nrequest is open, new patch requests for this website are rejected until it is merged\nor closed.\n\nData comes from periodic dependency scans, so it may lag behind the latest deployment.\nAn empty list means the most recent scan found no vulnerabilities; it does not\nguarantee the current deployment is vulnerability-free. Available on Business and\nCloud Hosting plans.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "severities": {
+          "type": "array",
+          "description": "Severities to filter by",
+          "items": {
+            "type": "string",
+            "description": "severities parameter",
+            "enum": [
+              "low",
+              "moderate",
+              "high",
+              "critical",
+              "unknown"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_patchNode_jsVulnerabilitiesV1",
+    "description": "Patches the selected Node.js vulnerabilities by updating the affected package versions\nin `package.json` and opening a GitHub pull request in the connected repository. The\ncustomer reviews and merges the pull request; merging triggers the automatic deployment.\n\nAuto-fix is only available for websites deployed from a connected GitHub repository.\nWebsites deployed from an archive have no auto-fix path and return a 404. The Hostinger\nGitHub App needs write access to the repository; without it the request fails with a\n403 explaining the missing permission.\n\nOnly vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable\nIDs in the selection are skipped; the pull request covers the patchable subset, listed\nin `patched_vulnerability_ids`. Selections without any patchable vulnerability are\nrejected with a 422. Only one patch pull request can be open at a time per website;\nclose or merge it before patching again. Available on Business and Cloud Hosting plans.",
+    "method": "POST",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "vulnerability_ids": {
+          "type": "array",
+          "description": "List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.",
+          "items": {
+            "type": "string",
+            "description": "vulnerability_ids parameter"
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "vulnerability_ids"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listOrdersV1",
     "description": "Retrieve a paginated list of orders accessible to the authenticated client.\n\nThis endpoint returns orders of your hosting accounts as well as orders\nof other client hosting accounts that have shared access with you.\n\nUse the available query parameters to filter results by order statuses\nor specific order IDs for more targeted results.",

package/src/core/tools/hosting.js

@@ -1248,6 +1248,88 @@ export default [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsVulnerabilitiesV1",
+    "description": "Lists known npm package vulnerabilities detected on a Node.js website, enriched with\nadvisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from\nthe most severe to the least severe, then by publish date (newest first). Use the\n`severities` query parameter to filter.\n\nVulnerabilities with `is_patchable` set to `true` can be auto-fixed via the\n`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with\nupdated package versions. Auto-fix is only available for websites deployed from a\nconnected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to\n`true` are already included in an open patch pull request; while any patch pull\nrequest is open, new patch requests for this website are rejected until it is merged\nor closed.\n\nData comes from periodic dependency scans, so it may lag behind the latest deployment.\nAn empty list means the most recent scan found no vulnerabilities; it does not\nguarantee the current deployment is vulnerability-free. Available on Business and\nCloud Hosting plans.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "severities": {
+          "type": "array",
+          "description": "Severities to filter by",
+          "items": {
+            "type": "string",
+            "description": "severities parameter",
+            "enum": [
+              "low",
+              "moderate",
+              "high",
+              "critical",
+              "unknown"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_patchNode_jsVulnerabilitiesV1",
+    "description": "Patches the selected Node.js vulnerabilities by updating the affected package versions\nin `package.json` and opening a GitHub pull request in the connected repository. The\ncustomer reviews and merges the pull request; merging triggers the automatic deployment.\n\nAuto-fix is only available for websites deployed from a connected GitHub repository.\nWebsites deployed from an archive have no auto-fix path and return a 404. The Hostinger\nGitHub App needs write access to the repository; without it the request fails with a\n403 explaining the missing permission.\n\nOnly vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable\nIDs in the selection are skipped; the pull request covers the patchable subset, listed\nin `patched_vulnerability_ids`. Selections without any patchable vulnerability are\nrejected with a 422. Only one patch pull request can be open at a time per website;\nclose or merge it before patching again. Available on Business and Cloud Hosting plans.",
+    "method": "POST",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "vulnerability_ids": {
+          "type": "array",
+          "description": "List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.",
+          "items": {
+            "type": "string",
+            "description": "vulnerability_ids parameter"
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "vulnerability_ids"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listOrdersV1",
     "description": "Retrieve a paginated list of orders accessible to the authenticated client.\n\nThis endpoint returns orders of your hosting accounts as well as orders\nof other client hosting accounts that have shared access with you.\n\nUse the available query parameters to filter results by order statuses\nor specific order IDs for more targeted results.",

package/src/core/tools/hosting.ts

@@ -1262,6 +1262,88 @@ const tools: OpenApiTool[] = [
     ],
     "group": "hosting"
   },
+  {
+    "name": "hosting_listNode_jsVulnerabilitiesV1",
+    "description": "Lists known npm package vulnerabilities detected on a Node.js website, enriched with\nadvisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from\nthe most severe to the least severe, then by publish date (newest first). Use the\n`severities` query parameter to filter.\n\nVulnerabilities with `is_patchable` set to `true` can be auto-fixed via the\n`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with\nupdated package versions. Auto-fix is only available for websites deployed from a\nconnected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to\n`true` are already included in an open patch pull request; while any patch pull\nrequest is open, new patch requests for this website are rejected until it is merged\nor closed.\n\nData comes from periodic dependency scans, so it may lag behind the latest deployment.\nAn empty list means the most recent scan found no vulnerabilities; it does not\nguarantee the current deployment is vulnerability-free. Available on Business and\nCloud Hosting plans.",
+    "method": "GET",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "severities": {
+          "type": "array",
+          "description": "Severities to filter by",
+          "items": {
+            "type": "string",
+            "description": "severities parameter",
+            "enum": [
+              "low",
+              "moderate",
+              "high",
+              "critical",
+              "unknown"
+            ]
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
+  {
+    "name": "hosting_patchNode_jsVulnerabilitiesV1",
+    "description": "Patches the selected Node.js vulnerabilities by updating the affected package versions\nin `package.json` and opening a GitHub pull request in the connected repository. The\ncustomer reviews and merges the pull request; merging triggers the automatic deployment.\n\nAuto-fix is only available for websites deployed from a connected GitHub repository.\nWebsites deployed from an archive have no auto-fix path and return a 404. The Hostinger\nGitHub App needs write access to the repository; without it the request fails with a\n403 explaining the missing permission.\n\nOnly vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable\nIDs in the selection are skipped; the pull request covers the patchable subset, listed\nin `patched_vulnerability_ids`. Selections without any patchable vulnerability are\nrejected with a 422. Only one patch pull request can be open at a time per website;\nclose or merge it before patching again. Available on Business and Cloud Hosting plans.",
+    "method": "POST",
+    "path": "/api/hosting/v1/accounts/{username}/websites/{domain}/nodejs/vulnerabilities/patch",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "username": {
+          "type": "string",
+          "description": "username parameter"
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "vulnerability_ids": {
+          "type": "array",
+          "description": "List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.",
+          "items": {
+            "type": "string",
+            "description": "vulnerability_ids parameter"
+          }
+        }
+      },
+      "required": [
+        "username",
+        "domain",
+        "vulnerability_ids"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "hosting"
+  },
   {
     "name": "hosting_listOrdersV1",
     "description": "Retrieve a paginated list of orders accessible to the authenticated client.\n\nThis endpoint returns orders of your hosting accounts as well as orders\nof other client hosting accounts that have shared access with you.\n\nUse the available query parameters to filter results by order statuses\nor specific order IDs for more targeted results.",

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.7.1', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-agency-hosting-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.8.0', 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.7.1', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.8.0', tools });

package/types.d.ts

@@ -2153,6 +2153,77 @@ has no effect. Returns success even when the website has no server process to re
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Lists known npm package vulnerabilities detected on a Node.js website, enriched with
+advisory metadata (severity, CVSS score, CVE, advisory URL). Results are sorted from
+the most severe to the least severe, then by publish date (newest first). Use the
+`severities` query parameter to filter.
+
+Vulnerabilities with `is_patchable` set to `true` can be auto-fixed via the
+`Patch Node.js Vulnerabilities` endpoint, which opens a GitHub pull request with
+updated package versions. Auto-fix is only available for websites deployed from a
+connected GitHub repository. Vulnerabilities with `is_patching_in_progress` set to
+`true` are already included in an open patch pull request; while any patch pull
+request is open, new patch requests for this website are rejected until it is merged
+or closed.
+
+Data comes from periodic dependency scans, so it may lag behind the latest deployment.
+An empty list means the most recent scan found no vulnerabilities; it does not
+guarantee the current deployment is vulnerability-free. Available on Business and
+Cloud Hosting plans.
+   */
+  "hosting_listNode_jsVulnerabilitiesV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Severities to filter by
+       */
+      severities?: array;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Patches the selected Node.js vulnerabilities by updating the affected package versions
+in `package.json` and opening a GitHub pull request in the connected repository. The
+customer reviews and merges the pull request; merging triggers the automatic deployment.
+
+Auto-fix is only available for websites deployed from a connected GitHub repository.
+Websites deployed from an archive have no auto-fix path and return a 404. The Hostinger
+GitHub App needs write access to the repository; without it the request fails with a
+403 explaining the missing permission.
+
+Only vulnerabilities with `is_patchable` set to `true` can be patched. Non-patchable
+IDs in the selection are skipped; the pull request covers the patchable subset, listed
+in `patched_vulnerability_ids`. Selections without any patchable vulnerability are
+rejected with a 422. Only one patch pull request can be open at a time per website;
+close or merge it before patching again. Available on Business and Cloud Hosting plans.
+   */
+  "hosting_patchNode_jsVulnerabilitiesV1": {
+    params: {
+      /**
+       * username parameter
+       */
+      username: string;
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * List of vulnerability IDs to patch, as returned by the list vulnerabilities endpoint.
+       */
+      vulnerability_ids: array;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a paginated list of orders accessible to the authenticated client.