@hostinger/mcp 2.16.0 → 2.17.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,22 @@ 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
+ ## v2.17.0 — 2026-10-15
8
+
9
+ ### Operations
10
+
11
+ - Added `agent-readiness_checks_list` — List checks
12
+ - Added `agent-readiness_scans_run-website` — Run website scan
13
+ - Added `agent-readiness_scans_website` — Get website scan
14
+
15
+ ### Also in this release
16
+
17
+ - Documentation: `README.md`
18
+ - Dependencies: `package-lock.json`, `package.json`
19
+ - Request handling and authentication: `src/core/runtime.js`, `src/core/runtime.ts`
20
+ - Build and packaging: `types.d.ts`
21
+ - Server entry points: `src/servers/agent-readiness.js`, `src/servers/agent-readiness.ts`
22
+
7
23
  ## v2.16.0 — 2026-10-14
8
24
 
9
25
  No changes to the published artifact.
package/README.md CHANGED
@@ -69,8 +69,9 @@ pnpm update -g @hostinger/mcp
69
69
 
70
70
  This package installs the following MCP server commands:
71
71
 
72
- - `hostinger-api-mcp` — unified server over every operation (417 total)
72
+ - `hostinger-api-mcp` — unified server over every operation (420 total)
73
73
  - `hostinger-agency-hosting-mcp` — 42 operations for agency-hosting
74
+ - `hostinger-agent-readiness-mcp` — 3 operations for agent-readiness
74
75
  - `hostinger-billing-mcp` — 9 operations for billing
75
76
  - `hostinger-dns-mcp` — 8 operations for dns
76
77
  - `hostinger-domains-mcp` — 42 operations for domains
@@ -680,6 +681,42 @@ Lists the WordPress core versions available for installation on an Agency Plan w
680
681
  - **Method**: `GET`
681
682
  - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/versions`
682
683
 
684
+ ### `hostinger-agent-readiness-mcp`
685
+
686
+ #### agent-readiness_checks_list
687
+
688
+ List every check an agent readiness scan runs, with its name, category and weight.\n
689
+ Use it to show the human-readable name of each `check_id` in a scan's results.
690
+
691
+ - **Method**: `GET`
692
+ - **Path**: `/api/agent-readiness/v1/checks`
693
+
694
+ #### agent-readiness_scans_run-website
695
+
696
+ Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
697
+ Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`
698
+ with no results yet. To get the results, poll the `Get website scan` operation with the same domain every
699
+ few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
700
+ plus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\n
701
+ Starting a scan for a domain that already has a pending scan from the last 5 minutes
702
+ returns that scan instead of starting a new one.
703
+
704
+ - **Method**: `POST`
705
+ - **Path**: `/api/agent-readiness/v1/scans`
706
+
707
+ #### agent-readiness_scans_website
708
+
709
+ Get the latest agent readiness scan of a website.\n
710
+ Scans started with the `Run website scan` operation are asynchronous. While the status is `pending`,
711
+ the result fields are null; wait a few seconds and call this operation again until the status is
712
+ `completed` or `failed`. A `failed` scan is not retried; run the scan again.\n
713
+ A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
714
+ check with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\n
715
+ Returns 404 when the domain has never been scanned; use the `Run website scan` operation first.
716
+
717
+ - **Method**: `GET`
718
+ - **Path**: `/api/agent-readiness/v1/scans/{domain}`
719
+
683
720
  ### `hostinger-billing-mcp`
684
721
 
685
722
  #### billing_catalog_list
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hostinger-api-mcp",
3
- "version": "2.16.0",
3
+ "version": "2.17.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": "2.16.0",
3
+ "version": "2.17.0",
4
4
  "mcpName": "io.github.hostinger/hostinger-api-mcp",
5
5
  "description": "MCP server for Hostinger API",
