@hostinger/mcp 3.31.3 → 3.31.4

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.31.4 — 2026-11-09
8
+
9
+ ### Operations
10
+
11
+ - Changed the description of `domains_portfolio_claim-free`
12
+ - Changed the description of `domains_portfolio_list`
13
+ - Changed the description of `domains_transfer_claim-free`
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.31.3 — 2026-11-09
8
22
 
9
23
  ### Also in this release
package/README.md CHANGED
@@ -1200,6 +1200,13 @@ Claim a free domain available on your account and register it.
1200
1200
  Unlike purchasing a domain, this consumes a free domain you already have,
1201
1201
  so no payment method is required.
1202
1202
 
1203
+ A free domain and a free domain transfer from the same plan are alternatives:
1204
+ claiming the free domain removes the plan's free domain transfer
1205
+ (`type: free_domain_transfer`). Before making request, confirm with the user which
1206
+ of the two they want. Right after a claim, the removed free domain transfer may
1207
+ still appear in the [domain list endpoint](#tag/domains-portfolio) for a short
1208
+ time; do not claim it.
1209
+
1203
1210
  A successful response means the domain is registered. If registration fails, login to
1204
1211
  [hPanel](https://hpanel.hostinger.com/) and check domain registration status.
1205
1212
 
@@ -1252,6 +1259,10 @@ Use this endpoint to view comprehensive domain configuration and status.
1252
1259
 
1253
1260
  Retrieve all domains associated with your account.
1254
1261
 
1262
+ A plan can include both a free domain (`type: free_domain`) and a free domain
1263
+ transfer (`type: free_domain_transfer`). They are alternatives: claiming one
1264
+ removes the other, which may still be listed for a short time after the claim.
1265
+
1255
1266
  Use this endpoint to view user's domain portfolio.
1256
1267
 
1257
1268
  - **Method**: `GET`
@@ -1362,6 +1373,12 @@ Claim a free domain transfer available on your account and start the transfer.
1362
1373
  Unlike purchasing a transfer, this consumes a free domain transfer you already have,
1363
1374
  so no payment method is required.
1364
1375
 
1376
+ A free domain and a free domain transfer from the same plan are alternatives:
1377
+ claiming the free domain transfer removes the plan's free domain
1378
+ (`type: free_domain`). Before making request, confirm with the user which of the
1379
+ two they want. Right after a claim, the removed free domain may still appear in
1380
+ the [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.
1381
+
1365
1382
  Before making request, unlock the domain at the current registrar and get its authorization
1366
1383
  code. The transfer is validated first, so domains which cannot be transferred are rejected
1367
1384
  before the free domain transfer is consumed.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "3.31.3",
3
+ "version": "3.31.4",
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.31.3",
3
+ "version": "3.31.4",
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.31.3",
20
+ "version": "3.31.4",
21
21
  "packages": [
22
22
  {
23
23
  "registryType": "npm",
24
24
  "identifier": "@hostinger/mcp",
25
- "version": "3.31.3",
25
+ "version": "3.31.4",
26
26
  "transport": {
27
27
  "type": "stdio"
28
28
  },
@@ -1,3 +1,3 @@
1
- version=3.31.3
1
+ version=3.31.4
2
2
  commit=fe38647c8150
3
3
  built=2026-11-09
@@ -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.8.0
65
+ * Generated from OpenAPI spec version 2.8.1
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.8.0
97
+ * Generated from OpenAPI spec version 2.8.1
98
98
  */
99
99
  class MCPServer {
100
100
  private readonly name: string;
@@ -4031,7 +4031,7 @@ export default [
4031
4031
  "readOnlyHint": false,
4032
4032
  "destructiveHint": false
4033
4033
  },
4034
- "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
4034
+ "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain removes the plan's free domain transfer\n(`type: free_domain_transfer`). Before making request, confirm with the user which\nof the two they want. Right after a claim, the removed free domain transfer may\nstill appear in the [domain list endpoint](#tag/domains-portfolio) for a short\ntime; do not claim it.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
4035
4035
  "method": "POST",
4036
4036
  "path": "/api/domains/v1/portfolio/claim",
4037
4037
  "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\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\nUse this endpoint to view user's domain portfolio.",
4184
4184
  "method": "GET",
4185
4185
  "path": "/api/domains/v1/portfolio",
4186
4186
  "inputSchema": {
@@ -4475,7 +4475,7 @@ export default [
4475
4475
  "readOnlyHint": false,
4476
4476
  "destructiveHint": false
4477
4477
  },
4478
- "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
4478
+ "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain transfer removes the plan's free domain\n(`type: free_domain`). Before making request, confirm with the user which of the\ntwo they want. Right after a claim, the removed free domain may still appear in\nthe [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
4479
4479
  "method": "POST",
4480
4480
  "path": "/api/domains/v1/transfers/claim",
4481
4481
  "inputSchema": {
@@ -4048,7 +4048,7 @@ const tools: OpenApiTool[] = [
4048
4048
  "readOnlyHint": false,
4049
4049
  "destructiveHint": false
4050
4050
  },
4051
- "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
4051
+ "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain removes the plan's free domain transfer\n(`type: free_domain_transfer`). Before making request, confirm with the user which\nof the two they want. Right after a claim, the removed free domain transfer may\nstill appear in the [domain list endpoint](#tag/domains-portfolio) for a short\ntime; do not claim it.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
4052
4052
  "method": "POST",
4053
4053
  "path": "/api/domains/v1/portfolio/claim",
4054
4054
  "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\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\nUse this endpoint to view user's domain portfolio.",
4201
4201
  "method": "GET",
4202
4202
  "path": "/api/domains/v1/portfolio",
4203
4203
  "inputSchema": {
@@ -4492,7 +4492,7 @@ const tools: OpenApiTool[] = [
4492
4492
  "readOnlyHint": false,
4493
4493
  "destructiveHint": false
4494
4494
  },
4495
- "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
4495
+ "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain transfer removes the plan's free domain\n(`type: free_domain`). Before making request, confirm with the user which of the\ntwo they want. Right after a claim, the removed free domain may still appear in\nthe [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
4496
4496
  "method": "POST",
4497
4497
  "path": "/api/domains/v1/transfers/claim",
4498
4498
  "inputSchema": {
@@ -703,7 +703,7 @@ export default [
703
703
  "readOnlyHint": false,
704
704
  "destructiveHint": false
705
705
  },
706
- "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
706
+ "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain removes the plan's free domain transfer\n(`type: free_domain_transfer`). Before making request, confirm with the user which\nof the two they want. Right after a claim, the removed free domain transfer may\nstill appear in the [domain list endpoint](#tag/domains-portfolio) for a short\ntime; do not claim it.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
707
707
  "method": "POST",
708
708
  "path": "/api/domains/v1/portfolio/claim",
709
709
  "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\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\nUse this endpoint to view user's domain portfolio.",
856
856
  "method": "GET",
857
857
  "path": "/api/domains/v1/portfolio",
858
858
  "inputSchema": {
@@ -1147,7 +1147,7 @@ export default [
1147
1147
  "readOnlyHint": false,
1148
1148
  "destructiveHint": false
1149
1149
  },
1150
- "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
1150
+ "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain transfer removes the plan's free domain\n(`type: free_domain`). Before making request, confirm with the user which of the\ntwo they want. Right after a claim, the removed free domain may still appear in\nthe [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
1151
1151
  "method": "POST",
1152
1152
  "path": "/api/domains/v1/transfers/claim",
1153
1153
  "inputSchema": {
@@ -720,7 +720,7 @@ const tools: OpenApiTool[] = [
720
720
  "readOnlyHint": false,
721
721
  "destructiveHint": false
722
722
  },
723
- "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
723
+ "description": "Claim a free domain available on your account and register it.\n\nUnlike purchasing a domain, this consumes a free domain you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain removes the plan's free domain transfer\n(`type: free_domain_transfer`). Before making request, confirm with the user which\nof the two they want. Right after a claim, the removed free domain transfer may\nstill appear in the [domain list endpoint](#tag/domains-portfolio) for a short\ntime; do not claim it.\n\nA successful response means the domain is registered. If registration fails, login to\n[hPanel](https://hpanel.hostinger.com/) and check domain registration status.\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nSome TLDs require `additional_details` to be provided and these will be validated before claiming.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body,\nfor example `2037` when no free domain is available.\n\nUse this endpoint to register a domain using a free domain from your account.",
724
724
  "method": "POST",
725
725
  "path": "/api/domains/v1/portfolio/claim",
726
726
  "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\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\nUse this endpoint to view user's domain portfolio.",
873
873
  "method": "GET",
874
874
  "path": "/api/domains/v1/portfolio",
875
875
  "inputSchema": {
@@ -1164,7 +1164,7 @@ const tools: OpenApiTool[] = [
1164
1164
  "readOnlyHint": false,
1165
1165
  "destructiveHint": false
1166
1166
  },
1167
- "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
1167
+ "description": "Claim a free domain transfer available on your account and start the transfer.\n\nUnlike purchasing a transfer, this consumes a free domain transfer you already have,\nso no payment method is required.\n\nA free domain and a free domain transfer from the same plan are alternatives:\nclaiming the free domain transfer removes the plan's free domain\n(`type: free_domain`). Before making request, confirm with the user which of the\ntwo they want. Right after a claim, the removed free domain may still appear in\nthe [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.\n\nBefore making request, unlock the domain at the current registrar and get its authorization\ncode. The transfer is validated first, so domains which cannot be transferred are rejected\nbefore the free domain transfer is consumed.\n\nA successful response means the transfer has been started. Completion depends on the current\nregistrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).\n\nIf no WHOIS information is provided, default contact information for that TLD will be used.\nBefore making request, ensure WHOIS information for desired TLD exists in your account.\n\nRequests which cannot be fulfilled are rejected with an error code in the response body.\n\nUse this endpoint to transfer a domain using a free domain transfer from your account.",
1168
1168
  "method": "POST",
1169
1169
  "path": "/api/domains/v1/transfers/claim",
1170
1170
  "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.31.3', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.31.4', 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.31.3', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '3.31.4', 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.31.3', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.31.4', 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.31.3', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-gpu-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '3.31.4', 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.31.3', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.31.4', 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.31.3', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.31.4', 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.31.3', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '3.31.4', tools });
package/types.d.ts CHANGED
@@ -2159,6 +2159,13 @@ Use this endpoint to obtain the code required to transfer a domain to another re
2159
2159
  Unlike purchasing a domain, this consumes a free domain you already have,
2160
2160
  so no payment method is required.
2161
2161
 
2162
+ A free domain and a free domain transfer from the same plan are alternatives:
2163
+ claiming the free domain removes the plan's free domain transfer
2164
+ (`type: free_domain_transfer`). Before making request, confirm with the user which
2165
+ of the two they want. Right after a claim, the removed free domain transfer may
2166
+ still appear in the [domain list endpoint](#tag/domains-portfolio) for a short
2167
+ time; do not claim it.
2168
+
2162
2169
  A successful response means the domain is registered. If registration fails, login to
2163
2170
  [hPanel](https://hpanel.hostinger.com/) and check domain registration status.
2164
2171
 
@@ -2243,6 +2250,10 @@ Use this endpoint to view comprehensive domain configuration and status.
2243
2250
  /**
2244
2251
  * Retrieve all domains associated with your account.
2245
2252
 
2253
+ A plan can include both a free domain (`type: free_domain`) and a free domain
2254
+ transfer (`type: free_domain_transfer`). They are alternatives: claiming one
2255
+ removes the other, which may still be listed for a short time after the claim.
2256
+
2246
2257
  Use this endpoint to view user's domain portfolio.
2247
2258
  */
2248
2259
  "domains_portfolio_list": {
@@ -2436,6 +2447,12 @@ Use this endpoint to configure custom DNS hosting for domains.
2436
2447
  Unlike purchasing a transfer, this consumes a free domain transfer you already have,
2437
2448
  so no payment method is required.
2438
2449
 
2450
+ A free domain and a free domain transfer from the same plan are alternatives:
2451
+ claiming the free domain transfer removes the plan's free domain
2452
+ (`type: free_domain`). Before making request, confirm with the user which of the
2453
+ two they want. Right after a claim, the removed free domain may still appear in
2454
+ the [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.
2455
+
2439
2456
  Before making request, unlock the domain at the current registrar and get its authorization
2440
2457
  code. The transfer is validated first, so domains which cannot be transferred are rejected
2441
2458
  before the free domain transfer is consumed.