@hostinger/mcp 2.17.0 → 2.18.0

package/CHANGELOG.md

@@ -4,6 +4,32 @@ Generated at release time from the diff between the previous and current
 build. Tool changes are listed individually; everything else is summarised
 by area.
 
+## v2.18.0 — 2026-10-15
+
+### Operations
+
+- Changed the description and input schema of `hosting_websites_start-setup`
+- Changed the description and input schema of `hosting_websites_create`
+
+### 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`
+
+## v2.17.1 — 2026-10-15
+
+### Operations
+
+- Renamed `agent-readiness_scans_run-website` → `agent-readiness_scans_run`
+- Renamed `agent-readiness_scans_website` → `agent-readiness_scans_get`
+
+### 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`
+
 ## v2.17.0 — 2026-10-15
 
 ### Operations

package/README.md

@@ -691,12 +691,12 @@ Use it to show the human-readable name of each `check_id` in a scan's results.
 - **Method**: `GET`
 - **Path**: `/api/agent-readiness/v1/checks`
 
-#### agent-readiness_scans_run-website
+#### agent-readiness_scans_run
 
 Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
 Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`
-with no results yet. To get the results, poll the `Get website scan` operation with the same domain every
-few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
+with no results yet. To get the results, poll the `Get agent readiness scan` operation with the same
+domain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
 plus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\n
 Starting a scan for a domain that already has a pending scan from the last 5 minutes
 returns that scan instead of starting a new one.
@@ -704,15 +704,15 @@ returns that scan instead of starting a new one.
 - **Method**: `POST`
 - **Path**: `/api/agent-readiness/v1/scans`
 
-#### agent-readiness_scans_website
+#### agent-readiness_scans_get
 
 Get the latest agent readiness scan of a website.\n
-Scans started with the `Run website scan` operation are asynchronous. While the status is `pending`,
-the result fields are null; wait a few seconds and call this operation again until the status is
+Scans started with the `Run agent readiness scan` operation are asynchronous. While the status is
+`pending`, the result fields are null; wait a few seconds and call this operation again until the status is
 `completed` or `failed`. A `failed` scan is not retried; run the scan again.\n
 A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
 check with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\n
-Returns 404 when the domain has never been scanned; use the `Run website scan` operation first.
+Returns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.
 
 - **Method**: `GET`
 - **Path**: `/api/agent-readiness/v1/scans/{domain}`
@@ -2600,8 +2600,8 @@ of the website root with generated credentials.
 
 Omit `domain` to set the website up on a generated temporary free subdomain.
 
-The order must already have a hosting account: to create the first website on a new
-hosting plan use the create website endpoint, which takes the `datacenter_code`.
+When the order has no hosting account yet, the setup creates one first, in the datacenter
+given by `datacenter_code` or the order's default datacenter when it is omitted.
 Returns 404 when the order does not exist or is not accessible to the authenticated
 client, and 409 with a `Retry-After` header while a setup for the same domain is still
 running.
@@ -2791,6 +2791,10 @@ endpoint instead.
 
 #### hosting_websites_create
 
+Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)
+instead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and
+returns the created setup.
+
 Create a new website for the authenticated client.
 
 You must choose which hosting order to create this website on. Pass that
@@ -2800,10 +2804,8 @@ available IDs; the website is provisioned on that order's hosting plan.
 Only Web and Cloud hosting orders are accepted. To create a website on an Agency
 Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.
 
-The datacenter_code parameter is required when creating the first website
-on a new hosting plan - this will set up and configure new hosting account
-in the selected datacenter.
-
+When the order has no hosting account yet, a new hosting account is set up first, in the
+datacenter given by `datacenter_code` or the order's default datacenter when it is omitted.
 Subsequent websites will be hosted on the same datacenter automatically.
 
 Website creation is asynchronous and takes up to a few minutes. Poll the list website

package/gemini-extension.json

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

package/src/core/runtime.js

@@ -64,7 +64,7 @@ const GetSkillRequestSchema = z.object({
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.67.0
+ * Generated from OpenAPI spec version 1.68.0
  */
 class MCPServer {
   constructor({ name, version, tools, instructions, skills = [] }) {

package/src/core/runtime.ts

@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
 
 /**
  * MCP Server for Hostinger API
- * Generated from OpenAPI spec version 1.67.0
+ * Generated from OpenAPI spec version 1.68.0
  */
 class MCPServer {
   private readonly name: string;

package/src/core/tools/agent-readiness.js

@@ -24,14 +24,14 @@ export default [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_run-website",
-    "title": "Run website scan",
+    "name": "agent-readiness_scans_run",
+    "title": "Run agent readiness scan",
     "annotations": {
-      "title": "Run website scan",
+      "title": "Run agent readiness scan",
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get website scan` operation with the same domain every\nfew seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
+    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get agent readiness scan` operation with the same\ndomain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
     "method": "POST",
     "path": "/api/agent-readiness/v1/scans",
     "inputSchema": {
@@ -54,14 +54,14 @@ export default [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_website",
-    "title": "Get website scan",
+    "name": "agent-readiness_scans_get",
+    "title": "Get agent readiness scan",
     "annotations": {
-      "title": "Get website scan",
+      "title": "Get agent readiness scan",
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run website scan` operation are asynchronous. While the status is `pending`,\nthe result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run website scan` operation first.",
+    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run agent readiness scan` operation are asynchronous. While the status is\n`pending`, the result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.",
     "method": "GET",
     "path": "/api/agent-readiness/v1/scans/{domain}",
     "inputSchema": {

package/src/core/tools/agent-readiness.ts

@@ -38,14 +38,14 @@ const tools: OpenApiTool[] = [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_run-website",
-    "title": "Run website scan",
+    "name": "agent-readiness_scans_run",
+    "title": "Run agent readiness scan",
     "annotations": {
-      "title": "Run website scan",
+      "title": "Run agent readiness scan",
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get website scan` operation with the same domain every\nfew seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
+    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get agent readiness scan` operation with the same\ndomain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
     "method": "POST",
     "path": "/api/agent-readiness/v1/scans",
     "inputSchema": {
@@ -68,14 +68,14 @@ const tools: OpenApiTool[] = [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_website",
-    "title": "Get website scan",
+    "name": "agent-readiness_scans_get",
+    "title": "Get agent readiness scan",
     "annotations": {
-      "title": "Get website scan",
+      "title": "Get agent readiness scan",
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run website scan` operation are asynchronous. While the status is `pending`,\nthe result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run website scan` operation first.",
+    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run agent readiness scan` operation are asynchronous. While the status is\n`pending`, the result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.",
     "method": "GET",
     "path": "/api/agent-readiness/v1/scans/{domain}",
     "inputSchema": {

package/src/core/tools/all.js

@@ -1955,14 +1955,14 @@ export default [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_run-website",
-    "title": "Run website scan",
+    "name": "agent-readiness_scans_run",
+    "title": "Run agent readiness scan",
     "annotations": {
-      "title": "Run website scan",
+      "title": "Run agent readiness scan",
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get website scan` operation with the same domain every\nfew seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
+    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get agent readiness scan` operation with the same\ndomain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
     "method": "POST",
     "path": "/api/agent-readiness/v1/scans",
     "inputSchema": {
@@ -1985,14 +1985,14 @@ export default [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_website",
-    "title": "Get website scan",
+    "name": "agent-readiness_scans_get",
+    "title": "Get agent readiness scan",
     "annotations": {
-      "title": "Get website scan",
+      "title": "Get agent readiness scan",
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run website scan` operation are asynchronous. While the status is `pending`,\nthe result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run website scan` operation first.",
+    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run agent readiness scan` operation are asynchronous. While the status is\n`pending`, the result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.",
     "method": "GET",
     "path": "/api/agent-readiness/v1/scans/{domain}",
     "inputSchema": {
@@ -8484,7 +8484,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
     "method": "POST",
     "path": "/api/hosting/v1/orders/{order_id}/onboardings",
     "inputSchema": {
@@ -8506,7 +8506,11 @@ export default [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. List available datacenters to find valid codes."
         },
         "wordpress": {
           "type": "object",
@@ -9202,7 +9206,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
+    "description": "Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)\ninstead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and\nreturns the created setup.\n\nCreate a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nWhen the order has no hosting account yet, a new hosting account is set up first, in the\ndatacenter given by `datacenter_code` or the order's default datacenter when it is omitted.\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -9210,7 +9214,7 @@ export default [
       "properties": {
         "domain": {
           "type": "string",
-          "description": "Domain name for the website. Cannot start with \"www.\""
+          "description": "Domain name for the website. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`."
         },
         "order_id": {
           "type": "integer",
@@ -9218,7 +9222,7 @@ export default [
         },
         "datacenter_code": {
           "type": "string",
-          "description": "Datacenter code. This parameter is required when creating the first website on a new hosting plan."
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. Must be an available datacenter; list available datacenters to find valid codes."
         }
       },
       "required": [

package/src/core/tools/all.ts

@@ -1969,14 +1969,14 @@ const tools: OpenApiTool[] = [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_run-website",
-    "title": "Run website scan",
+    "name": "agent-readiness_scans_run",
+    "title": "Run agent readiness scan",
     "annotations": {
-      "title": "Run website scan",
+      "title": "Run agent readiness scan",
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get website scan` operation with the same domain every\nfew seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
+    "description": "Start a scan of how ready a public website is for AI agents to discover, read and act on.\\n\nScanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`\nwith no results yet. To get the results, poll the `Get agent readiness scan` operation with the same\ndomain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,\nplus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\\n\nStarting a scan for a domain that already has a pending scan from the last 5 minutes\nreturns that scan instead of starting a new one.",
     "method": "POST",
     "path": "/api/agent-readiness/v1/scans",
     "inputSchema": {
@@ -1999,14 +1999,14 @@ const tools: OpenApiTool[] = [
     "group": "agent-readiness"
   },
   {
-    "name": "agent-readiness_scans_website",
-    "title": "Get website scan",
+    "name": "agent-readiness_scans_get",
+    "title": "Get agent readiness scan",
     "annotations": {
-      "title": "Get website scan",
+      "title": "Get agent readiness scan",
       "readOnlyHint": true,
       "destructiveHint": false
     },
-    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run website scan` operation are asynchronous. While the status is `pending`,\nthe result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run website scan` operation first.",
+    "description": "Get the latest agent readiness scan of a website.\\n\nScans started with the `Run agent readiness scan` operation are asynchronous. While the status is\n`pending`, the result fields are null; wait a few seconds and call this operation again until the status is\n`completed` or `failed`. A `failed` scan is not retried; run the scan again.\\n\nA completed scan has a 0-100 score, a letter grade, a score per category, and the result of every\ncheck with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\\n\nReturns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.",
     "method": "GET",
     "path": "/api/agent-readiness/v1/scans/{domain}",
     "inputSchema": {
@@ -8498,7 +8498,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
     "method": "POST",
     "path": "/api/hosting/v1/orders/{order_id}/onboardings",
     "inputSchema": {
@@ -8520,7 +8520,11 @@ const tools: OpenApiTool[] = [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. List available datacenters to find valid codes."
         },
         "wordpress": {
           "type": "object",
@@ -9216,7 +9220,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
+    "description": "Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)\ninstead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and\nreturns the created setup.\n\nCreate a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nWhen the order has no hosting account yet, a new hosting account is set up first, in the\ndatacenter given by `datacenter_code` or the order's default datacenter when it is omitted.\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -9224,7 +9228,7 @@ const tools: OpenApiTool[] = [
       "properties": {
         "domain": {
           "type": "string",
-          "description": "Domain name for the website. Cannot start with \"www.\""
+          "description": "Domain name for the website. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`."
         },
         "order_id": {
           "type": "integer",
@@ -9232,7 +9236,7 @@ const tools: OpenApiTool[] = [
         },
         "datacenter_code": {
           "type": "string",
-          "description": "Datacenter code. This parameter is required when creating the first website on a new hosting plan."
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. Must be an available datacenter; list available datacenters to find valid codes."
         }
       },
       "required": [

package/src/core/tools/hosting.js

@@ -2874,7 +2874,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
     "method": "POST",
     "path": "/api/hosting/v1/orders/{order_id}/onboardings",
     "inputSchema": {
@@ -2896,7 +2896,11 @@ export default [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. List available datacenters to find valid codes."
         },
         "wordpress": {
           "type": "object",
@@ -3592,7 +3596,7 @@ export default [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
+    "description": "Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)\ninstead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and\nreturns the created setup.\n\nCreate a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nWhen the order has no hosting account yet, a new hosting account is set up first, in the\ndatacenter given by `datacenter_code` or the order's default datacenter when it is omitted.\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -3600,7 +3604,7 @@ export default [
       "properties": {
         "domain": {
           "type": "string",
-          "description": "Domain name for the website. Cannot start with \"www.\""
+          "description": "Domain name for the website. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`."
         },
         "order_id": {
           "type": "integer",
@@ -3608,7 +3612,7 @@ export default [
         },
         "datacenter_code": {
           "type": "string",
-          "description": "Datacenter code. This parameter is required when creating the first website on a new hosting plan."
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. Must be an available datacenter; list available datacenters to find valid codes."
         }
       },
       "required": [

package/src/core/tools/hosting.ts

@@ -2888,7 +2888,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nThe order must already have a hosting account: to create the first website on a new\nhosting plan use the create website endpoint, which takes the `datacenter_code`.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
+    "description": "Starts a website setup on a Web or Cloud hosting order and returns the created setup\nright away; the website itself is provisioned asynchronously. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for\n`status: completed` before uploading files, deploying or creating databases.\n\nOmit `type` for an empty website. `type: wordpress` installs WordPress in the website\nroot with the admin user, email and password from `wordpress`, the domain as the site\ntitle, and `en_US` when `wordpress.language` is omitted. The headless types\n(`headless_wordpress`, `headless_ecommerce`, `headless_pocketbase`) create a headless\nwebsite; `headless_wordpress` additionally installs WordPress into the `cms` directory\nof the website root with generated credentials.\n\nOmit `domain` to set the website up on a generated temporary free subdomain.\n\nWhen the order has no hosting account yet, the setup creates one first, in the datacenter\ngiven by `datacenter_code` or the order's default datacenter when it is omitted.\nReturns 404 when the order does not exist or is not accessible to the authenticated\nclient, and 409 with a `Retry-After` header while a setup for the same domain is still\nrunning.",
     "method": "POST",
     "path": "/api/hosting/v1/orders/{order_id}/onboardings",
     "inputSchema": {
@@ -2910,7 +2910,11 @@ const tools: OpenApiTool[] = [
         },
         "domain": {
           "type": "string",
-          "description": "Customer-owned domain. Cannot start with \"www.\". Omit or `null` to set the website up on a generated temporary free subdomain."
+          "description": "Customer-owned domain. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain."
+        },
+        "datacenter_code": {
+          "type": "string",
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. List available datacenters to find valid codes."
         },
         "wordpress": {
           "type": "object",
@@ -3606,7 +3610,7 @@ const tools: OpenApiTool[] = [
       "readOnlyHint": false,
       "destructiveHint": false
     },
-    "description": "Create a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nThe datacenter_code parameter is required when creating the first website\non a new hosting plan - this will set up and configure new hosting account\nin the selected datacenter.\n\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
+    "description": "Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)\ninstead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and\nreturns the created setup.\n\nCreate a new website for the authenticated client.\n\nYou must choose which hosting order to create this website on. Pass that\norder as `order_id` together with the domain name. List orders to see\navailable IDs; the website is provisioned on that order's hosting plan.\n\nOnly Web and Cloud hosting orders are accepted. To create a website on an Agency\nPlan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.\n\nWhen the order has no hosting account yet, a new hosting account is set up first, in the\ndatacenter given by `datacenter_code` or the order's default datacenter when it is omitted.\nSubsequent websites will be hosted on the same datacenter automatically.\n\nWebsite creation is asynchronous and takes up to a few minutes. Poll the list website\nsetups endpoint with the `domain` filter every 10 to 15 seconds and wait for `status:\ncompleted` before uploading files, deploying or creating databases. While the setup is\n`running`, endpoints that operate on the website may respond with `404` or `409`.\n`is_enabled` on the websites list reflects suspension, not readiness.",
     "method": "POST",
     "path": "/api/hosting/v1/websites",
     "inputSchema": {
@@ -3614,7 +3618,7 @@ const tools: OpenApiTool[] = [
       "properties": {
         "domain": {
           "type": "string",
-          "description": "Domain name for the website. Cannot start with \"www.\""
+          "description": "Domain name for the website. Cannot start with \"www.\" and can have at most one subdomain level, e.g. `blog.example.com`."
         },
         "order_id": {
           "type": "integer",
@@ -3622,7 +3626,7 @@ const tools: OpenApiTool[] = [
         },
         "datacenter_code": {
           "type": "string",
-          "description": "Datacenter code. This parameter is required when creating the first website on a new hosting plan."
+          "description": "Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. Must be an available datacenter; list available datacenters to find valid codes."
         }
       },
       "required": [

package/src/servers/agency-hosting.js

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

package/src/servers/agency-hosting.ts

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

package/src/servers/agent-readiness.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.17.0', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.18.0', tools });

package/src/servers/agent-readiness.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/agent-readiness.js';
 
-startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.17.0', tools });
+startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.18.0', tools });

package/src/servers/all.js

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.17.0', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.18.0', tools, instructions, skills });

package/src/servers/all.ts

@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
 import instructions from '../core/instructions.js';
 import skills from '../core/skills.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '2.17.0', tools, instructions, skills });
+startServer({ name: 'hostinger-api-mcp', version: '2.18.0', tools, instructions, skills });

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: '2.17.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '2.18.0', tools });

package/src/servers/hosting.js

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

package/src/servers/hosting.ts

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

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: '2.17.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.18.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: '2.17.0', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '2.18.0', tools });

package/types.d.ts

@@ -1081,13 +1081,13 @@ Use it to show the human-readable name of each `check_id` in a scan's results.
   /**
    * Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
 Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`
-with no results yet. To get the results, poll the `Get website scan` operation with the same domain every
-few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
+with no results yet. To get the results, poll the `Get agent readiness scan` operation with the same
+domain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
 plus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\n
 Starting a scan for a domain that already has a pending scan from the last 5 minutes
 returns that scan instead of starting a new one.
    */
-  "agent-readiness_scans_run-website": {
+  "agent-readiness_scans_run": {
     params: {
       /**
        * Domain name or full URL of the website to scan. Only the host is used.
@@ -1099,14 +1099,14 @@ returns that scan instead of starting a new one.
 
   /**
    * Get the latest agent readiness scan of a website.\n
-Scans started with the `Run website scan` operation are asynchronous. While the status is `pending`,
-the result fields are null; wait a few seconds and call this operation again until the status is
+Scans started with the `Run agent readiness scan` operation are asynchronous. While the status is
+`pending`, the result fields are null; wait a few seconds and call this operation again until the status is
 `completed` or `failed`. A `failed` scan is not retried; run the scan again.\n
 A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
 check with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\n
-Returns 404 when the domain has never been scanned; use the `Run website scan` operation first.
+Returns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.
    */
-  "agent-readiness_scans_website": {
+  "agent-readiness_scans_get": {
     params: {
       /**
        * Domain name the scan was run for
@@ -4893,8 +4893,8 @@ of the website root with generated credentials.
 
 Omit `domain` to set the website up on a generated temporary free subdomain.
 
-The order must already have a hosting account: to create the first website on a new
-hosting plan use the create website endpoint, which takes the `datacenter_code`.
+When the order has no hosting account yet, the setup creates one first, in the datacenter
+given by `datacenter_code` or the order's default datacenter when it is omitted.
 Returns 404 when the order does not exist or is not accessible to the authenticated
 client, and 409 with a `Retry-After` header while a setup for the same domain is still
 running.
@@ -4910,9 +4910,13 @@ running.
        */
       type?: string;
       /**
-       * Customer-owned domain. Cannot start with "www.". Omit or `null` to set the website up on a generated temporary free subdomain.
+       * Customer-owned domain. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`. Omit or `null` to set the website up on a generated temporary free subdomain.
        */
       domain?: string;
+      /**
+       * Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. List available datacenters to find valid codes.
+       */
+      datacenter_code?: string;
       /**
        * WordPress install settings. Required when `type` is `wordpress`, not allowed otherwise. The site title is the domain.
        */
@@ -5320,7 +5324,11 @@ endpoint instead.
   };
 
   /**
-   * Create a new website for the authenticated client.
+   * Deprecated: use `POST /api/hosting/v1/orders/{order_id}/onboardings` (start website setup)
+instead. It takes the same `domain` and `datacenter_code`, can also install WordPress, and
+returns the created setup.
+
+Create a new website for the authenticated client.
 
 You must choose which hosting order to create this website on. Pass that
 order as `order_id` together with the domain name. List orders to see
@@ -5329,10 +5337,8 @@ available IDs; the website is provisioned on that order's hosting plan.
 Only Web and Cloud hosting orders are accepted. To create a website on an Agency
 Plan order, use `POST /api/agency-hosting/v1/orders/{order_id}/websites/setups`.
 
-The datacenter_code parameter is required when creating the first website
-on a new hosting plan - this will set up and configure new hosting account
-in the selected datacenter.
-
+When the order has no hosting account yet, a new hosting account is set up first, in the
+datacenter given by `datacenter_code` or the order's default datacenter when it is omitted.
 Subsequent websites will be hosted on the same datacenter automatically.
 
 Website creation is asynchronous and takes up to a few minutes. Poll the list website
@@ -5344,7 +5350,7 @@ completed` before uploading files, deploying or creating databases. While the se
   "hosting_websites_create": {
     params: {
       /**
-       * Domain name for the website. Cannot start with "www."
+       * Domain name for the website. Cannot start with "www." and can have at most one subdomain level, e.g. `blog.example.com`.
        */
       domain: string;
       /**
@@ -5352,7 +5358,7 @@ completed` before uploading files, deploying or creating databases. While the se
        */
       order_id: number;
       /**
-       * Datacenter code. This parameter is required when creating the first website on a new hosting plan.
+       * Datacenter for the hosting account when the order does not have one yet. Omit to use the order's default datacenter. Ignored when the order already has a hosting account. Must be an available datacenter; list available datacenters to find valid codes.
        */
       datacenter_code?: string;
     };