6
6
  "repository": {
@@ -20,6 +20,7 @@
20
20
  "bin": {
21
21
  "hostinger-api-mcp": "./src/servers/all.js",
22
22
  "hostinger-agency-hosting-mcp": "./src/servers/agency-hosting.js",
23
+ "hostinger-agent-readiness-mcp": "./src/servers/agent-readiness.js",
23
24
  "hostinger-billing-mcp": "./src/servers/billing.js",
24
25
  "hostinger-dns-mcp": "./src/servers/dns.js",
25
26
  "hostinger-domains-mcp": "./src/servers/domains.js",
package/server.json CHANGED
@@ -6,12 +6,12 @@
6
6
  "url": "https://github.com/hostinger/api-mcp-server",
7
7
  "source": "github"
8
8
  },
9
- "version": "2.16.0",
9
+ "version": "2.17.0",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "identifier": "@hostinger/mcp",
14
- "version": "2.16.0",
14
+ "version": "2.17.0",
15
15
  "transport": {
16
16
  "type": "stdio"
17
17
  },
@@ -64,7 +64,7 @@ const GetSkillRequestSchema = z.object({
64
64
 
65
65
  /**
66
66
  * MCP Server for Hostinger API
67
- * Generated from OpenAPI spec version 1.66.0
67
+ * Generated from OpenAPI spec version 1.67.0
68
68
  */
69
69
  class MCPServer {
70
70
  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 1.66.0
97
+ * Generated from OpenAPI spec version 1.67.0
98
98
  */
99
99
  class MCPServer {
100
100
  private readonly name: string;
@@ -0,0 +1,86 @@
1
+ // Auto-generated tool list for group: agent-readiness
2
+ export default [
3
+ {
4
+ "name": "agent-readiness_checks_list",
5
+ "title": "List checks",
6
+ "annotations": {
7
+ "title": "List checks",
8
+ "readOnlyHint": true,
9
+ "destructiveHint": false
10
+ },
11
+ "description": "List every check an agent readiness scan runs, with its name, category and weight.\\n\nUse it to show the human-readable name of each `check_id` in a scan's results.",
12
+ "method": "GET",
13
+ "path": "/api/agent-readiness/v1/checks",
14
+ "inputSchema": {
15
+ "type": "object",
16
+ "properties": {},
17
+ "required": []
18
+ },
19
+ "security": [
20
+ {
21
+ "apiToken": []
22
+ }
23
+ ],
24
+ "group": "agent-readiness"
25
+ },
26
+ {
27
+ "name": "agent-readiness_scans_run-website",
28
+ "title": "Run website scan",
29
+ "annotations": {
30
+ "title": "Run website scan",
31
+ "readOnlyHint": false,
32
+ "destructiveHint": false
33
+ },
34
+ "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.",
35
+ "method": "POST",
36
+ "path": "/api/agent-readiness/v1/scans",
37
+ "inputSchema": {
38
+ "type": "object",
39
+ "properties": {
40
+ "domain": {
41
+ "type": "string",
42
+ "description": "Domain name or full URL of the website to scan. Only the host is used."
43
+ }
44
+ },
45
+ "required": [
46
+ "domain"
47
+ ]
48
+ },
49
+ "security": [
50
+ {
51
+ "apiToken": []
52
+ }
53
+ ],
54
+ "group": "agent-readiness"
55
+ },
56
+ {
57
+ "name": "agent-readiness_scans_website",
58
+ "title": "Get website scan",
59
+ "annotations": {
60
+ "title": "Get website scan",
61
+ "readOnlyHint": true,
62
+ "destructiveHint": false
63
+ },
64
+ "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.",
65
+ "method": "GET",
66
+ "path": "/api/agent-readiness/v1/scans/{domain}",
67
+ "inputSchema": {
68
+ "type": "object",
69
+ "properties": {
70
+ "domain": {
71
+ "type": "string",
72
+ "description": "Domain name the scan was run for"
73
+ }
74
+ },
75
+ "required": [
76
+ "domain"
77
+ ]
78
+ },
79
+ "security": [
80
+ {
81
+ "apiToken": []
82
+ }
83
+ ],
84
+ "group": "agent-readiness"
85
+ }
86
+ ];
@@ -0,0 +1,101 @@
1
+ // Auto-generated tool list for group: agent-readiness
2
+ import type { Tool } from "@modelcontextprotocol/sdk/types.js";
3
+
4
+ export interface OpenApiTool extends Tool {
5
+ method: string;
6
+ path: string;
7
+ security: unknown[];
8
+ custom?: boolean;
9
+ group?: string;
10
+ topic?: string;
11
+ handlerMethod?: string;
12
+ templateFile?: string;
13
+ templateFileTS?: string;
14
+ }
15
+
16
+ const tools: OpenApiTool[] = [
17
+ {
18
+ "name": "agent-readiness_checks_list",
19
+ "title": "List checks",
20
+ "annotations": {
21
+ "title": "List checks",
22
+ "readOnlyHint": true,
23
+ "destructiveHint": false
24
+ },
25
+ "description": "List every check an agent readiness scan runs, with its name, category and weight.\\n\nUse it to show the human-readable name of each `check_id` in a scan's results.",
26
+ "method": "GET",
27
+ "path": "/api/agent-readiness/v1/checks",
28
+ "inputSchema": {
29
+ "type": "object",
30
+ "properties": {},
31
+ "required": []
32
+ },
33
+ "security": [
34
+ {
35
+ "apiToken": []
36
+ }
37
+ ],
38
+ "group": "agent-readiness"
39
+ },
40
+ {
41
+ "name": "agent-readiness_scans_run-website",
42
+ "title": "Run website scan",
43
+ "annotations": {
44
+ "title": "Run website scan",
45
+ "readOnlyHint": false,
46
+ "destructiveHint": false
47
+ },
48
+ "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.",
49
+ "method": "POST",
50
+ "path": "/api/agent-readiness/v1/scans",
51
+ "inputSchema": {
52
+ "type": "object",
53
+ "properties": {
54
+ "domain": {
55
+ "type": "string",
56
+ "description": "Domain name or full URL of the website to scan. Only the host is used."
57
+ }
58
+ },
59
+ "required": [
60
+ "domain"
61
+ ]
62
+ },
63
+ "security": [
64
+ {
65
+ "apiToken": []
66
+ }
67
+ ],
68
+ "group": "agent-readiness"
69
+ },
70
+ {
71
+ "name": "agent-readiness_scans_website",
72
+ "title": "Get website scan",
73
+ "annotations": {
74
+ "title": "Get website scan",
75
+ "readOnlyHint": true,
76
+ "destructiveHint": false
77
+ },
78
+ "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.",
79
+ "method": "GET",
80
+ "path": "/api/agent-readiness/v1/scans/{domain}",
81
+ "inputSchema": {
82
+ "type": "object",
83
+ "properties": {
84
+ "domain": {
85
+ "type": "string",
86
+ "description": "Domain name the scan was run for"
87
+ }
88
+ },
89
+ "required": [
90
+ "domain"
91
+ ]
92
+ },
93
+ "security": [
94
+ {
95
+ "apiToken": []
96
+ }
97
+ ],
98
+ "group": "agent-readiness"
99
+ }
100
+ ];
101
+ export default tools;
@@ -1931,6 +1931,89 @@ export default [
1931
1931
  ],
1932
1932
  "group": "agency-hosting"
1933
1933
  },
1934
+ {
1935
+ "name": "agent-readiness_checks_list",
1936
+ "title": "List checks",
1937
+ "annotations": {
1938
+ "title": "List checks",
1939
+ "readOnlyHint": true,
1940
+ "destructiveHint": false
1941
+ },
1942
+ "description": "List every check an agent readiness scan runs, with its name, category and weight.\\n\nUse it to show the human-readable name of each `check_id` in a scan's results.",
1943
+ "method": "GET",
1944
+ "path": "/api/agent-readiness/v1/checks",
1945
+ "inputSchema": {
1946
+ "type": "object",
1947
+ "properties": {},
1948
+ "required": []
1949
+ },
1950
+ "security": [
1951
+ {
1952
+ "apiToken": []
1953
+ }
1954
+ ],
1955
+ "group": "agent-readiness"
1956
+ },
1957
+ {
1958
+ "name": "agent-readiness_scans_run-website",
1959
+ "title": "Run website scan",
1960
+ "annotations": {
1961
+ "title": "Run website scan",
1962
+ "readOnlyHint": false,
1963
+ "destructiveHint": false
1964
+ },
1965
+ "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.",
1966
+ "method": "POST",
1967
+ "path": "/api/agent-readiness/v1/scans",
1968
+ "inputSchema": {
1969
+ "type": "object",
1970
+ "properties": {
1971
+ "domain": {
1972
+ "type": "string",
1973
+ "description": "Domain name or full URL of the website to scan. Only the host is used."
1974
+ }
1975
+ },
1976
+ "required": [
1977
+ "domain"
1978
+ ]
1979
+ },
1980
+ "security": [
1981
+ {
1982
+ "apiToken": []
1983
+ }
1984
+ ],
1985
+ "group": "agent-readiness"
1986
+ },
1987
+ {
1988
+ "name": "agent-readiness_scans_website",
1989
+ "title": "Get website scan",
1990
+ "annotations": {
1991
+ "title": "Get website scan",
1992
+ "readOnlyHint": true,
1993
+ "destructiveHint": false
1994
+ },
1995
+ "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.",
1996
+ "method": "GET",
1997
+ "path": "/api/agent-readiness/v1/scans/{domain}",
1998
+ "inputSchema": {
1999
+ "type": "object",
2000
+ "properties": {
2001
+ "domain": {
2002
+ "type": "string",
2003
+ "description": "Domain name the scan was run for"
2004
+ }
2005
+ },
2006
+ "required": [
2007
+ "domain"
2008
+ ]
2009
+ },
2010
+ "security": [
2011
+ {
2012
+ "apiToken": []
2013
+ }
2014
+ ],
2015
+ "group": "agent-readiness"
2016
+ },
1934
2017
  {
1935
2018
  "name": "billing_catalog_list",
1936
2019
  "title": "Get catalog item list",
@@ -1945,6 +1945,89 @@ const tools: OpenApiTool[] = [
1945
1945
  ],
1946
1946
  "group": "agency-hosting"
1947
1947
  },
1948
+ {
1949
+ "name": "agent-readiness_checks_list",
1950
+ "title": "List checks",
1951
+ "annotations": {
1952
+ "title": "List checks",
1953
+ "readOnlyHint": true,
1954
+ "destructiveHint": false
1955
+ },
1956
+ "description": "List every check an agent readiness scan runs, with its name, category and weight.\\n\nUse it to show the human-readable name of each `check_id` in a scan's results.",
1957
+ "method": "GET",
1958
+ "path": "/api/agent-readiness/v1/checks",
1959
+ "inputSchema": {
1960
+ "type": "object",
1961
+ "properties": {},
1962
+ "required": []
1963
+ },
1964
+ "security": [
1965
+ {
1966
+ "apiToken": []
1967
+ }
1968
+ ],
1969
+ "group": "agent-readiness"
1970
+ },
1971
+ {
1972
+ "name": "agent-readiness_scans_run-website",
1973
+ "title": "Run website scan",
1974
+ "annotations": {
1975
+ "title": "Run website scan",
1976
+ "readOnlyHint": false,
1977
+ "destructiveHint": false
1978
+ },
1979
+ "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.",
1980
+ "method": "POST",
1981
+ "path": "/api/agent-readiness/v1/scans",
1982
+ "inputSchema": {
1983
+ "type": "object",
1984
+ "properties": {
1985
+ "domain": {
1986
+ "type": "string",
1987
+ "description": "Domain name or full URL of the website to scan. Only the host is used."
1988
+ }
1989
+ },
1990
+ "required": [
1991
+ "domain"
1992
+ ]
1993
+ },
1994
+ "security": [
1995
+ {
1996
+ "apiToken": []
1997
+ }
1998
+ ],
1999
+ "group": "agent-readiness"
2000
+ },
2001
+ {
2002
+ "name": "agent-readiness_scans_website",
2003
+ "title": "Get website scan",
2004
+ "annotations": {
2005
+ "title": "Get website scan",
2006
+ "readOnlyHint": true,
2007
+ "destructiveHint": false
2008
+ },
2009
+ "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.",
2010
+ "method": "GET",
2011
+ "path": "/api/agent-readiness/v1/scans/{domain}",
2012
+ "inputSchema": {
2013
+ "type": "object",
2014
+ "properties": {
2015
+ "domain": {
2016
+ "type": "string",
2017
+ "description": "Domain name the scan was run for"
2018
+ }
2019
+ },
2020
+ "required": [
2021
+ "domain"
2022
+ ]
2023
+ },
2024
+ "security": [
2025
+ {
2026
+ "apiToken": []
2027
+ }
2028
+ ],
2029
+ "group": "agent-readiness"
2030
+ },
1948
2031
  {
1949
2032
  "name": "billing_catalog_list",
1950
2033
  "title": "Get catalog item list",
@@ -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.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.16.0', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.17.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.js';
6
6
 
7
- startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.16.0', tools, instructions });
7
+ startServer({ name: 'hostinger-agency-hosting-mcp', version: '2.17.0', tools, instructions });
@@ -0,0 +1,6 @@
1
+ #!/usr/bin/env node
2
+ // Auto-generated entry for group: agent-readiness
3
+ import { startServer } from '../core/runtime.js';
4
+ import tools from '../core/tools/agent-readiness.js';
5
+
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.17.0', tools });
@@ -0,0 +1,6 @@
1
+ #!/usr/bin/env node
2
+ // Auto-generated entry for group: agent-readiness
3
+ import { startServer } from '../core/runtime.js';
4
+ import tools from '../core/tools/agent-readiness.js';
5
+
6
+ startServer({ name: 'hostinger-agent-readiness-mcp', version: '2.17.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: '2.16.0', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '2.17.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: '2.16.0', tools, instructions, skills });
8
+ startServer({ name: 'hostinger-api-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-billing-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-dns-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-domains-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-ecommerce-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-horizons-mcp', version: '2.17.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: '2.16.0', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '2.17.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: '2.16.0', tools, instructions });
7
+ startServer({ name: 'hostinger-hosting-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-mail-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-reach-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-vps-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '2.17.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: '2.16.0', tools });
6
+ startServer({ name: 'hostinger-wordpress-mcp', version: '2.17.0', tools });
package/types.d.ts CHANGED
@@ -1067,6 +1067,55 @@ LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
1067
1067
  response: any; // Response structure will depend on the API
1068
1068
  };
1069
1069
 
1070
+ /**
1071
+ * List every check an agent readiness scan runs, with its name, category and weight.\n
1072
+ Use it to show the human-readable name of each `check_id` in a scan's results.
1073
+ */
1074
+ "agent-readiness_checks_list": {
1075
+ params: {
1076
+
1077
+ };
1078
+ response: any; // Response structure will depend on the API
1079
+ };
1080
+
1081
+ /**
1082
+ * Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
1083
+ Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`
1084
+ with no results yet. To get the results, poll the `Get website scan` operation with the same domain every
1085
+ few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
1086
+ plus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\n
1087
+ Starting a scan for a domain that already has a pending scan from the last 5 minutes
1088
+ returns that scan instead of starting a new one.
1089
+ */
1090
+ "agent-readiness_scans_run-website": {
1091
+ params: {
1092
+ /**
1093
+ * Domain name or full URL of the website to scan. Only the host is used.
1094
+ */
1095
+ domain: string;
1096
+ };
1097
+ response: any; // Response structure will depend on the API
1098
+ };
1099
+
1100
+ /**
1101
+ * Get the latest agent readiness scan of a website.\n
1102
+ Scans started with the `Run website scan` operation are asynchronous. While the status is `pending`,
1103
+ the result fields are null; wait a few seconds and call this operation again until the status is
1104
+ `completed` or `failed`. A `failed` scan is not retried; run the scan again.\n
1105
+ A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
1106
+ check with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\n
1107
+ Returns 404 when the domain has never been scanned; use the `Run website scan` operation first.
1108
+ */
1109
+ "agent-readiness_scans_website": {
1110
+ params: {
1111
+ /**
1112
+ * Domain name the scan was run for
1113
+ */
1114
+ domain: string;
1115
+ };
1116
+ response: any; // Response structure will depend on the API
1117
+ };
1118
+
1070
1119
  /**
1071
1120
  * Retrieve catalog items available for order.
1072
1121