@hostinger/mcp 3.34.1 → 3.35.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,20 @@ Generated at release time from the diff between the previous and current
4
4
  build. Tool changes are listed individually; everything else is summarised
5
5
  by area.
6
6
 
7
+ ## v3.35.0 — 2026-11-10
8
+
9
+ ### Operations
10
+
11
+ - Changed the description of `domains_portfolio_get`
12
+ - Changed the description of `domains_portfolio_list`
13
+ - Changed the description of `domains_portfolio_complete-setup`
14
+
15
+ ### Also in this release
16
+
17
+ - Documentation: `README.md`
18
+ - Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
19
+ - Build and packaging: `types.d.ts`
20
+
7
21
  ## v3.34.1 — 2026-11-10
8
22
 
9
23
  ### Operations
package/README.md CHANGED
@@ -1266,6 +1266,10 @@ Use this endpoint to prepare domains for transfer to other registrars.
1266
1266
 
1267
1267
  Retrieve detailed information for specified domain.
1268
1268
 
1269
+ A domain is found here only once it is registered. Until then, `Get domain list` shows it, and
1270
+ its `verification` field says what registration waits for when the domain is held for
1271
+ verification.
1272
+
1269
1273
  Use this endpoint to view comprehensive domain configuration and status.
1270
1274
 
1271
1275
  - **Method**: `GET`
@@ -1279,6 +1283,10 @@ A plan can include both a free domain (`type: free_domain`) and a free domain
1279
1283
  transfer (`type: free_domain_transfer`). They are alternatives: claiming one
1280
1284
  removes the other, which may still be listed for a short time after the claim.
1281
1285
 
1286
+ A domain held for verification before it is registered has `status: pending_verification`,
1287
+ and its `verification` field says what registration waits for: a manual review, an SMS code,
1288
+ or owner contact verification.
1289
+
1282
1290
  Use this endpoint to view user's domain portfolio.
1283
1291
 
1284
1292
  - **Method**: `GET`
@@ -1365,7 +1373,8 @@ The domain is set up with the default nameservers and with privacy protection. U
1365
1373
 
1366
1374
  A successful response means the setup request was accepted, not that the domain is already
1367
1375
  registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
1368
- only once it is registered.
1376
+ only once it is registered. When the domain is held for verification, its `verification` field
1377
+ in `Get domain list` says what registration waits for.
1369
1378
 
1370
1379
  Use this endpoint to finish registering a domain that is awaiting setup on your account.
1371
1380
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "3.34.1",
3
+ "version": "3.35.0",
4
4
  "description": "Hostinger API — manage domains, DNS, hosting, VPS, billing and more from Gemini CLI.",
