hostinger-api-mcp 1.58.0 → 1.59.0

package/CHANGELOG.md

@@ -4,6 +4,25 @@ 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.59.0 — 2026-09-11
+
+### Tools
+
+- Added `domains_completeDomainSetupV1` — Complete domain setup
+
+### Also in this release
+
+- Documentation: `README.md`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+- Build and packaging: `types.d.ts`
+
+## v1.58.1 — 2026-09-11
+
+### Also in this release
+
+- Dependencies: `package-lock.json`
+- Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
+
 ## v1.58.0 — 2026-09-09
 
 ### Tools

package/README.md

@@ -69,11 +69,11 @@ pnpm update -g @hostinger/mcp
 
 This package installs the following MCP server commands:
 
-- `hostinger-api-mcp` — unified server with every tool (386 total)
+- `hostinger-api-mcp` — unified server with every tool (387 total)
 - `hostinger-agency-hosting-mcp` — 38 tools for agency-hosting
 - `hostinger-billing-mcp` — 9 tools for billing
 - `hostinger-dns-mcp` — 8 tools for dns
-- `hostinger-domains-mcp` — 40 tools for domains
+- `hostinger-domains-mcp` — 41 tools for domains
 - `hostinger-ecommerce-mcp` — 29 tools for ecommerce
 - `hostinger-horizons-mcp` — 6 tools for horizons
 - `hostinger-hosting-mcp` — 64 tools for hosting
@@ -1158,6 +1158,39 @@ Use this endpoint to build renewal automation and expiry monitoring for a single
 - **Method**: `GET`
 - **Path**: `/api/domains/v1/portfolio/{domain}/renewal`
 
+#### domains_completeDomainSetupV1
+
+Register a domain you have already paid for but which has not been set up yet.
+
+Use this endpoint when an order completed without registering the domain, for example when
+`Purchase new domain` returned `202 Accepted` and the domain was added to your account without
+being registered, or when an earlier setup attempt failed. No new order is placed and no payment
+is taken: the subscription you already own is used, for the period you already paid for.
+
+A domain is left awaiting setup when the details needed to register it were missing or invalid
+as the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.
+Complete the missing information, then call this endpoint. If the order itself has not completed
+yet, the domain is not on your account, wait until it appears in `Get domain list`.
+
+If `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four
+roles. The profile must exist and be complete for the TLD, an incomplete profile is the most
+common reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.
+
+Some TLDs require `additional_details`. These are validated before setup, so a missing or
+invalid value is rejected without any registration being attempted.
+
+The domain is set up with the default nameservers and without privacy protection. Use
+`Update domain nameservers` and `Enable privacy protection` afterwards to change either.
+
+A successful response means the setup request was accepted, not that the domain is already
+registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
+only once it is registered.
+
+Use this endpoint to finish registering a domain that is awaiting setup on your account.
+
+- **Method**: `POST`
+- **Path**: `/api/domains/v1/portfolio/{domain}/setup`
+
 #### domains_updateDomainNameserversV1
 
 Set nameservers for a specified domain.

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hostinger-api-mcp",
-  "version": "1.58.0",
+  "version": "1.59.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.58.0",
+  "version": "1.59.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.58.0",
+  "version": "1.59.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@hostinger/mcp",
-      "version": "1.58.0",
+      "version": "1.59.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.50.0
+ * Generated from OpenAPI spec version 1.51.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.50.0
+ * Generated from OpenAPI spec version 1.51.0
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/all.js

@@ -3469,6 +3469,63 @@ export default [
     ],
     "group": "domains"
   },
+  {
+    "name": "domains_completeDomainSetupV1",
+    "title": "Complete domain setup",
+    "annotations": {
+      "title": "Complete domain setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and without privacy protection. Use\n`Update domain nameservers` and `Enable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
+    "method": "POST",
+    "path": "/api/domains/v1/portfolio/{domain}/setup",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "domain_contacts": {
+          "type": "object",
+          "description": "Domain contact information",
+          "properties": {
+            "owner_id": {
+              "type": "integer",
+              "description": "Owner contact WHOIS record ID"
+            },
+            "admin_id": {
+              "type": "integer",
+              "description": "Administrative contact WHOIS record ID"
+            },
+            "billing_id": {
+              "type": "integer",
+              "description": "Billing contact WHOIS record ID"
+            },
+            "tech_id": {
+              "type": "integer",
+              "description": "Technical contact WHOIS record ID"
+            }
+          }
+        },
+        "additional_details": {
+          "type": "object",
+          "description": "Additional registration data, possible values depends on TLD",
+          "properties": {}
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "domains"
+  },
   {
     "name": "domains_updateDomainNameserversV1",
     "title": "Update domain nameservers",

package/src/core/tools/all.ts

@@ -3483,6 +3483,63 @@ const tools: OpenApiTool[] = [
     ],
     "group": "domains"
   },
