hostinger-api-mcp 1.14.0 → 1.15.0

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.14.0', tools });
+startServer({ name: 'hostinger-billing-mcp', version: '1.15.0', tools });

package/src/servers/billing.ts

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

package/src/servers/dns.js

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

package/src/servers/dns.ts

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

package/src/servers/domains.js

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

package/src/servers/domains.ts

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

package/src/servers/ecommerce.js

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

package/src/servers/ecommerce.ts

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

package/src/servers/horizons.js

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

package/src/servers/horizons.ts

@@ -3,4 +3,4 @@
 import { startServer } from '../core/runtime.js';
 import tools from '../core/tools/horizons.js';
 
-startServer({ name: 'hostinger-horizons-mcp', version: '1.14.0', tools });
+startServer({ name: 'hostinger-horizons-mcp', version: '1.15.0', 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.14.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.15.0', 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.14.0', tools });
+startServer({ name: 'hostinger-hosting-mcp', version: '1.15.0', 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.14.0', tools });
+startServer({ name: 'hostinger-mail-mcp', version: '1.15.0', tools });

package/src/servers/mail.ts

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

package/src/servers/reach.js

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

package/src/servers/reach.ts

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

package/src/servers/vps.js

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

package/src/servers/vps.ts

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

package/src/servers/wordpress.js

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

package/src/servers/wordpress.ts

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

package/types.d.ts

@@ -677,6 +677,50 @@ Poll this endpoint after initiating async operations (SSL setup, backups, clonin
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation.
+   */
+  "agency-hosting_changeAgencyPlanWebsiteWordPressCoreVersionV1": {
+    params: {
+      /**
+       * Agency Plan website UID
+       */
+      website_uid: string;
+      /**
+       * Target WordPress core version to install. Must be one of the available versions.
+       */
+      version: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Returns the current WordPress settings for an Agency Plan website: installed core version,
+LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
+   */
+  "agency-hosting_getAgencyPlanWebsiteWordPressSettingsV1": {
+    params: {
+      /**
+       * Agency Plan website UID
+       */
+      website_uid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Lists the WordPress core versions available for installation on an Agency Plan website.
+   */
+  "agency-hosting_listAvailableWordPressVersionsForAnAgencyPlanWebsiteV1": {
+    params: {
+      /**
+       * Agency Plan website UID
+       */
+      website_uid: string;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve catalog items available for order.
 
@@ -2797,6 +2841,248 @@ complete. The response returns before the removal finishes.
     response: any; // Response structure will depend on the API
   };
 
+  /**
+   * Retrieve paginated access logs for the domain attached to the given
+mail order. Supports filtering by account, date range, protocol,
+status, and deletion flag. Results are sorted by timestamp descending.
+   */
+  "mail_listAccessLogsV1": {
+    params: {
+      /**
+       * Order resource ID
+       */
+      orderId: string;
+      /**
+       * Filter log entries by a specific email account
+       */
+      account?: string;
+      /**
+       * Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
+       */
+      date?: string;
+      /**
+       * Date range start (RFC 3339)
+       */
+      from_date?: string;
+      /**
+       * Date range end (RFC 3339)
+       */
+      to_date?: string;
+      /**
+       * Filter log entries by status
+       */
+      status?: string;
+      /**
+       * Filter access log entries by protocol
+       */
+      protocol?: string;
+      /**
+       * Filter access log entries by whether the session had deletions
+       */
+      has_deletions?: boolean;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve paginated account action logs (administrative and user
+actions) for the given mail order. Supports filtering by account,
+date range, and status. Results are sorted by timestamp descending.
+   */
+  "mail_listActionLogsV1": {
+    params: {
+      /**
+       * Order resource ID
+       */
+      orderId: string;
+      /**
+       * Filter log entries by a specific email account
+       */
+      account?: string;
+      /**
+       * Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
+       */
+      date?: string;
+      /**
+       * Date range start (RFC 3339)
+       */
+      from_date?: string;
+      /**
+       * Date range end (RFC 3339)
+       */
+      to_date?: string;
+      /**
+       * Filter log entries by status
+       */
+      status?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve paginated inbound (received mail) delivery logs for the
+domain attached to the given mail order. Supports filtering by
+account, date range, status, sender, and recipient. Results are
+sorted by timestamp descending.
+   */
+  "mail_listInboundLogsV1": {
+    params: {
+      /**
+       * Order resource ID
+       */
+      orderId: string;
+      /**
+       * Filter log entries by a specific email account
+       */
+      account?: string;
+      /**
+       * Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
+       */
+      date?: string;
+      /**
+       * Date range start (RFC 3339)
+       */
+      from_date?: string;
+      /**
+       * Date range end (RFC 3339)
+       */
+      to_date?: string;
+      /**
+       * Filter log entries by status
+       */
+      status?: string;
+      /**
+       * Filter log entries by sender. Accepts a full email address or a domain.
+       */
+      sender?: string;
+      /**
+       * Filter log entries by recipient. Accepts a full email address or a domain.
+       */
+      recipient?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve paginated mailbox action logs (message and mailbox events)
+for a mailbox in the given mail order. The mailbox email must belong
+to the order's domain. Supports date range and event type filters.
+Results are sorted by timestamp descending.
+   */
+  "mail_listMailboxActionLogsV1": {
+    params: {
+      /**
+       * Order resource ID
+       */
+      orderId: string;
+      /**
+       * Mailbox email address. Must belong to the order's domain.
+       */
+      email: string;
+      /**
+       * Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
+       */
+      date?: string;
+      /**
+       * Date range start (RFC 3339)
+       */
+      from_date?: string;
+      /**
+       * Date range end (RFC 3339)
+       */
+      to_date?: string;
+      /**
+       * Filter mailbox action log entries by event type
+       */
+      event?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
+  /**
+   * Retrieve paginated outbound (sent mail) delivery logs for the domain
+attached to the given mail order. Supports filtering by account, date
+range, status, sender, and recipient. Results are sorted by timestamp
+descending.
+   */
+  "mail_listOutboundLogsV1": {
+    params: {
+      /**
+       * Order resource ID
+       */
+      orderId: string;
+      /**
+       * Filter log entries by a specific email account
+       */
+      account?: string;
+      /**
+       * Exact date filter (YYYY-MM-DD). Takes precedence over `from_date`/`to_date` when both are given.
+       */
+      date?: string;
+      /**
+       * Date range start (RFC 3339)
+       */
+      from_date?: string;
+      /**
+       * Date range end (RFC 3339)
+       */
+      to_date?: string;
+      /**
+       * Filter log entries by status
+       */
+      status?: string;
+      /**
+       * Filter log entries by sender. Accepts a full email address or a domain.
+       */
+      sender?: string;
+      /**
+       * Filter log entries by recipient. Accepts a full email address or a domain.
+       */
+      recipient?: string;
+      /**
+       * Page number
+       */
+      page?: number;
+      /**
+       * Number of items per page
+       */
+      per_page?: number;
+    };
+    response: any; // Response structure will depend on the API
+  };
+
   /**
    * Retrieve a paginated list of mailboxes belonging to a mail order.
 
@@ -2804,7 +3090,7 @@ Use this endpoint to monitor mailboxes of your mail service, including
 their status, enabled protocols, attached resource counts, and
 periodically synced usage numbers (usage may lag behind live values).
    */
-  "mail_getMailboxListV1": {
+  "mail_listMailboxesV1": {
     params: {
       /**
        * Order resource ID
@@ -2889,7 +3175,7 @@ for a limited period before it is permanently removed.
 Use this endpoint to monitor your mail services, including their status,
 plan, attached domain, and expiration details.
    */
-  "mail_getMailOrderListV1": {
+  "mail_listOrdersV1": {
     params: {
       /**
        * Filter orders by domain name (exact match)