hostinger-api-mcp 1.45.5 → 1.46.1

package/src/core/tools/reach.js

@@ -1166,6 +1166,150 @@ export default [
     ],
     "group": "reach"
   },
+  {
+    "name": "reach_listSegmentFilterAttributesV1",
+    "description": "List every attribute a segment condition can filter on, with the operators each attribute\naccepts, the value format they expect and, where the value is constrained, the allowed\nvalues.\n\nThe list is profile specific: it includes the profile's custom contact fields, its tags and\nits 20 most recently published campaigns, so the valid attributes cannot be hardcoded. Read\nit before creating or updating a segment to discover the valid `attribute`, `operator` and\n`value` combinations.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/segmentation/filters/attributes",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
+  {
+    "name": "reach_previewContactsMatchingConditionsV1",
+    "description": "Preview the contacts matching a set of conditions without saving a segment.\n\nThe body is the same set of conditions accepted when creating or updating a segment, so this\nis how to check who a filter reaches, and how many, before persisting it. Nothing is stored\nand no contact is modified.\n\nCall the segment filter attributes endpoint first to discover the valid `attribute`,\n`operator` and `value` combinations.",
+    "method": "POST",
+    "path": "/api/reach/v1/profiles/{profileUuid}/segmentation/filters/contacts",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        },
+        "conditions": {
+          "type": "array",
+          "description": "Conditions a contact must satisfy to appear in the preview",
+          "items": {
+            "type": "object",
+            "description": "conditions parameter",
+            "properties": {
+              "attribute": {
+                "type": "string",
+                "description": "A built-in contact attribute, or `cf:{fieldUuid}` to target a custom\ncontact field. Which operators are accepted depends on the attribute,\nso read the segment filter attributes endpoint for the authoritative\nlist."
+              },
+              "operator": {
+                "type": "string",
+                "description": "operator parameter",
+                "enum": [
+                  "equals",
+                  "not_equals",
+                  "contains",
+                  "not_contains",
+                  "gte",
+                  "lte",
+                  "exists",
+                  "within_last_days",
+                  "not_within_last_days",
+                  "older_than_days",
+                  "processed",
+                  "not_processed",
+                  "delivered",
+                  "not_delivered",
+                  "dropped",
+                  "not_dropped",
+                  "bounced",
+                  "not_bounced",
+                  "soft_bounced",
+                  "not_soft_bounced",
+                  "opened",
+                  "not_opened",
+                  "clicked",
+                  "not_clicked",
+                  "unsubscribed",
+                  "not_unsubscribed"
+                ]
+              },
+              "value": {
+                "type": "string",
+                "description": "Always a string, including for numeric and date comparisons"
+              }
+            },
+            "required": [
+              "attribute",
+              "operator",
+              "value"
+            ]
+          }
+        },
+        "logic": {
+          "type": "string",
+          "description": "How to combine multiple conditions",
+          "enum": [
+            "AND",
+            "OR"
+          ]
+        },
+        "page": {
+          "type": "integer",
+          "description": "Page number"
+        },
+        "per_page": {
+          "type": "integer",
+          "description": "Number of items per page"
+        },
+        "search": {
+          "type": "string",
+          "description": "Narrow the preview to contacts whose email matches"
+        },
+        "sort_by": {
+          "type": "string",
+          "description": "sort_by parameter",
+          "enum": [
+            "email",
+            "name",
+            "surname",
+            "phone",
+            "subscription_status"
+          ]
+        },
+        "sort_direction": {
+          "type": "string",
+          "description": "sort_direction parameter",
+          "enum": [
+            "asc",
+            "desc"
+          ]
+        }
+      },
+      "required": [
+        "profileUuid",
+        "conditions",
+        "logic"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
   {
     "name": "reach_listProfileSegmentsV1",
     "description": "Get a paginated list of the segments defined in a profile.\n\nEach entry carries the number of contacts currently matching it, which is recalculated on\nread rather than stored. Use `count_type` to count either every matching contact or only\nthe subscribed ones.",
@@ -1728,6 +1872,54 @@ export default [
     ],
     "group": "reach"
   },
+  {
+    "name": "reach_getConnectedSendingDomainV1",
+    "description": "Get the sending domain connected to the profile, its verification status and any suspended\nsender addresses.\n\nCampaigns only go out once a domain is connected and active, so this is the cheapest way to\ncheck that precondition before building one. A profile with no domain connected returns the\nsame shape with every field set to `null`. For the individual MX, SPF, DKIM and DMARC records\nbehind the status, use the DNS status endpoint.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/domains",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
+  {
+    "name": "reach_listPlanFeatureAccessV1",
+    "description": "List which plan features the profile can use.\n\nThis is the feature lock matrix, not a usage quota. `available` means the feature can be\nused right now and `locked` means it is not part of the base plan, so an upgrade is needed.\nFor remaining emails, recipients and AI credits use the limits endpoint instead.\n\nWorth checking before building something that cannot be activated afterwards, such as an\nautomation on a plan without automation activation.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/features",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
   {
     "name": "reach_getRemainingPlanLimitsV1",
     "description": "Get how much of the plan is left for the current period.\n\nTwo things to keep in mind before you build alerting on this. The period is a calendar month\nrather than a billing anniversary, so the counters reset on the 1st no matter when the\nsubscription started. And usage is tracked per order, so every profile on the same order shares\none pool and reports the same numbers here. Only the current period is available, past usage is\nnot kept.",

package/src/core/tools/reach.ts

@@ -1180,6 +1180,150 @@ const tools: OpenApiTool[] = [
     ],
     "group": "reach"
   },
+  {
+    "name": "reach_listSegmentFilterAttributesV1",
+    "description": "List every attribute a segment condition can filter on, with the operators each attribute\naccepts, the value format they expect and, where the value is constrained, the allowed\nvalues.\n\nThe list is profile specific: it includes the profile's custom contact fields, its tags and\nits 20 most recently published campaigns, so the valid attributes cannot be hardcoded. Read\nit before creating or updating a segment to discover the valid `attribute`, `operator` and\n`value` combinations.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/segmentation/filters/attributes",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
+  {
+    "name": "reach_previewContactsMatchingConditionsV1",
+    "description": "Preview the contacts matching a set of conditions without saving a segment.\n\nThe body is the same set of conditions accepted when creating or updating a segment, so this\nis how to check who a filter reaches, and how many, before persisting it. Nothing is stored\nand no contact is modified.\n\nCall the segment filter attributes endpoint first to discover the valid `attribute`,\n`operator` and `value` combinations.",
+    "method": "POST",
+    "path": "/api/reach/v1/profiles/{profileUuid}/segmentation/filters/contacts",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        },
+        "conditions": {
+          "type": "array",
+          "description": "Conditions a contact must satisfy to appear in the preview",
+          "items": {
+            "type": "object",
+            "description": "conditions parameter",
+            "properties": {
+              "attribute": {
+                "type": "string",
+                "description": "A built-in contact attribute, or `cf:{fieldUuid}` to target a custom\ncontact field. Which operators are accepted depends on the attribute,\nso read the segment filter attributes endpoint for the authoritative\nlist."
+              },
+              "operator": {
+                "type": "string",
+                "description": "operator parameter",
+                "enum": [
+                  "equals",
+                  "not_equals",
+                  "contains",
+                  "not_contains",
+                  "gte",
+                  "lte",
+                  "exists",
+                  "within_last_days",
+                  "not_within_last_days",
+                  "older_than_days",
+                  "processed",
+                  "not_processed",
+                  "delivered",
+                  "not_delivered",
+                  "dropped",
+                  "not_dropped",
+                  "bounced",
+                  "not_bounced",
+                  "soft_bounced",
+                  "not_soft_bounced",
+                  "opened",
+                  "not_opened",
+                  "clicked",
+                  "not_clicked",
+                  "unsubscribed",
+                  "not_unsubscribed"
+                ]
+              },
+              "value": {
+                "type": "string",
+                "description": "Always a string, including for numeric and date comparisons"
+              }
+            },
+            "required": [
+              "attribute",
+              "operator",
+              "value"
+            ]
+          }
+        },
+        "logic": {
+          "type": "string",
+          "description": "How to combine multiple conditions",
+          "enum": [
+            "AND",
+            "OR"
+          ]
+        },
+        "page": {
+          "type": "integer",
+          "description": "Page number"
+        },
+        "per_page": {
+          "type": "integer",
+          "description": "Number of items per page"
+        },
+        "search": {
+          "type": "string",
+          "description": "Narrow the preview to contacts whose email matches"
+        },
+        "sort_by": {
+          "type": "string",
+          "description": "sort_by parameter",
+          "enum": [
+            "email",
+            "name",
+            "surname",
+            "phone",
+            "subscription_status"
+          ]
+        },
+        "sort_direction": {
+          "type": "string",
+          "description": "sort_direction parameter",
+          "enum": [
+            "asc",
+            "desc"
+          ]
+        }
+      },
+      "required": [
+        "profileUuid",
+        "conditions",
+        "logic"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
   {
     "name": "reach_listProfileSegmentsV1",
     "description": "Get a paginated list of the segments defined in a profile.\n\nEach entry carries the number of contacts currently matching it, which is recalculated on\nread rather than stored. Use `count_type` to count either every matching contact or only\nthe subscribed ones.",
@@ -1742,6 +1886,54 @@ const tools: OpenApiTool[] = [
     ],
     "group": "reach"
   },
+  {
+    "name": "reach_getConnectedSendingDomainV1",
+    "description": "Get the sending domain connected to the profile, its verification status and any suspended\nsender addresses.\n\nCampaigns only go out once a domain is connected and active, so this is the cheapest way to\ncheck that precondition before building one. A profile with no domain connected returns the\nsame shape with every field set to `null`. For the individual MX, SPF, DKIM and DMARC records\nbehind the status, use the DNS status endpoint.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/domains",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
+  {
+    "name": "reach_listPlanFeatureAccessV1",
+    "description": "List which plan features the profile can use.\n\nThis is the feature lock matrix, not a usage quota. `available` means the feature can be\nused right now and `locked` means it is not part of the base plan, so an upgrade is needed.\nFor remaining emails, recipients and AI credits use the limits endpoint instead.\n\nWorth checking before building something that cannot be activated afterwards, such as an\nautomation on a plan without automation activation.",
+    "method": "GET",
+    "path": "/api/reach/v1/profiles/{profileUuid}/features",
+    "inputSchema": {
+      "type": "object",
+      "properties": {
+        "profileUuid": {
+          "type": "string",
+          "description": "Profile uuid parameter"
+        }
+      },
+      "required": [
+        "profileUuid"
+      ]
+    },
+    "security": [
+      {
+        "apiToken": []
+      }
+    ],
+    "group": "reach"
+  },
   {
     "name": "reach_getRemainingPlanLimitsV1",
     "description": "Get how much of the plan is left for the current period.\n\nTwo things to keep in mind before you build alerting on this. The period is a calendar month\nrather than a billing anniversary, so the counters reset on the 1st no matter when the\nsubscription started. And usage is tracked per order, so every profile on the same order shares\none pool and reports the same numbers here. Only the current period is available, past usage is\nnot kept.",

package/src/servers/agency-hosting.js

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

package/src/servers/agency-hosting.ts

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

package/src/servers/all.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.46.1', tools });

package/src/servers/all.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/all.js';
 
-startServer({ name: 'hostinger-api-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-api-mcp', version: '1.46.1', tools });

package/src/servers/billing.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.46.1', tools });

package/src/servers/billing.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/billing.js';
 
-startServer({ name: 'hostinger-billing-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.46.1', tools });

package/src/servers/dns.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.46.1', tools });

package/src/servers/dns.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/dns.js';
 
-startServer({ name: 'hostinger-dns-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-dns-mcp', version: '1.46.1', tools });

package/src/servers/domains.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.46.1', tools });

package/src/servers/domains.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/domains.js';
 
-startServer({ name: 'hostinger-domains-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-domains-mcp', version: '1.46.1', tools });

package/src/servers/ecommerce.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.46.1', tools });

package/src/servers/ecommerce.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/ecommerce.js';
 
-startServer({ name: 'hostinger-ecommerce-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-ecommerce-mcp', version: '1.46.1', tools });

package/src/servers/horizons.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.46.1', tools });

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.46.1', tools });

package/src/servers/hosting.js

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

package/src/servers/hosting.ts

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

package/src/servers/mail.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.46.1', tools });

package/src/servers/mail.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/mail.js';
 
-startServer({ name: 'hostinger-mail-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.46.1', tools });

package/src/servers/reach.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.46.1', tools });

package/src/servers/reach.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/reach.js';
 
-startServer({ name: 'hostinger-reach-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-reach-mcp', version: '1.46.1', tools });

package/src/servers/vps.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.46.1', tools });

package/src/servers/vps.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/vps.js';
 
-startServer({ name: 'hostinger-vps-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-vps-mcp', version: '1.46.1', tools });

package/src/servers/wordpress.js

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.46.1', tools });

package/src/servers/wordpress.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/wordpress.js';
 
-startServer({ name: 'hostinger-wordpress-mcp', version: '1.45.5', tools });
+startServer({ name: 'hostinger-wordpress-mcp', version: '1.46.1', tools });