+  {
+    "name": "domains_completeDomainSetupV1",
+    "title": "Complete domain setup",
+    "annotations": {
+      "title": "Complete domain setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and without privacy protection. Use\n`Update domain nameservers` and `Enable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
+    "method": "POST",
+    "path": "/api/domains/v1/portfolio/{domain}/setup",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "domain_contacts": {
+          "type": "object",
+          "description": "Domain contact information",
+          "properties": {
+            "owner_id": {
+              "type": "integer",
+              "description": "Owner contact WHOIS record ID"
+            },
+            "admin_id": {
+              "type": "integer",
+              "description": "Administrative contact WHOIS record ID"
+            },
+            "billing_id": {
+              "type": "integer",
+              "description": "Billing contact WHOIS record ID"
+            },
+            "tech_id": {
+              "type": "integer",
+              "description": "Technical contact WHOIS record ID"
+            }
+          }
+        },
+        "additional_details": {
+          "type": "object",
+          "description": "Additional registration data, possible values depends on TLD",
+          "properties": {}
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "domains"
+  },
   {
     "name": "domains_updateDomainNameserversV1",
     "title": "Update domain nameservers",

package/src/core/tools/domains.js

@@ -982,6 +982,63 @@ export default [
     ],
     "group": "domains"
   },
+  {
+    "name": "domains_completeDomainSetupV1",
+    "title": "Complete domain setup",
+    "annotations": {
+      "title": "Complete domain setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and without privacy protection. Use\n`Update domain nameservers` and `Enable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
+    "method": "POST",
+    "path": "/api/domains/v1/portfolio/{domain}/setup",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "domain_contacts": {
+          "type": "object",
+          "description": "Domain contact information",
+          "properties": {
+            "owner_id": {
+              "type": "integer",
+              "description": "Owner contact WHOIS record ID"
+            },
+            "admin_id": {
+              "type": "integer",
+              "description": "Administrative contact WHOIS record ID"
+            },
+            "billing_id": {
+              "type": "integer",
+              "description": "Billing contact WHOIS record ID"
+            },
+            "tech_id": {
+              "type": "integer",
+              "description": "Technical contact WHOIS record ID"
+            }
+          }
+        },
+        "additional_details": {
+          "type": "object",
+          "description": "Additional registration data, possible values depends on TLD",
+          "properties": {}
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "domains"
+  },
   {
     "name": "domains_updateDomainNameserversV1",
     "title": "Update domain nameservers",

package/src/core/tools/domains.ts

@@ -996,6 +996,63 @@ const tools: OpenApiTool[] = [
     ],
     "group": "domains"
   },
+  {
+    "name": "domains_completeDomainSetupV1",
+    "title": "Complete domain setup",
+    "annotations": {
+      "title": "Complete domain setup",
+      "readOnlyHint": false,
+      "destructiveHint": false
+    },
+    "description": "Register a domain you have already paid for but which has not been set up yet.\n\nUse this endpoint when an order completed without registering the domain, for example when\n`Purchase new domain` returned `202 Accepted` and the domain was added to your account without\nbeing registered, or when an earlier setup attempt failed. No new order is placed and no payment\nis taken: the subscription you already own is used, for the period you already paid for.\n\nA domain is left awaiting setup when the details needed to register it were missing or invalid\nas the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.\nComplete the missing information, then call this endpoint. If the order itself has not completed\nyet, the domain is not on your account, wait until it appears in `Get domain list`.\n\nIf `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four\nroles. The profile must exist and be complete for the TLD, an incomplete profile is the most\ncommon reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.\n\nSome TLDs require `additional_details`. These are validated before setup, so a missing or\ninvalid value is rejected without any registration being attempted.\n\nThe domain is set up with the default nameservers and without privacy protection. Use\n`Update domain nameservers` and `Enable privacy protection` afterwards to change either.\n\nA successful response means the setup request was accepted, not that the domain is already\nregistered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`\nonly once it is registered.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
+    "method": "POST",
+    "path": "/api/domains/v1/portfolio/{domain}/setup",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "domain": {
+          "type": "string",
+          "description": "Domain name"
+        },
+        "domain_contacts": {
+          "type": "object",
+          "description": "Domain contact information",
+          "properties": {
+            "owner_id": {
+              "type": "integer",
+              "description": "Owner contact WHOIS record ID"
+            },
+            "admin_id": {
+              "type": "integer",
+              "description": "Administrative contact WHOIS record ID"
+            },
+            "billing_id": {
+              "type": "integer",
+              "description": "Billing contact WHOIS record ID"
+            },
+            "tech_id": {
+              "type": "integer",
+              "description": "Technical contact WHOIS record ID"
+            }
+          }
+        },
+        "additional_details": {
+          "type": "object",
+          "description": "Additional registration data, possible values depends on TLD",
+          "properties": {}
+        }
+      },
+      "required": [
+        "domain"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "domains"
+  },
   {
     "name": "domains_updateDomainNameserversV1",
     "title": "Update domain nameservers",

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

package/types.d.ts

@@ -1891,6 +1891,53 @@ Use this endpoint to build renewal automation and expiry monitoring for a single
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Register a domain you have already paid for but which has not been set up yet.
+
+Use this endpoint when an order completed without registering the domain, for example when
+`Purchase new domain` returned `202 Accepted` and the domain was added to your account without
+being registered, or when an earlier setup attempt failed. No new order is placed and no payment
+is taken: the subscription you already own is used, for the period you already paid for.
+
+A domain is left awaiting setup when the details needed to register it were missing or invalid
+as the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.
+Complete the missing information, then call this endpoint. If the order itself has not completed
+yet, the domain is not on your account, wait until it appears in `Get domain list`.
+
+If `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four
+roles. The profile must exist and be complete for the TLD, an incomplete profile is the most
+common reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.
+
+Some TLDs require `additional_details`. These are validated before setup, so a missing or
+invalid value is rejected without any registration being attempted.
+
+The domain is set up with the default nameservers and without privacy protection. Use
+`Update domain nameservers` and `Enable privacy protection` afterwards to change either.
+
+A successful response means the setup request was accepted, not that the domain is already
+registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
+only once it is registered.
+
+Use this endpoint to finish registering a domain that is awaiting setup on your account.
+   */
+  "domains_completeDomainSetupV1": {
+    params: {
+      /**
+       * Domain name
+       */
+      domain: string;
+      /**
+       * Domain contact information
+       */
+      domain_contacts?: object;
+      /**
+       * Additional registration data, possible values depends on TLD
+       */
+      additional_details?: object;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Set nameservers for a specified domain.