5
5
  "mcpServers": {
6
6
  "hostinger": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hostinger/mcp",
3
- "version": "3.34.1",
3
+ "version": "3.35.0",
4
4
  "mcpName": "io.github.hostinger/hostinger-api-mcp",
5
5
  "description": "MCP server for Hostinger API",
6
6
  "repository": {
package/server.json CHANGED
@@ -17,12 +17,12 @@
17
17
  "url": "https://github.com/hostinger/api-mcp-server",
18
18
  "source": "github"
19
19
  },
20
- "version": "3.34.1",
20
+ "version": "3.35.0",
21
21
  "packages": [
22
22
  {
23
23
  "registryType": "npm",
24
24
  "identifier": "@hostinger/mcp",
25
- "version": "3.34.1",
25
+ "version": "3.35.0",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -1,3 +1,3 @@
1
- version=3.34.1
1
+ version=3.35.0
2
2
  commit=fe38647c8150
3
3
  built=2026-11-10
@@ -62,7 +62,7 @@ const GetSkillRequestSchema = z.object({
62
62
 
63
63
  /**
64
64
  * MCP Server for Hostinger API
65
- * Generated from OpenAPI spec version 2.11.1
65
+ * Generated from OpenAPI spec version 2.12.0
66
66
  */
67
67
  class MCPServer {
68
68
  constructor({ name, version, tools, instructions, skills = [] }) {
@@ -94,7 +94,7 @@ interface Skill { uri: string; frontmatter: Record<string, unknown>; resources:
94
94
 
95
95
  /**
96
96
  * MCP Server for Hostinger API
97
- * Generated from OpenAPI spec version 2.11.1
97
+ * Generated from OpenAPI spec version 2.12.0
98
98
  */
99
99
  class MCPServer {
100
100
  private readonly name: string;
@@ -4150,7 +4150,7 @@ export default [
4150
4150
  "readOnlyHint": true,
4151
4151
  "destructiveHint": false
4152
4152
  },
4153
- "description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
4153
+ "description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
4154
4154
  "method": "GET",
4155
4155
  "path": "/api/domains/v1/portfolio/{domain}",
4156
4156
  "inputSchema": {
@@ -4180,7 +4180,7 @@ export default [
4180
4180
  "readOnlyHint": true,
4181
4181
  "destructiveHint": false
4182
4182
  },
4183
- "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
4183
+ "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
4184
4184
  "method": "GET",
4185
4185
  "path": "/api/domains/v1/portfolio",
4186
4186
  "inputSchema": {
@@ -4369,7 +4369,7 @@ export default [
4369
4369
  "readOnlyHint": false,
4370
4370
  "destructiveHint": false
4371
4371
  },
4372
- "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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.",
4372
+ "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
4373
4373
  "method": "POST",
4374
4374
  "path": "/api/domains/v1/portfolio/{domain}/setup",
4375
4375
  "inputSchema": {
@@ -4167,7 +4167,7 @@ const tools: OpenApiTool[] = [
4167
4167
  "readOnlyHint": true,
4168
4168
  "destructiveHint": false
4169
4169
  },
4170
- "description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
4170
+ "description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
4171
4171
  "method": "GET",
4172
4172
  "path": "/api/domains/v1/portfolio/{domain}",
4173
4173
  "inputSchema": {
@@ -4197,7 +4197,7 @@ const tools: OpenApiTool[] = [
4197
4197
  "readOnlyHint": true,
4198
4198
  "destructiveHint": false
4199
4199
  },
4200
- "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
4200
+ "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
4201
4201
  "method": "GET",
4202
4202
  "path": "/api/domains/v1/portfolio",
4203
4203
  "inputSchema": {
@@ -4386,7 +4386,7 @@ const tools: OpenApiTool[] = [
4386
4386
  "readOnlyHint": false,
4387
4387
  "destructiveHint": false
4388
4388
  },
4389
- "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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.",
4389
+ "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
4390
4390
  "method": "POST",
4391
4391
  "path": "/api/domains/v1/portfolio/{domain}/setup",
4392
4392
  "inputSchema": {
@@ -822,7 +822,7 @@ export default [
822
822
  "readOnlyHint": true,
823
823
  "destructiveHint": false
824
824
  },
825
- "description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
825
+ "description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
826
826
  "method": "GET",
827
827
  "path": "/api/domains/v1/portfolio/{domain}",
828
828
  "inputSchema": {
@@ -852,7 +852,7 @@ export default [
852
852
  "readOnlyHint": true,
853
853
  "destructiveHint": false
854
854
  },
855
- "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
855
+ "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
856
856
  "method": "GET",
857
857
  "path": "/api/domains/v1/portfolio",
858
858
  "inputSchema": {
@@ -1041,7 +1041,7 @@ export default [
1041
1041
  "readOnlyHint": false,
1042
1042
  "destructiveHint": false
1043
1043
  },
1044
- "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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.",
1044
+ "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
1045
1045
  "method": "POST",
1046
1046
  "path": "/api/domains/v1/portfolio/{domain}/setup",
1047
1047
  "inputSchema": {
@@ -839,7 +839,7 @@ const tools: OpenApiTool[] = [
839
839
  "readOnlyHint": true,
840
840
  "destructiveHint": false
841
841
  },
842
- "description": "Retrieve detailed information for specified domain.\n\nUse this endpoint to view comprehensive domain configuration and status.",
842
+ "description": "Retrieve detailed information for specified domain.\n\nA domain is found here only once it is registered. Until then, `Get domain list` shows it, and\nits `verification` field says what registration waits for when the domain is held for\nverification.\n\nUse this endpoint to view comprehensive domain configuration and status.",
843
843
  "method": "GET",
844
844
  "path": "/api/domains/v1/portfolio/{domain}",
845
845
  "inputSchema": {
@@ -869,7 +869,7 @@ const tools: OpenApiTool[] = [
869
869
  "readOnlyHint": true,
870
870
  "destructiveHint": false
871
871
  },
872
- "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nUse this endpoint to view user's domain portfolio.",
872
+ "description": "Retrieve all domains associated with your account.\n\nA plan can include both a free domain (`type: free_domain`) and a free domain\ntransfer (`type: free_domain_transfer`). They are alternatives: claiming one\nremoves the other, which may still be listed for a short time after the claim.\n\nA domain held for verification before it is registered has `status: pending_verification`,\nand its `verification` field says what registration waits for: a manual review, an SMS code,\nor owner contact verification.\n\nUse this endpoint to view user's domain portfolio.",
873
873
  "method": "GET",
874
874
  "path": "/api/domains/v1/portfolio",
875
875
  "inputSchema": {
@@ -1058,7 +1058,7 @@ const tools: OpenApiTool[] = [
1058
1058
  "readOnlyHint": false,
1059
1059
  "destructiveHint": false
1060
1060
  },
1061
- "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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.",
1061
+ "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 with privacy protection. Use\n`Update domain nameservers` and `Disable 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. When the domain is held for verification, its `verification` field\nin `Get domain list` says what registration waits for.\n\nUse this endpoint to finish registering a domain that is awaiting setup on your account.",
1062
1062
  "method": "POST",
1063
1063
  "path": "/api/domains/v1/portfolio/{domain}/setup",
1064
1064
  "inputSchema": {
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agency-hosting.js';
5
5
  import instructions from '../core/instructions.agency-hosting.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.34.1', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.35.0', tools, instructions });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agency-hosting.js';
5
5
  import instructions from '../core/instructions.agency-hosting.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.34.1', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.35.0', tools, instructions });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agent-readiness.js';
5
5
 
6
- startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/agent-readiness.js';
5
5
 
6
- startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.35.0', tools });
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
5
5
  import instructions from '../core/instructions.js';
6
6
  import skills from '../core/skills.js';
7
7
 
8
- startServer({ name: 'hostinger-api-mcp', version: '3.34.1', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.35.0', tools, instructions, skills });
@@ -5,4 +5,4 @@ import tools from '../core/tools/all.js';
5
5
  import instructions from '../core/instructions.js';
6
6
  import skills from '../core/skills.js';
7
7
 
8
- startServer({ name: 'hostinger-api-mcp', version: '3.34.1', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.35.0', tools, instructions, skills });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/billing.js';
5
5
 
6
- startServer({ name: 'hostinger-billing-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/billing.js';
5
5
 
6
- startServer({ name: 'hostinger-billing-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/dns.js';
5
5
 
6
- startServer({ name: 'hostinger-dns-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/dns.js';
5
5
 
6
- startServer({ name: 'hostinger-dns-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/domains.js';
5
5
 
6
- startServer({ name: 'hostinger-domains-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/domains.js';
5
5
 
6
- startServer({ name: 'hostinger-domains-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/ecommerce.js';
5
5
 
6
- startServer({ name: 'hostinger-ecommerce-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/ecommerce.js';
5
5
 
6
- startServer({ name: 'hostinger-ecommerce-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/gpu.js';
5
5
 
6
- startServer({ name: 'hostinger-gpu-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/gpu.js';
5
5
 
6
- startServer({ name: 'hostinger-gpu-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/horizons.js';
5
5
 
6
- startServer({ name: 'hostinger-horizons-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/horizons.js';
5
5
 
6
- startServer({ name: 'hostinger-horizons-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.35.0', tools });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/hosting.js';
5
5
  import instructions from '../core/instructions.js';
6
6
 
7
- startServer({ name: 'hostinger-hosting-mcp', version: '3.34.1', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.35.0', tools, instructions });
@@ -4,4 +4,4 @@ import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/hosting.js';
5
5
  import instructions from '../core/instructions.js';
6
6
 
7
- startServer({ name: 'hostinger-hosting-mcp', version: '3.34.1', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.35.0', tools, instructions });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/mail.js';
5
5
 
6
- startServer({ name: 'hostinger-mail-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/mail.js';
5
5
 
6
- startServer({ name: 'hostinger-mail-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/reach.js';
5
5
 
6
- startServer({ name: 'hostinger-reach-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/reach.js';
5
5
 
6
- startServer({ name: 'hostinger-reach-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/vps.js';
5
5
 
6
- startServer({ name: 'hostinger-vps-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/vps.js';
5
5
 
6
- startServer({ name: 'hostinger-vps-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/wordpress.js';
5
5
 
6
- startServer({ name: 'hostinger-wordpress-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.35.0', tools });
@@ -3,4 +3,4 @@
3
3
  import { startServer } from '../core/runtime.js';
4
4
  import tools from '../core/tools/wordpress.js';
5
5
 
6
- startServer({ name: 'hostinger-wordpress-mcp', version: '3.34.1', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.35.0', tools });
package/types.d.ts CHANGED
@@ -2251,6 +2251,10 @@ Use this endpoint to prepare domains for transfer to other registrars.
2251
2251
  /**
2252
2252
  * Retrieve detailed information for specified domain.
2253
2253
 
2254
+ A domain is found here only once it is registered. Until then, `Get domain list` shows it, and
2255
+ its `verification` field says what registration waits for when the domain is held for
2256
+ verification.
2257
+
2254
2258
  Use this endpoint to view comprehensive domain configuration and status.
2255
2259
  */
2256
2260
  "domains_portfolio_get": {
@@ -2270,6 +2274,10 @@ A plan can include both a free domain (`type: free_domain`) and a free domain
2270
2274
  transfer (`type: free_domain_transfer`). They are alternatives: claiming one
2271
2275
  removes the other, which may still be listed for a short time after the claim.
2272
2276
 
2277
+ A domain held for verification before it is registered has `status: pending_verification`,
2278
+ and its `verification` field says what registration waits for: a manual review, an SMS code,
2279
+ or owner contact verification.
2280
+
2273
2281
  Use this endpoint to view user's domain portfolio.
2274
2282
  */
2275
2283
  "domains_portfolio_list": {
@@ -2403,7 +2411,8 @@ The domain is set up with the default nameservers and with privacy protection. U
2403
2411
 
2404
2412
  A successful response means the setup request was accepted, not that the domain is already
2405
2413
  registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
2406
- only once it is registered.
2414
+ only once it is registered. When the domain is held for verification, its `verification` field
2415
+ in `Get domain list` says what registration waits for.
2407
2416
 
2408
2417
  Use this endpoint to finish registering a domain that is awaiting setup on your account.
2409
2418
  */