HOSTINGER-MCP

Managed Hostinger MCP rollout for domains, hosting, DNS, VPS, and deployment workflows.

Authentication

Header: Authorization
Format: Bearer mad_live_***
This service reference is generated from the active immutable Portal catalog.

Catalog Coverage

Raw provider tools: 130
Exposed compatibility tools: 130
Agent-ready tools: 123
Documented descriptors: 130
Public reference pages: 130
Source repository: https://github.com/MADPANDA3D/HOSTINGER-MCP
Catalog version: hostinger-2026.07.12.1
Catalog verified: 2026-07-12T10:07:51.087478+00:00 (5 days old)
Guide verified: not manually verified (not verified)
Committed snapshot: catalog-5ec40de147b11c40
Docs generated: 2026-07-18T00:19:58.776Z

Read-only Tools

Hostinger Billing Get Catalog Item List V1 — Use this tool when you need the Hostinger operation Get catalog item list. Retrieve catalog items available for order. Prices in catalog items is displayed as cents (without floating point), e.g: float 17.99 is displayed as integer 1799. Use this endpoint to view available services and pricing before placing orders. It calls GET /api/billing/v1/catalog against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: category (query, optional): Filter catalog items by category name (query, optional): Filter catalog items by name. Use * for wildcard search, e.g. .COM* to find .com domain The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_getCatalogItemListV1: Get catalog item list. Retrieve catalog items available for order. Prices in catalog items is displayed as cents (without floating point), e.g: float 17.99 is displayed as integer 1799. Use this endpoint to view available services and pricing before placing orders. Endpoint: GET /api/billing/v1/catalog. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Billing Get Payment Method List V1 — Use this tool when you need the Hostinger operation Get payment method list. Retrieve available payment methods that can be used for placing new orders. If you want to add new payment method, please use hPanel. Use this endpoint to view available payment options before creating orders. It calls GET /api/billing/v1/payment-methods against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_getPaymentMethodListV1: Get payment method list. Retrieve available payment methods that can be used for placing new orders. If you want to add new payment method, please use hPanel. Use this endpoint to view available payment options before creating orders. Endpoint: GET /api/billing/v1/payment-methods. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Billing Get Subscription List V1 — Use this tool when you need the Hostinger operation Get subscription list. Retrieve a list of all subscriptions associated with your account. Use this endpoint to monitor active services and billing status. It calls GET /api/billing/v1/subscriptions against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_getSubscriptionListV1: Get subscription list. Retrieve a list of all subscriptions associated with your account. Use this endpoint to monitor active services and billing status. Endpoint: GET /api/billing/v1/subscriptions. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Check Configuration — Use this tool to inspect whether Portal access and per-request Hostinger configuration are ready without returning credential values. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Check Portal and per-request Hostinger readiness without contacting Hostinger or returning credential values.
Hostinger DNS Get Dnsrecords V1 — Use this tool when you need the Hostinger operation Get DNS records. Retrieve DNS zone records for a specific domain. Use this endpoint to view current DNS configuration for domain management. It calls GET /api/dns/v1/zones/{domain} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_getDNSRecordsV1: Get DNS records. Retrieve DNS zone records for a specific domain. Use this endpoint to view current DNS configuration for domain management. Endpoint: GET /api/dns/v1/zones/{domain}. Path params: domain. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Get Dnssnapshot List V1 — Use this tool when you need the Hostinger operation Get DNS snapshot list. Retrieve DNS snapshots for a domain. Use this endpoint to view available DNS backup points for restoration. It calls GET /api/dns/v1/snapshots/{domain} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_getDNSSnapshotListV1: Get DNS snapshot list. Retrieve DNS snapshots for a domain. Use this endpoint to view available DNS backup points for restoration. Endpoint: GET /api/dns/v1/snapshots/{domain}. Path params: domain. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Get Dnssnapshot V1 — Use this tool when you need the Hostinger operation Get DNS snapshot. Retrieve particular DNS snapshot with contents of DNS zone records. Use this endpoint to view historical DNS configurations for domains. It calls GET /api/dns/v1/snapshots/{domain}/{snapshotId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name snapshotId (path, required): Snapshot ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_getDNSSnapshotV1: Get DNS snapshot. Retrieve particular DNS snapshot with contents of DNS zone records. Use this endpoint to view historical DNS configurations for domains. Endpoint: GET /api/dns/v1/snapshots/{domain}/{snapshotId}. Path params: domain, snapshotId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Validate Dnsrecords V1 — Use this tool when you need the Hostinger operation Validate DNS records. Validate DNS records prior to update for the selected domain. If the validation is successful, the response will contain 200 Success code. If there is validation error, the response will fail with 422 Validation error code. Use this endpoint to verify DNS record validity before applying changes. It calls POST /api/dns/v1/zones/{domain}/validate against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_validateDNSRecordsV1: Validate DNS records. Validate DNS records prior to update for the selected domain. If the validation is successful, the response will contain 200 Success code. If there is validation error, the response will fail with 422 Validation error code. Use this endpoint to verify DNS record validity before applying changes. Endpoint: POST /api/dns/v1/zones/{domain}/validate. Path params: domain. Request body: required/accepted. Risk class: read. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Check Domain Availability V1 — Use this tool when you need the Hostinger operation Check domain availability. Check availability of domain names across multiple TLDs. Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set with_alternatives to true. TLDs should be provided without leading dot (e.g. com, net, org). Endpoint has rate limit of 10 requests per minute. Use this endpoint to verify domain availability before purchase. It calls POST /api/domains/v1/availability against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_checkDomainAvailabilityV1: Check domain availability. Check availability of domain names across multiple TLDs. Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set with_alternatives to true. TLDs should be provided without leading dot (e.g. com, net, org). Endpoint has rate limit of 10 requests per minute. Use this endpoint to verify domain availability before purchase. Endpoint: POST /api/domains/v1/availability. Path params: none. Request body: required/accepted. Risk class: read. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Domain Details V1 — Use this tool when you need the Hostinger operation Get domain details. Retrieve detailed information for specified domain. Use this endpoint to view comprehensive domain configuration and status. It calls GET /api/domains/v1/portfolio/{domain} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getDomainDetailsV1: Get domain details. Retrieve detailed information for specified domain. Use this endpoint to view comprehensive domain configuration and status. Endpoint: GET /api/domains/v1/portfolio/{domain}. Path params: domain. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Domain Forwarding V1 — Use this tool when you need the Hostinger operation Get domain forwarding. Retrieve domain forwarding data. Use this endpoint to view current redirect configuration for domains. It calls GET /api/domains/v1/forwarding/{domain} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getDomainForwardingV1: Get domain forwarding. Retrieve domain forwarding data. Use this endpoint to view current redirect configuration for domains. Endpoint: GET /api/domains/v1/forwarding/{domain}. Path params: domain. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Domain List V1 — Use this tool when you need the Hostinger operation Get domain list. Retrieve all domains associated with your account. Use this endpoint to view user's domain portfolio. It calls GET /api/domains/v1/portfolio against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getDomainListV1: Get domain list. Retrieve all domains associated with your account. Use this endpoint to view user's domain portfolio. Endpoint: GET /api/domains/v1/portfolio. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Whoisprofile List V1 — Use this tool when you need the Hostinger operation Get WHOIS profile list. Retrieve WHOIS contact profiles. Use this endpoint to view available contact profiles for domain registration. It calls GET /api/domains/v1/whois against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: tld (query, optional): Filter by TLD (without leading dot) The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getWHOISProfileListV1: Get WHOIS profile list. Retrieve WHOIS contact profiles. Use this endpoint to view available contact profiles for domain registration. Endpoint: GET /api/domains/v1/whois. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Whoisprofile Usage V1 — Use this tool when you need the Hostinger operation Get WHOIS profile usage. Retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles. It calls GET /api/domains/v1/whois/{whoisId}/usage against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: whoisId (path, required): WHOIS ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getWHOISProfileUsageV1: Get WHOIS profile usage. Retrieve domain list where provided WHOIS contact profile is used. Use this endpoint to view which domains use specific contact profiles. Endpoint: GET /api/domains/v1/whois/{whoisId}/usage. Path params: whoisId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Get Whoisprofile V1 — Use this tool when you need the Hostinger operation Get WHOIS profile. Retrieve a WHOIS contact profile. Use this endpoint to view domain registration contact information. It calls GET /api/domains/v1/whois/{whoisId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: whoisId (path, required): WHOIS ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_getWHOISProfileV1: Get WHOIS profile. Retrieve a WHOIS contact profile. Use this endpoint to view domain registration contact information. Endpoint: GET /api/domains/v1/whois/{whoisId}. Path params: whoisId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Find Tools — Use this tool to rank Hostinger tools for a punctuation-normalized multi-token task without contacting Hostinger. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Rank Hostinger tools for a punctuation-normalized multi-token task with category, risk, and legacy filters.
Hostinger Get Endpoint Coverage — Use this tool to inspect the checked-in Hostinger OpenAPI coverage matrix with bounded tag, risk, and text filters. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Return a bounded section of the checked-in Hostinger OpenAPI endpoint coverage without contacting Hostinger.
Hostinger Get Tool Usage — Use this tool to retrieve one complete, lossless descriptor by native name, canonical name, or supported alias. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Return one complete lossless Hostinger ToolManifest descriptor by native name, canonical name, or alias.
Hostinger Hosting List Available Datacenters V1 — Use this tool when you need the Hostinger operation List available datacenters. Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements. It calls GET /api/hosting/v1/datacenters against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: order_id (query, required): Order ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_listAvailableDatacentersV1: List available datacenters. Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements. Endpoint: GET /api/hosting/v1/datacenters. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting List JS Deployments — Use this tool to list JavaScript application deployment runs for one Hostinger-hosted domain. It reads external Hostinger state without modifying it. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: List JavaScript application deployments for a Hostinger-hosted domain.
Hostinger Hosting List Orders V1 — Use this tool when you need the Hostinger operation List orders. Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you. Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results. It calls GET /api/hosting/v1/orders against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: page (query, optional): Page number per_page (query, optional): Number of items per page statuses (query, optional): Filter by order statuses order_ids (query, optional): Filter by specific order IDs The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_listOrdersV1: List orders. Retrieve a paginated list of orders accessible to the authenticated client. This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you. Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results. Endpoint: GET /api/hosting/v1/orders. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting List Websites V1 — Use this tool when you need the Hostinger operation List websites. Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you. Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results. It calls GET /api/hosting/v1/websites against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: page (query, optional): Page number per_page (query, optional): Number of items per page username (query, optional): Filter by specific username order_id (query, optional): Order ID is_enabled (query, optional): Filter by enabled status domain (query, optional): Filter by domain name (exact match) The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_listWebsitesV1: List websites. Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client. This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you. Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results. Endpoint: GET /api/hosting/v1/websites. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting Show JS Deployment Logs — Use this tool to read a bounded Hostinger JavaScript deployment log from a known build UUID. It reads external Hostinger state without modifying it. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Retrieve logs for a Hostinger JavaScript application deployment.
Hostinger Hostinger Check Configuration — Use this tool to use the legacy provider-authenticated configuration response retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Check Hostinger MCP portal/BYOK configuration without exposing secrets.
Hostinger Hostinger Find Tools — Use this tool to use the legacy provider-authenticated endpoint-only search retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Search Hostinger tool names, summaries, tags, methods, and paths.
Hostinger Hostinger Get Endpoint Coverage — Use this tool to use the legacy provider-authenticated endpoint coverage lookup retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Return the Hostinger OpenAPI endpoint coverage matrix or a filtered section.
Hostinger Hostinger Get Tool Usage — Use this tool to use the legacy provider-authenticated endpoint-tool reference retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Explain when and how to use a Hostinger tool, including risk gates.
Hostinger Hostinger List Capabilities — Use this tool to use the legacy provider-authenticated capability summary retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: List Hostinger MCP capability groups, tool counts, and common workflows.
Hostinger List Capabilities — Use this tool to inspect catalog counts, capability categories, risks, common workflows, and optionally the complete immutable ToolManifest. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: List Hostinger capability categories and ToolManifest counts; optionally include every complete descriptor for catalog publication.
Hostinger Mcp Health Check — Use this tool to read the legacy in-protocol runtime health summary retained for existing clients. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Basic Hostinger MCP health and config check without secret leakage.
Hostinger Reach Get Segment Details V1 — Use this tool when you need the Hostinger operation Get segment details. Get details of a specific segment. This endpoint retrieves information about a single segment identified by UUID. Segments are used to organize and group contacts based on specific criteria. It calls GET /api/reach/v1/segmentation/segments/{segmentUuid} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: segmentUuid (path, required): Segment uuid parameter The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_getSegmentDetailsV1: Get segment details. Get details of a specific segment. This endpoint retrieves information about a single segment identified by UUID. Segments are used to organize and group contacts based on specific criteria. Endpoint: GET /api/reach/v1/segmentation/segments/{segmentUuid}. Path params: segmentUuid. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach List Contact Groups V1 — Use this tool when you need the Hostinger operation List contact groups. Get a list of all contact groups. This endpoint returns a list of contact groups that can be used to organize contacts. It calls GET /api/reach/v1/contacts/groups against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_listContactGroupsV1: List contact groups. Get a list of all contact groups. This endpoint returns a list of contact groups that can be used to organize contacts. Endpoint: GET /api/reach/v1/contacts/groups. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach List Contacts V1 — Use this tool when you need the Hostinger operation List contacts. Get a list of contacts, optionally filtered by group and subscription status. This endpoint returns a paginated list of contacts with their basic information. You can filter contacts by group UUID and subscription status. It calls GET /api/reach/v1/contacts against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: group_uuid (query, optional): Filter contacts by group UUID subscription_status (query, optional): Filter contacts by subscription status page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_listContactsV1: List contacts. Get a list of contacts, optionally filtered by group and subscription status. This endpoint returns a paginated list of contacts with their basic information. You can filter contacts by group UUID and subscription status. Endpoint: GET /api/reach/v1/contacts. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach List Profiles V1 — Use this tool when you need the Hostinger operation List Profiles. This endpoint returns all profiles available to the client, including their basic information. It calls GET /api/reach/v1/profiles against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_listProfilesV1: List Profiles. This endpoint returns all profiles available to the client, including their basic information. Endpoint: GET /api/reach/v1/profiles. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach List Segment Contacts V1 — Use this tool when you need the Hostinger operation List segment contacts. Retrieve contacts associated with a specific segment. This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID. It calls GET /api/reach/v1/segmentation/segments/{segmentUuid}/contacts against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: segmentUuid (path, required): Segment uuid parameter page (query, optional): Page number per_page (query, optional): Number of items per page The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_listSegmentContactsV1: List segment contacts. Retrieve contacts associated with a specific segment. This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID. Endpoint: GET /api/reach/v1/segmentation/segments/{segmentUuid}/contacts. Path params: segmentUuid. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach List Segments V1 — Use this tool when you need the Hostinger operation List segments. Get a list of all contact segments. This endpoint returns a list of contact segments that can be used to organize contacts. It calls GET /api/reach/v1/segmentation/segments against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_listSegmentsV1: List segments. Get a list of all contact segments. This endpoint returns a list of contact segments that can be used to organize contacts. Endpoint: GET /api/reach/v1/segmentation/segments. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger V2 Get Domain Verifications Direct — Use this tool when you need the Hostinger operation Get domain verifications. Retrieve a list of pending and completed domain verifications. It calls GET /api/v2/direct/verifications/active against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation v2_getDomainVerificationsDIRECT: Get domain verifications. Retrieve a list of pending and completed domain verifications. Endpoint: GET /api/v2/direct/verifications/active. Path params: none. Request body: required/accepted. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Action Details V1 — Use this tool when you need the Hostinger operation Get action details. Retrieve detailed information about a specific action performed on a specified virtual machine. Use this endpoint to monitor specific VPS operation status and details. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID actionId (path, required): Action ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getActionDetailsV1: Get action details. Retrieve detailed information about a specific action performed on a specified virtual machine. Use this endpoint to monitor specific VPS operation status and details. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/actions/{actionId}. Path params: virtualMachineId, actionId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Actions V1 — Use this tool when you need the Hostinger operation Get actions. Retrieve actions performed on a specified virtual machine. Actions are operations or events that have been executed on the virtual machine, such as starting, stopping, or modifying the machine. This endpoint allows you to view the history of these actions, providing details about each action, such as the action name, timestamp, and status. Use this endpoint to view VPS operation history and troubleshoot issues. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/actions against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getActionsV1: Get actions. Retrieve actions performed on a specified virtual machine. Actions are operations or events that have been executed on the virtual machine, such as starting, stopping, or modifying the machine. This endpoint allows you to view the history of these actions, providing details about each action, such as the action name, timestamp, and status. Use this endpoint to view VPS operation history and troubleshoot issues. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/actions. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Attached Public Keys V1 — Use this tool when you need the Hostinger operation Get attached public keys. Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/public-keys against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getAttachedPublicKeysV1: Get attached public keys. Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/public-keys. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Backups V1 — Use this tool when you need the Hostinger operation Get backups. Retrieve backups for a specified virtual machine. Use this endpoint to view available backup points for VPS data recovery. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/backups against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getBackupsV1: Get backups. Retrieve backups for a specified virtual machine. Use this endpoint to view available backup points for VPS data recovery. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/backups. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Data Center List V1 — Use this tool when you need the Hostinger operation Get data center list. Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances. It calls GET /api/vps/v1/data-centers against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getDataCenterListV1: Get data center list. Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances. Endpoint: GET /api/vps/v1/data-centers. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Firewall Details V1 — Use this tool when you need the Hostinger operation Get firewall details. Retrieve firewall by its ID and rules associated with it. Use this endpoint to view specific firewall configuration and rules. It calls GET /api/vps/v1/firewall/{firewallId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: firewallId (path, required): Firewall ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getFirewallDetailsV1: Get firewall details. Retrieve firewall by its ID and rules associated with it. Use this endpoint to view specific firewall configuration and rules. Endpoint: GET /api/vps/v1/firewall/{firewallId}. Path params: firewallId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Firewall List V1 — Use this tool when you need the Hostinger operation Get firewall list. Retrieve all available firewalls. Use this endpoint to view existing firewall configurations. It calls GET /api/vps/v1/firewall against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getFirewallListV1: Get firewall list. Retrieve all available firewalls. Use this endpoint to view existing firewall configurations. Endpoint: GET /api/vps/v1/firewall. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Metrics V1 — Use this tool when you need the Hostinger operation Get metrics. Retrieve historical metrics for a specified virtual machine. It includes the following metrics: - CPU usage - Memory usage - Disk usage - Network usage - Uptime Use this endpoint to monitor VPS performance and resource utilization over time. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/metrics against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID date_from (query, required): Provider-defined value. date_to (query, required): Provider-defined value. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getMetricsV1: Get metrics. Retrieve historical metrics for a specified virtual machine. It includes the following metrics: - CPU usage - Memory usage - Disk usage - Network usage - Uptime Use this endpoint to monitor VPS performance and resource utilization over time. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/metrics. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Post Install Script V1 — Use this tool when you need the Hostinger operation Get post-install script. Retrieve post-install script by its ID. Use this endpoint to view specific automation script details. It calls GET /api/vps/v1/post-install-scripts/{postInstallScriptId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: postInstallScriptId (path, required): Post-install script ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getPostInstallScriptV1: Get post-install script. Retrieve post-install script by its ID. Use this endpoint to view specific automation script details. Endpoint: GET /api/vps/v1/post-install-scripts/{postInstallScriptId}. Path params: postInstallScriptId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Post Install Scripts V1 — Use this tool when you need the Hostinger operation Get post-install scripts. Retrieve post-install scripts associated with your account. Use this endpoint to view available automation scripts for VPS deployment. It calls GET /api/vps/v1/post-install-scripts against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getPostInstallScriptsV1: Get post-install scripts. Retrieve post-install scripts associated with your account. Use this endpoint to view available automation scripts for VPS deployment. Endpoint: GET /api/vps/v1/post-install-scripts. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Project Containers V1 — Use this tool when you need the Hostinger operation Get project containers. Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine. This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration. Use this to monitor the health and state of all services within your Docker Compose project. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/containers against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getProjectContainersV1: Get project containers. Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine. This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration. Use this to monitor the health and state of all services within your Docker Compose project. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/containers. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Project Contents V1 — Use this tool when you need the Hostinger operation Get project contents. Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status. This endpoint provides the full configuration and state details of a specific Docker Compose project. Use this to inspect project settings, review the compose file, or check the overall project health. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getProjectContentsV1: Get project contents. Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status. This endpoint provides the full configuration and state details of a specific Docker Compose project. Use this to inspect project settings, review the compose file, or check the overall project health. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Project List V1 — Use this tool when you need the Hostinger operation Get project list. Retrieves a list of all Docker Compose projects currently deployed on the virtual machine. This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitted in this endpoint. If you need to get detailed information about container with stats included, use the Get project containers endpoint. Use this to get an overview of all Docker projects on your VPS instance. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getProjectListV1: Get project list. Retrieves a list of all Docker Compose projects currently deployed on the virtual machine. This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitted in this endpoint. If you need to get detailed information about container with stats included, use the Get project containers endpoint. Use this to get an overview of all Docker projects on your VPS instance. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Project Logs V1 — Use this tool when you need the Hostinger operation Get project logs. Retrieves aggregated log entries from all services within a Docker Compose project. This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services. Use this for debugging, monitoring application behavior, and troubleshooting issues across your entire project stack. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/logs against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getProjectLogsV1: Get project logs. Retrieves aggregated log entries from all services within a Docker Compose project. This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services. Use this for debugging, monitoring application behavior, and troubleshooting issues across your entire project stack. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/logs. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Public Keys V1 — Use this tool when you need the Hostinger operation Get public keys. Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication. It calls GET /api/vps/v1/public-keys against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: page (query, optional): Page number The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getPublicKeysV1: Get public keys. Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication. Endpoint: GET /api/vps/v1/public-keys. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Scan Metrics V1 — Use this tool when you need the Hostinger operation Get scan metrics. Retrieve scan metrics for the Monarx malware scanner installed on a specified virtual machine. The scan metrics provide detailed information about malware scans performed by Monarx, including number of scans, detected threats, and other relevant statistics. This information is useful for monitoring security status of the virtual machine and assessing effectiveness of the malware scanner. Use this endpoint to monitor VPS security scan results and threat detection. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/monarx against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getScanMetricsV1: Get scan metrics. Retrieve scan metrics for the Monarx malware scanner installed on a specified virtual machine. The scan metrics provide detailed information about malware scans performed by Monarx, including number of scans, detected threats, and other relevant statistics. This information is useful for monitoring security status of the virtual machine and assessing effectiveness of the malware scanner. Use this endpoint to monitor VPS security scan results and threat detection. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/monarx. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Snapshot V1 — Use this tool when you need the Hostinger operation Get snapshot. Retrieve snapshot for a specified virtual machine. Use this endpoint to view current VPS snapshot information. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getSnapshotV1: Get snapshot. Retrieve snapshot for a specified virtual machine. Use this endpoint to view current VPS snapshot information. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Template Details V1 — Use this tool when you need the Hostinger operation Get template details. Retrieve detailed information about a specific OS template for virtual machines. Use this endpoint to view specific template specifications before deployment. It calls GET /api/vps/v1/templates/{templateId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: templateId (path, required): Template ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getTemplateDetailsV1: Get template details. Retrieve detailed information about a specific OS template for virtual machines. Use this endpoint to view specific template specifications before deployment. Endpoint: GET /api/vps/v1/templates/{templateId}. Path params: templateId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Templates V1 — Use this tool when you need the Hostinger operation Get templates. Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances. It calls GET /api/vps/v1/templates against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getTemplatesV1: Get templates. Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances. Endpoint: GET /api/vps/v1/templates. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Virtual Machine Details V1 — Use this tool when you need the Hostinger operation Get virtual machine details. Retrieve detailed information about a specified virtual machine. Use this endpoint to view comprehensive VPS configuration and status. It calls GET /api/vps/v1/virtual-machines/{virtualMachineId} against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getVirtualMachineDetailsV1: Get virtual machine details. Retrieve detailed information about a specified virtual machine. Use this endpoint to view comprehensive VPS configuration and status. Endpoint: GET /api/vps/v1/virtual-machines/{virtualMachineId}. Path params: virtualMachineId. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Get Virtual Machines V1 — Use this tool when you need the Hostinger operation Get virtual machines. Retrieve all available virtual machines. Use this endpoint to view available VPS instances. It calls GET /api/vps/v1/virtual-machines against the configured Hostinger account. This reads external Hostinger account state and does not modify it. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_getVirtualMachinesV1: Get virtual machines. Retrieve all available virtual machines. Use this endpoint to view available VPS instances. Endpoint: GET /api/vps/v1/virtual-machines. Path params: none. Request body: not expected. Risk class: read. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.

Write and Destructive Tools

Hostinger Billing Delete Payment Method V1 — Use this tool when you need the Hostinger operation Delete payment method. Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts. It calls DELETE /api/billing/v1/payment-methods/{paymentMethodId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: paymentMethodId (path, required): Payment method ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_deletePaymentMethodV1: Delete payment method. Delete a payment method from your account. Use this endpoint to remove unused payment methods from user accounts. Endpoint: DELETE /api/billing/v1/payment-methods/{paymentMethodId}. Path params: paymentMethodId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Billing Disable Auto Renewal V1 — Use this tool when you need the Hostinger operation Disable auto-renewal. Disable auto-renewal for a subscription. Use this endpoint when disable auto-renewal for a subscription. It calls DELETE /api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/disable against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: subscriptionId (path, required): Subscription ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_disableAutoRenewalV1: Disable auto-renewal. Disable auto-renewal for a subscription. Use this endpoint when disable auto-renewal for a subscription. Endpoint: DELETE /api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/disable. Path params: subscriptionId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Billing Enable Auto Renewal V1 — Use this tool when you need the Hostinger operation Enable auto-renewal. Enable auto-renewal for a subscription. Use this endpoint when enable auto-renewal for a subscription. It calls PATCH /api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: subscriptionId (path, required): Subscription ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_enableAutoRenewalV1: Enable auto-renewal. Enable auto-renewal for a subscription. Use this endpoint when enable auto-renewal for a subscription. Endpoint: PATCH /api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable. Path params: subscriptionId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Billing Set Default Payment Method V1 — Use this tool when you need the Hostinger operation Set default payment method. Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders. It calls POST /api/billing/v1/payment-methods/{paymentMethodId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: paymentMethodId (path, required): Payment method ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation billing_setDefaultPaymentMethodV1: Set default payment method. Set the default payment method for your account. Use this endpoint to configure the primary payment method for future orders. Endpoint: POST /api/billing/v1/payment-methods/{paymentMethodId}. Path params: paymentMethodId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Delete Dnsrecords V1 — Use this tool when you need the Hostinger operation Delete DNS records. Delete DNS records for the selected domain. To filter which records to delete, add the name of the record and type to the filter. Multiple filters can be provided with single request. If you have multiple records with the same name and type, and you want to delete only part of them, refer to the Update zone records endpoint. Use this endpoint to remove specific DNS records from domains. It calls DELETE /api/dns/v1/zones/{domain} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_deleteDNSRecordsV1: Delete DNS records. Delete DNS records for the selected domain. To filter which records to delete, add the name of the record and type to the filter. Multiple filters can be provided with single request. If you have multiple records with the same name and type, and you want to delete only part of them, refer to the Update zone records endpoint. Use this endpoint to remove specific DNS records from domains. Endpoint: DELETE /api/dns/v1/zones/{domain}. Path params: domain. Request body: required/accepted. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Reset Dnsrecords V1 — Use this tool when you need the Hostinger operation Reset DNS records. Reset DNS zone to the default records. Use this endpoint to restore domain DNS to original configuration. It calls POST /api/dns/v1/zones/{domain}/reset against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_resetDNSRecordsV1: Reset DNS records. Reset DNS zone to the default records. Use this endpoint to restore domain DNS to original configuration. Endpoint: POST /api/dns/v1/zones/{domain}/reset. Path params: domain. Request body: required/accepted. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Restore Dnssnapshot V1 — Use this tool when you need the Hostinger operation Restore DNS snapshot. Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration. It calls POST /api/dns/v1/snapshots/{domain}/{snapshotId}/restore against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name snapshotId (path, required): Snapshot ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_restoreDNSSnapshotV1: Restore DNS snapshot. Restore DNS zone to the selected snapshot. Use this endpoint to revert domain DNS to a previous configuration. Endpoint: POST /api/dns/v1/snapshots/{domain}/{snapshotId}/restore. Path params: domain, snapshotId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger DNS Update Dnsrecords V1 — Use this tool when you need the Hostinger operation Update DNS records. Update DNS records for the selected domain. Using overwrite = true will replace existing records with the provided ones. Otherwise existing records will be updated and new records will be added. Use this endpoint to modify domain DNS configuration. It calls PUT /api/dns/v1/zones/{domain} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation DNS_updateDNSRecordsV1: Update DNS records. Update DNS records for the selected domain. Using overwrite = true will replace existing records with the provided ones. Otherwise existing records will be updated and new records will be added. Use this endpoint to modify domain DNS configuration. Endpoint: PUT /api/dns/v1/zones/{domain}. Path params: domain. Request body: required/accepted. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Create Domain Forwarding V1 — Use this tool when you need the Hostinger operation Create domain forwarding. Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs. It calls POST /api/domains/v1/forwarding against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_createDomainForwardingV1: Create domain forwarding. Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs. Endpoint: POST /api/domains/v1/forwarding. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Create Whoisprofile V1 — Use this tool when you need the Hostinger operation Create WHOIS profile. Create WHOIS contact profile. Use this endpoint to add new contact information for domain registration. It calls POST /api/domains/v1/whois against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_createWHOISProfileV1: Create WHOIS profile. Create WHOIS contact profile. Use this endpoint to add new contact information for domain registration. Endpoint: POST /api/domains/v1/whois. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Delete Domain Forwarding V1 — Use this tool when you need the Hostinger operation Delete domain forwarding. Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains. It calls DELETE /api/domains/v1/forwarding/{domain} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_deleteDomainForwardingV1: Delete domain forwarding. Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains. Endpoint: DELETE /api/domains/v1/forwarding/{domain}. Path params: domain. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Delete Whoisprofile V1 — Use this tool when you need the Hostinger operation Delete WHOIS profile. Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account. It calls DELETE /api/domains/v1/whois/{whoisId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: whoisId (path, required): WHOIS ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_deleteWHOISProfileV1: Delete WHOIS profile. Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account. Endpoint: DELETE /api/domains/v1/whois/{whoisId}. Path params: whoisId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Disable Domain Lock V1 — Use this tool when you need the Hostinger operation Disable domain lock. Disable domain lock for the domain. Domain lock needs to be disabled before transferring the domain to another registrar. Use this endpoint to prepare domains for transfer to other registrars. It calls DELETE /api/domains/v1/portfolio/{domain}/domain-lock against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_disableDomainLockV1: Disable domain lock. Disable domain lock for the domain. Domain lock needs to be disabled before transferring the domain to another registrar. Use this endpoint to prepare domains for transfer to other registrars. Endpoint: DELETE /api/domains/v1/portfolio/{domain}/domain-lock. Path params: domain. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Disable Privacy Protection V1 — Use this tool when you need the Hostinger operation Disable privacy protection. Disable privacy protection for the domain. When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database. Use this endpoint to make domain owner's information publicly visible. It calls DELETE /api/domains/v1/portfolio/{domain}/privacy-protection against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_disablePrivacyProtectionV1: Disable privacy protection. Disable privacy protection for the domain. When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database. Use this endpoint to make domain owner's information publicly visible. Endpoint: DELETE /api/domains/v1/portfolio/{domain}/privacy-protection. Path params: domain. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Enable Domain Lock V1 — Use this tool when you need the Hostinger operation Enable domain lock. Enable domain lock for the domain. When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock. Use this endpoint to secure domains against unauthorized transfers. It calls PUT /api/domains/v1/portfolio/{domain}/domain-lock against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_enableDomainLockV1: Enable domain lock. Enable domain lock for the domain. When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock. Use this endpoint to secure domains against unauthorized transfers. Endpoint: PUT /api/domains/v1/portfolio/{domain}/domain-lock. Path params: domain. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Enable Privacy Protection V1 — Use this tool when you need the Hostinger operation Enable privacy protection. Enable privacy protection for the domain. When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database. Use this endpoint to protect domain owner's personal information from public view. It calls PUT /api/domains/v1/portfolio/{domain}/privacy-protection against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_enablePrivacyProtectionV1: Enable privacy protection. Enable privacy protection for the domain. When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database. Use this endpoint to protect domain owner's personal information from public view. Endpoint: PUT /api/domains/v1/portfolio/{domain}/privacy-protection. Path params: domain. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Purchase New Domain V1 — Use this tool when you need the Hostinger operation Purchase new domain. Purchase and register a new domain name. If registration fails, login to hPanel and check domain registration status. If no payment method is provided, your default payment method will be used automatically. If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Some TLDs require additional_details to be provided and these will be validated before completing purchase. Use this endpoint to register new domains for users. It calls POST /api/domains/v1/portfolio against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_purchaseNewDomainV1: Purchase new domain. Purchase and register a new domain name. If registration fails, login to hPanel and check domain registration status. If no payment method is provided, your default payment method will be used automatically. If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account. Some TLDs require additional_details to be provided and these will be validated before completing purchase. Use this endpoint to register new domains for users. Endpoint: POST /api/domains/v1/portfolio. Path params: none. Request body: required/accepted. Risk class: spend. This spend tool requires confirm=true and confirmation_phrase='I understand this may charge my Hostinger account'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Domains Update Domain Nameservers V1 — Use this tool when you need the Hostinger operation Update domain nameservers. Set nameservers for a specified domain. Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable. Use this endpoint to configure custom DNS hosting for domains. It calls PUT /api/domains/v1/portfolio/{domain}/nameservers against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: domain (path, required): Domain name The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation domains_updateDomainNameserversV1: Update domain nameservers. Set nameservers for a specified domain. Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable. Use this endpoint to configure custom DNS hosting for domains. Endpoint: PUT /api/domains/v1/portfolio/{domain}/nameservers. Path params: domain. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting Create Website V1 — Use this tool when you need the Hostinger operation Create website. Create a new website for the authenticated client. Provide the domain name and associated order ID to create a new website. The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter. Subsequent websites will be hosted on the same datacenter automatically. Website creation takes up to a few minutes to complete. Check the websites list endpoint to see when your new website becomes available. It calls POST /api/hosting/v1/websites against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_createWebsiteV1: Create website. Create a new website for the authenticated client. Provide the domain name and associated order ID to create a new website. The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter. Subsequent websites will be hosted on the same datacenter automatically. Website creation takes up to a few minutes to complete. Check the websites list endpoint to see when your new website becomes available. Endpoint: POST /api/hosting/v1/websites. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting Deploy JS Application — Use this tool to upload JavaScript application source and start a Hostinger server build. It changes or overwrites external website state and requires explicit confirmation after preview. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Deploy a JavaScript application source archive to Hostinger and trigger a server build.
Hostinger Hosting Deploy Static Website — Use this tool to upload and deploy a local static-site archive, overwriting hosted website files. It changes or overwrites external website state and requires explicit confirmation after preview. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Deploy a pre-built static website archive to Hostinger hosting.
Hostinger Hosting Deploy Wordpress Plugin — Use this tool to upload a local WordPress plugin directory and deploy it to a hosted website. It changes or overwrites external website state and requires explicit confirmation after preview. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Upload a WordPress plugin directory and trigger plugin deployment.
Hostinger Hosting Deploy Wordpress Theme — Use this tool to upload a local WordPress theme directory and optionally activate it. It changes or overwrites external website state and requires explicit confirmation after preview. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Upload a WordPress theme directory and optionally activate it.
Hostinger Hosting Generate Afree Subdomain V1 — Use this tool when you need the Hostinger operation Generate a free subdomain. Generate a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately and you can always connect a custom domain to your site later. It calls POST /api/hosting/v1/domains/free-subdomains against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_generateAFreeSubdomainV1: Generate a free subdomain. Generate a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately and you can always connect a custom domain to your site later. Endpoint: POST /api/hosting/v1/domains/free-subdomains. Path params: none. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hosting Import Wordpress Website — Use this tool to upload a WordPress archive and SQL dump and replace website state through import. It changes or overwrites external website state and requires explicit confirmation after preview. It contacts Hostinger using the protected per-request credential and never accepts credentials as tool arguments. Use dry_run when offered to validate local paths and request shape before provider work. Do not use this tool for a different Hostinger account or for content whose local files are unavailable to this container. The result is the compact Hostinger MCP envelope with the affected domain, stable provider identifiers when available, safe status metadata, and a recoverable error without secret values. Runtime summary: Upload a WordPress archive and SQL dump, then trigger Hostinger WordPress import.
Hostinger Hosting Verify Domain Ownership V1 — Use this tool when you need the Hostinger operation Verify domain ownership. Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have is_accessible: true. If not, add the given TXT record to your domain's DNS records and try verifying again. Keep in mind that it may take up to 10 minutes for new TXT DNS records to propagate. Skip this verification when using Hostinger's free subdomains (.hostingersite.com). It calls POST /api/hosting/v1/domains/verify-ownership against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation hosting_verifyDomainOwnershipV1: Verify domain ownership. Verify ownership of a single domain and return the verification status. Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have is_accessible: true. If not, add the given TXT record to your domain's DNS records and try verifying again. Keep in mind that it may take up to 10 minutes for new TXT DNS records to propagate. Skip this verification when using Hostinger's free subdomains (.hostingersite.com). Endpoint: POST /api/hosting/v1/domains/verify-ownership. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Hostinger Raw Request — Use this tool to call an allowlisted Hostinger API path that is not yet represented by a typed endpoint tool. It is part of the Hostinger MCP agent contract. It never returns Portal grants, Hostinger API tokens, request headers, or raw credential values. Prefer the typed endpoint tools for provider work and use the five unprefixed navigation tools for new discovery flows. The result is a compact Hostinger MCP envelope designed for the next agent action. Runtime summary: Allowlisted raw Hostinger API request for newly released endpoints not yet in the generated manifest. Requires the same BYOK auth and write/destructive risk gates.
Hostinger Reach Create Anew Contact Segment V1 — Use this tool when you need the Hostinger operation Create a new contact segment. Create a new contact segment. This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc. It calls POST /api/reach/v1/segmentation/segments against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_createANewContactSegmentV1: Create a new contact segment. Create a new contact segment. This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc. Endpoint: POST /api/reach/v1/segmentation/segments. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach Create Anew Contact V1 — Use this tool when you need the Hostinger operation Create a new contact. Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. It calls POST /api/reach/v1/contacts against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_createANewContactV1: Create a new contact. Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. Endpoint: POST /api/reach/v1/contacts. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach Create New Contacts V1 — Use this tool when you need the Hostinger operation Create new contacts. Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. It calls POST /api/reach/v1/profiles/{profileUuid}/contacts against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: profileUuid (path, required): Profile uuid parameter The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_createNewContactsV1: Create new contacts. Create a new contact in the email marketing system. This endpoint allows you to create a new contact with basic information like name, email, and surname. If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent. Endpoint: POST /api/reach/v1/profiles/{profileUuid}/contacts. Path params: profileUuid. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger Reach Delete Acontact V1 — Use this tool when you need the Hostinger operation Delete a contact. Delete a contact with the specified UUID. This endpoint permanently removes a contact from the email marketing system. It calls DELETE /api/reach/v1/contacts/{uuid} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: uuid (path, required): UUID of the contact to delete The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation reach_deleteAContactV1: Delete a contact. Delete a contact with the specified UUID. This endpoint permanently removes a contact from the email marketing system. Endpoint: DELETE /api/reach/v1/contacts/{uuid}. Path params: uuid. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Activate Firewall V1 — Use this tool when you need the Hostinger operation Activate firewall. Activate a firewall for a specified virtual machine. Only one firewall can be active for a virtual machine at a time. Use this endpoint to apply firewall rules to VPS instances. It calls POST /api/vps/v1/firewall/{firewallId}/activate/{virtualMachineId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: firewallId (path, required): Firewall ID virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_activateFirewallV1: Activate firewall. Activate a firewall for a specified virtual machine. Only one firewall can be active for a virtual machine at a time. Use this endpoint to apply firewall rules to VPS instances. Endpoint: POST /api/vps/v1/firewall/{firewallId}/activate/{virtualMachineId}. Path params: firewallId, virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Attach Public Key V1 — Use this tool when you need the Hostinger operation Attach public key. Attach existing public keys from your account to a specified virtual machine. Multiple keys can be attached to a single virtual machine. Use this endpoint to enable SSH key authentication for VPS instances. It calls POST /api/vps/v1/public-keys/attach/{virtualMachineId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_attachPublicKeyV1: Attach public key. Attach existing public keys from your account to a specified virtual machine. Multiple keys can be attached to a single virtual machine. Use this endpoint to enable SSH key authentication for VPS instances. Endpoint: POST /api/vps/v1/public-keys/attach/{virtualMachineId}. Path params: virtualMachineId. Request body: required/accepted. Risk class: credential. This credential tool requires confirm=true and confirmation_phrase='I understand this changes Hostinger credentials or access'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create Firewall Rule V1 — Use this tool when you need the Hostinger operation Create firewall rule. Create new firewall rule for a specified firewall. By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to add new security rules to firewalls. It calls POST /api/vps/v1/firewall/{firewallId}/rules against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: firewallId (path, required): Firewall ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createFirewallRuleV1: Create firewall rule. Create new firewall rule for a specified firewall. By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to add new security rules to firewalls. Endpoint: POST /api/vps/v1/firewall/{firewallId}/rules. Path params: firewallId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create New Firewall V1 — Use this tool when you need the Hostinger operation Create new firewall. Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security. It calls POST /api/vps/v1/firewall against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createNewFirewallV1: Create new firewall. Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security. Endpoint: POST /api/vps/v1/firewall. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create New Project V1 — Use this tool when you need the Hostinger operation Create new project. Deploy new project from docker-compose.yaml contents or download contents from URL. URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents. If project with the same name already exists, existing project will be replaced. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createNewProjectV1: Create new project. Deploy new project from docker-compose.yaml contents or download contents from URL. URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents. If project with the same name already exists, existing project will be replaced. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker. Path params: virtualMachineId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create Post Install Script V1 — Use this tool when you need the Hostinger operation Create post-install script. Add a new post-install script to your account, which can then be used after virtual machine installation. The script contents will be saved to the file /post_install with executable attribute set and will be executed once virtual machine is installed. The output of the script will be redirected to /post_install.log. Maximum script size is 48KB. Use this endpoint to create automation scripts for VPS setup tasks. It calls POST /api/vps/v1/post-install-scripts against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createPostInstallScriptV1: Create post-install script. Add a new post-install script to your account, which can then be used after virtual machine installation. The script contents will be saved to the file /post_install with executable attribute set and will be executed once virtual machine is installed. The output of the script will be redirected to /post_install.log. Maximum script size is 48KB. Use this endpoint to create automation scripts for VPS setup tasks. Endpoint: POST /api/vps/v1/post-install-scripts. Path params: none. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create Ptrrecord V1 — Use this tool when you need the Hostinger operation Create PTR record. Create or update a PTR (Pointer) record for a specified virtual machine. Use this endpoint to configure reverse DNS lookup for VPS IP addresses. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID ipAddressId (path, required): IP Address ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createPTRRecordV1: Create PTR record. Create or update a PTR (Pointer) record for a specified virtual machine. Use this endpoint to configure reverse DNS lookup for VPS IP addresses. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId}. Path params: virtualMachineId, ipAddressId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create Public Key V1 — Use this tool when you need the Hostinger operation Create public key. Add a new public key to your account. Use this endpoint to register SSH keys for VPS authentication. It calls POST /api/vps/v1/public-keys against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createPublicKeyV1: Create public key. Add a new public key to your account. Use this endpoint to register SSH keys for VPS authentication. Endpoint: POST /api/vps/v1/public-keys. Path params: none. Request body: required/accepted. Risk class: credential. This credential tool requires confirm=true and confirmation_phrase='I understand this changes Hostinger credentials or access'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Create Snapshot V1 — Use this tool when you need the Hostinger operation Create snapshot. Create a snapshot of a specified virtual machine. A snapshot captures the state and data of the virtual machine at a specific point in time, allowing users to restore the virtual machine to that state if needed. This operation is useful for backup purposes, system recovery, and testing changes without affecting the current state of the virtual machine. Creating new snapshot will overwrite the existing snapshot! Use this endpoint to capture VPS state for backup and recovery purposes. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_createSnapshotV1: Create snapshot. Create a snapshot of a specified virtual machine. A snapshot captures the state and data of the virtual machine at a specific point in time, allowing users to restore the virtual machine to that state if needed. This operation is useful for backup purposes, system recovery, and testing changes without affecting the current state of the virtual machine. Creating new snapshot will overwrite the existing snapshot! Use this endpoint to capture VPS state for backup and recovery purposes. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot. Path params: virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Deactivate Firewall V1 — Use this tool when you need the Hostinger operation Deactivate firewall. Deactivate a firewall for a specified virtual machine. Use this endpoint to remove firewall protection from VPS instances. It calls POST /api/vps/v1/firewall/{firewallId}/deactivate/{virtualMachineId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: firewallId (path, required): Firewall ID virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deactivateFirewallV1: Deactivate firewall. Deactivate a firewall for a specified virtual machine. Use this endpoint to remove firewall protection from VPS instances. Endpoint: POST /api/vps/v1/firewall/{firewallId}/deactivate/{virtualMachineId}. Path params: firewallId, virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Firewall Rule V1 — Use this tool when you need the Hostinger operation Delete firewall rule. Delete a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to remove specific firewall rules. It calls DELETE /api/vps/v1/firewall/{firewallId}/rules/{ruleId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: firewallId (path, required): Firewall ID ruleId (path, required): Firewall Rule ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deleteFirewallRuleV1: Delete firewall rule. Delete a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to remove specific firewall rules. Endpoint: DELETE /api/vps/v1/firewall/{firewallId}/rules/{ruleId}. Path params: firewallId, ruleId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Firewall V1 — Use this tool when you need the Hostinger operation Delete firewall. Delete a specified firewall. Any virtual machine that has this firewall activated will automatically have it deactivated. Use this endpoint to remove unused firewall configurations. It calls DELETE /api/vps/v1/firewall/{firewallId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: firewallId (path, required): Firewall ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deleteFirewallV1: Delete firewall. Delete a specified firewall. Any virtual machine that has this firewall activated will automatically have it deactivated. Use this endpoint to remove unused firewall configurations. Endpoint: DELETE /api/vps/v1/firewall/{firewallId}. Path params: firewallId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Post Install Script V1 — Use this tool when you need the Hostinger operation Delete post-install script. Delete a post-install script from your account. Use this endpoint to remove unused automation scripts. It calls DELETE /api/vps/v1/post-install-scripts/{postInstallScriptId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: postInstallScriptId (path, required): Post-install script ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deletePostInstallScriptV1: Delete post-install script. Delete a post-install script from your account. Use this endpoint to remove unused automation scripts. Endpoint: DELETE /api/vps/v1/post-install-scripts/{postInstallScriptId}. Path params: postInstallScriptId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Project V1 — Use this tool when you need the Hostinger operation Delete project. Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images. This operation is irreversible and will delete all project data. Use this when you want to permanently remove a project and free up system resources. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/down against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deleteProjectV1: Delete project. Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images. This operation is irreversible and will delete all project data. Use this when you want to permanently remove a project and free up system resources. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/down. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Ptrrecord V1 — Use this tool when you need the Hostinger operation Delete PTR record. Delete a PTR (Pointer) record for a specified virtual machine. Once deleted, reverse DNS lookups to the virtual machine's IP address will no longer return the previously configured hostname. Use this endpoint to remove reverse DNS configuration from VPS instances. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID ipAddressId (path, required): IP Address ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deletePTRRecordV1: Delete PTR record. Delete a PTR (Pointer) record for a specified virtual machine. Once deleted, reverse DNS lookups to the virtual machine's IP address will no longer return the previously configured hostname. Use this endpoint to remove reverse DNS configuration from VPS instances. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/ptr/{ipAddressId}. Path params: virtualMachineId, ipAddressId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Public Key V1 — Use this tool when you need the Hostinger operation Delete public key. Delete a public key from your account. Deleting public key from account does not remove it from virtual machine Use this endpoint to remove unused SSH keys from account. It calls DELETE /api/vps/v1/public-keys/{publicKeyId} against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: publicKeyId (path, required): Public Key ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deletePublicKeyV1: Delete public key. Delete a public key from your account. Deleting public key from account does not remove it from virtual machine Use this endpoint to remove unused SSH keys from account. Endpoint: DELETE /api/vps/v1/public-keys/{publicKeyId}. Path params: publicKeyId. Request body: not expected. Risk class: credential. This credential tool requires confirm=true and confirmation_phrase='I understand this changes Hostinger credentials or access'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Delete Snapshot V1 — Use this tool when you need the Hostinger operation Delete snapshot. Delete a snapshot of a specified virtual machine. Use this endpoint to remove VPS snapshots. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_deleteSnapshotV1: Delete snapshot. Delete a snapshot of a specified virtual machine. Use this endpoint to remove VPS snapshots. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot. Path params: virtualMachineId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Install Monarx V1 — Use this tool when you need the Hostinger operation Install Monarx. Install the Monarx malware scanner on a specified virtual machine. Monarx is a security tool designed to detect and prevent malware infections on virtual machines. By installing Monarx, users can enhance the security of their virtual machines, ensuring that they are protected against malicious software. Use this endpoint to enable malware protection on VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/monarx against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_installMonarxV1: Install Monarx. Install the Monarx malware scanner on a specified virtual machine. Monarx is a security tool designed to detect and prevent malware infections on virtual machines. By installing Monarx, users can enhance the security of their virtual machines, ensuring that they are protected against malicious software. Use this endpoint to enable malware protection on VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/monarx. Path params: virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Purchase New Virtual Machine V1 — Use this tool when you need the Hostinger operation Purchase new virtual machine. Purchase and setup a new virtual machine. If virtual machine setup fails for any reason, login to hPanel and complete the setup manually. If no payment method is provided, your default payment method will be used automatically. Use this endpoint to create new VPS instances. It calls POST /api/vps/v1/virtual-machines against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: This operation has no path or query parameters. The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_purchaseNewVirtualMachineV1: Purchase new virtual machine. Purchase and setup a new virtual machine. If virtual machine setup fails for any reason, login to hPanel and complete the setup manually. If no payment method is provided, your default payment method will be used automatically. Use this endpoint to create new VPS instances. Endpoint: POST /api/vps/v1/virtual-machines. Path params: none. Request body: required/accepted. Risk class: spend. This spend tool requires confirm=true and confirmation_phrase='I understand this may charge my Hostinger account'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Recreate Virtual Machine V1 — Use this tool when you need the Hostinger operation Recreate virtual machine. Recreate a virtual machine from scratch. The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted. ## Password Requirements Password will be checked against leaked password databases. Requirements for the password are: - At least 12 characters long - At least one uppercase letter - At least one lowercase letter - At least one number - Is not leaked publicly This operation is irreversible and will result in the loss of all data stored on the virtual machine! Use this endpoint to completely rebuild VPS instances with fresh OS installation. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/recreate against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_recreateVirtualMachineV1: Recreate virtual machine. Recreate a virtual machine from scratch. The recreation process involves reinstalling the operating system and resetting the virtual machine to its initial state. Snapshots, if there are any, will be deleted. ## Password Requirements Password will be checked against leaked password databases. Requirements for the password are: - At least 12 characters long - At least one uppercase letter - At least one lowercase letter - At least one number - Is not leaked publicly This operation is irreversible and will result in the loss of all data stored on the virtual machine! Use this endpoint to completely rebuild VPS instances with fresh OS installation. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/recreate. Path params: virtualMachineId. Request body: required/accepted. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Reset Hostname V1 — Use this tool when you need the Hostinger operation Reset hostname. Reset hostname and PTR record of a specified virtual machine to default value. Use this endpoint to restore default hostname configuration for VPS instances. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/hostname against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_resetHostnameV1: Reset hostname. Reset hostname and PTR record of a specified virtual machine to default value. Use this endpoint to restore default hostname configuration for VPS instances. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/hostname. Path params: virtualMachineId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Restart Project V1 — Use this tool when you need the Hostinger operation Restart project. Restarts all services in a Docker Compose project by stopping and starting containers in the correct dependency order. This operation preserves data volumes and network configurations while refreshing the running containers. Use this to apply configuration changes or recover from service failures. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/restart against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_restartProjectV1: Restart project. Restarts all services in a Docker Compose project by stopping and starting containers in the correct dependency order. This operation preserves data volumes and network configurations while refreshing the running containers. Use this to apply configuration changes or recover from service failures. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/restart. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Restart Virtual Machine V1 — Use this tool when you need the Hostinger operation Restart virtual machine. Restart a specified virtual machine by fully stopping and starting it. If the virtual machine was stopped, it will be started. Use this endpoint to reboot VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/restart against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_restartVirtualMachineV1: Restart virtual machine. Restart a specified virtual machine by fully stopping and starting it. If the virtual machine was stopped, it will be started. Use this endpoint to reboot VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/restart. Path params: virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Restore Backup V1 — Use this tool when you need the Hostinger operation Restore backup. Restore a backup for a specified virtual machine. The system will then initiate the restore process, which may take some time depending on the size of the backup. All data on the virtual machine will be overwritten with the data from the backup. Use this endpoint to recover VPS data from backup points. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/backups/{backupId}/restore against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID backupId (path, required): Backup ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_restoreBackupV1: Restore backup. Restore a backup for a specified virtual machine. The system will then initiate the restore process, which may take some time depending on the size of the backup. All data on the virtual machine will be overwritten with the data from the backup. Use this endpoint to recover VPS data from backup points. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/backups/{backupId}/restore. Path params: virtualMachineId, backupId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Restore Snapshot V1 — Use this tool when you need the Hostinger operation Restore snapshot. Restore a specified virtual machine to a previous state using a snapshot. Restoring from a snapshot allows users to revert the virtual machine to that state, which is useful for system recovery, undoing changes, or testing. Use this endpoint to revert VPS instances to previous saved states. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot/restore against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_restoreSnapshotV1: Restore snapshot. Restore a specified virtual machine to a previous state using a snapshot. Restoring from a snapshot allows users to revert the virtual machine to that state, which is useful for system recovery, undoing changes, or testing. Use this endpoint to revert VPS instances to previous saved states. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/snapshot/restore. Path params: virtualMachineId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Set Hostname V1 — Use this tool when you need the Hostinger operation Set hostname. Set hostname for a specified virtual machine. Changing hostname does not update PTR record automatically. If you want your virtual machine to be reachable by a hostname, you need to point your domain A/AAAA records to virtual machine IP as well. Use this endpoint to configure custom hostnames for VPS instances. It calls PUT /api/vps/v1/virtual-machines/{virtualMachineId}/hostname against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_setHostnameV1: Set hostname. Set hostname for a specified virtual machine. Changing hostname does not update PTR record automatically. If you want your virtual machine to be reachable by a hostname, you need to point your domain A/AAAA records to virtual machine IP as well. Use this endpoint to configure custom hostnames for VPS instances. Endpoint: PUT /api/vps/v1/virtual-machines/{virtualMachineId}/hostname. Path params: virtualMachineId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Set Nameservers V1 — Use this tool when you need the Hostinger operation Set nameservers. Set nameservers for a specified virtual machine. Be aware, that improper nameserver configuration can lead to the virtual machine being unable to resolve domain names. Use this endpoint to configure custom DNS resolvers for VPS instances. It calls PUT /api/vps/v1/virtual-machines/{virtualMachineId}/nameservers against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_setNameserversV1: Set nameservers. Set nameservers for a specified virtual machine. Be aware, that improper nameserver configuration can lead to the virtual machine being unable to resolve domain names. Use this endpoint to configure custom DNS resolvers for VPS instances. Endpoint: PUT /api/vps/v1/virtual-machines/{virtualMachineId}/nameservers. Path params: virtualMachineId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Set Panel Password V1 — Use this tool when you need the Hostinger operation Set panel password. Set panel password for a specified virtual machine. If virtual machine does not use panel OS, the request will still be processed without any effect. Requirements for password are same as in the recreate virtual machine endpoint. Use this endpoint to configure control panel access credentials for VPS instances. It calls PUT /api/vps/v1/virtual-machines/{virtualMachineId}/panel-password against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_setPanelPasswordV1: Set panel password. Set panel password for a specified virtual machine. If virtual machine does not use panel OS, the request will still be processed without any effect. Requirements for password are same as in the recreate virtual machine endpoint. Use this endpoint to configure control panel access credentials for VPS instances. Endpoint: PUT /api/vps/v1/virtual-machines/{virtualMachineId}/panel-password. Path params: virtualMachineId. Request body: required/accepted. Risk class: credential. This credential tool requires confirm=true and confirmation_phrase='I understand this changes Hostinger credentials or access'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Set Root Password V1 — Use this tool when you need the Hostinger operation Set root password. Set root password for a specified virtual machine. Requirements for password are same as in the recreate virtual machine endpoint. Use this endpoint to update administrator credentials for VPS instances. It calls PUT /api/vps/v1/virtual-machines/{virtualMachineId}/root-password against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_setRootPasswordV1: Set root password. Set root password for a specified virtual machine. Requirements for password are same as in the recreate virtual machine endpoint. Use this endpoint to update administrator credentials for VPS instances. Endpoint: PUT /api/vps/v1/virtual-machines/{virtualMachineId}/root-password. Path params: virtualMachineId. Request body: required/accepted. Risk class: credential. This credential tool requires confirm=true and confirmation_phrase='I understand this changes Hostinger credentials or access'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Setup Purchased Virtual Machine V1 — Use this tool when you need the Hostinger operation Setup purchased virtual machine. Setup newly purchased virtual machine with initial state. Use this endpoint to configure and initialize purchased VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/setup against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_setupPurchasedVirtualMachineV1: Setup purchased virtual machine. Setup newly purchased virtual machine with initial state. Use this endpoint to configure and initialize purchased VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/setup. Path params: virtualMachineId. Request body: required/accepted. Risk class: spend. This spend tool requires confirm=true and confirmation_phrase='I understand this may charge my Hostinger account'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Start Project V1 — Use this tool when you need the Hostinger operation Start project. Starts all services in a Docker Compose project that are currently stopped. This operation brings up containers in the correct dependency order as defined in the compose file. Use this to resume a project that was previously stopped or to start services after a system reboot. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/start against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_startProjectV1: Start project. Starts all services in a Docker Compose project that are currently stopped. This operation brings up containers in the correct dependency order as defined in the compose file. Use this to resume a project that was previously stopped or to start services after a system reboot. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/start. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Start Recovery Mode V1 — Use this tool when you need the Hostinger operation Start recovery mode. Initiate recovery mode for a specified virtual machine. Recovery mode is a special state that allows users to perform system rescue operations, such as repairing file systems, recovering data, or troubleshooting issues that prevent the virtual machine from booting normally. Virtual machine will boot recovery disk image and original disk image will be mounted in /mnt directory. Use this endpoint to enable system rescue operations on VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/recovery against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_startRecoveryModeV1: Start recovery mode. Initiate recovery mode for a specified virtual machine. Recovery mode is a special state that allows users to perform system rescue operations, such as repairing file systems, recovering data, or troubleshooting issues that prevent the virtual machine from booting normally. Virtual machine will boot recovery disk image and original disk image will be mounted in /mnt directory. Use this endpoint to enable system rescue operations on VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/recovery. Path params: virtualMachineId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Start Virtual Machine V1 — Use this tool when you need the Hostinger operation Start virtual machine. Start a specified virtual machine. If the virtual machine is already running, the request will still be processed without any effect. Use this endpoint to power on stopped VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/start against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_startVirtualMachineV1: Start virtual machine. Start a specified virtual machine. If the virtual machine is already running, the request will still be processed without any effect. Use this endpoint to power on stopped VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/start. Path params: virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Stop Project V1 — Use this tool when you need the Hostinger operation Stop project. Stops all running services in a Docker Compose project while preserving container configurations and data volumes. This operation gracefully shuts down containers in reverse dependency order. Use this to temporarily halt a project without removing data or configurations. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/stop against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_stopProjectV1: Stop project. Stops all running services in a Docker Compose project while preserving container configurations and data volumes. This operation gracefully shuts down containers in reverse dependency order. Use this to temporarily halt a project without removing data or configurations. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/stop. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Stop Recovery Mode V1 — Use this tool when you need the Hostinger operation Stop recovery mode. Stop recovery mode for a specified virtual machine. If virtual machine is not in recovery mode, this operation will fail. Use this endpoint to exit system rescue mode and return VPS to normal operation. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/recovery against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_stopRecoveryModeV1: Stop recovery mode. Stop recovery mode for a specified virtual machine. If virtual machine is not in recovery mode, this operation will fail. Use this endpoint to exit system rescue mode and return VPS to normal operation. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/recovery. Path params: virtualMachineId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Stop Virtual Machine V1 — Use this tool when you need the Hostinger operation Stop virtual machine. Stop a specified virtual machine. If the virtual machine is already stopped, the request will still be processed without any effect. Use this endpoint to power off running VPS instances. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/stop against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_stopVirtualMachineV1: Stop virtual machine. Stop a specified virtual machine. If the virtual machine is already stopped, the request will still be processed without any effect. Use this endpoint to power off running VPS instances. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/stop. Path params: virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Sync Firewall V1 — Use this tool when you need the Hostinger operation Sync firewall. Sync a firewall for a specified virtual machine. Firewall can lose sync with virtual machine if the firewall has new rules added, removed or updated. Use this endpoint to apply updated firewall rules to VPS instances. It calls POST /api/vps/v1/firewall/{firewallId}/sync/{virtualMachineId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: firewallId (path, required): Firewall ID virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_syncFirewallV1: Sync firewall. Sync a firewall for a specified virtual machine. Firewall can lose sync with virtual machine if the firewall has new rules added, removed or updated. Use this endpoint to apply updated firewall rules to VPS instances. Endpoint: POST /api/vps/v1/firewall/{firewallId}/sync/{virtualMachineId}. Path params: firewallId, virtualMachineId. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Uninstall Monarx V1 — Use this tool when you need the Hostinger operation Uninstall Monarx. Uninstall the Monarx malware scanner on a specified virtual machine. If Monarx is not installed, the request will still be processed without any effect. Use this endpoint to remove malware scanner from VPS instances. It calls DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/monarx against the configured Hostinger account. This can delete, overwrite, change credentials, or spend money and requires both the declared confirmation controls and a Portal destructive preview. Provider parameters: virtualMachineId (path, required): Virtual Machine ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_uninstallMonarxV1: Uninstall Monarx. Uninstall the Monarx malware scanner on a specified virtual machine. If Monarx is not installed, the request will still be processed without any effect. Use this endpoint to remove malware scanner from VPS instances. Endpoint: DELETE /api/vps/v1/virtual-machines/{virtualMachineId}/monarx. Path params: virtualMachineId. Request body: not expected. Risk class: destructive. This destructive tool requires confirm=true and confirmation_phrase='I understand this may delete or overwrite Hostinger resources'. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Update Firewall Rule V1 — Use this tool when you need the Hostinger operation Update firewall rule. Update a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to modify existing firewall rules. It calls PUT /api/vps/v1/firewall/{firewallId}/rules/{ruleId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: firewallId (path, required): Firewall ID ruleId (path, required): Firewall Rule ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_updateFirewallRuleV1: Update firewall rule. Update a specific firewall rule from a specified firewall. Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually. Use this endpoint to modify existing firewall rules. Endpoint: PUT /api/vps/v1/firewall/{firewallId}/rules/{ruleId}. Path params: firewallId, ruleId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Update Post Install Script V1 — Use this tool when you need the Hostinger operation Update post-install script. Update a specific post-install script. Use this endpoint to modify existing automation scripts. It calls PUT /api/vps/v1/post-install-scripts/{postInstallScriptId} against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: postInstallScriptId (path, required): Post-install script ID The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_updatePostInstallScriptV1: Update post-install script. Update a specific post-install script. Use this endpoint to modify existing automation scripts. Endpoint: PUT /api/vps/v1/post-install-scripts/{postInstallScriptId}. Path params: postInstallScriptId. Request body: required/accepted. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.
Hostinger VPS Update Project V1 — Use this tool when you need the Hostinger operation Update project. Updates a Docker Compose project by pulling the latest image versions and recreating containers with new configurations. This operation preserves data volumes while applying changes from the compose file. Use this to deploy application updates, apply configuration changes, or refresh container images to their latest versions. It calls POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/update against the configured Hostinger account. This changes external Hostinger state and requires confirm=true. Provider parameters: virtualMachineId (path, required): Virtual Machine ID projectName (path, required): Docker Compose project name using alphanumeric characters, dashes, and underscores only The body follows the complete Hostinger schema in inputSchema. Do not place API tokens in arguments; credentials arrive only through protected Portal headers. The result is the normalized Hostinger MCP envelope with data, safe error details, HTTP/rate metadata, and pagination metadata when available. Runtime summary: Use this when you need Hostinger API operation VPS_updateProjectV1: Update project. Updates a Docker Compose project by pulling the latest image versions and recreating containers with new configurations. This operation preserves data volumes while applying changes from the compose file. Use this to deploy application updates, apply configuration changes, or refresh container images to their latest versions. Endpoint: POST /api/vps/v1/virtual-machines/{virtualMachineId}/docker/{projectName}/update. Path params: virtualMachineId, projectName. Request body: not expected. Risk class: write. This write tool requires confirm=true. Returns the compact MAD envelope {ok,data,error,meta}; set dry_run=true to preview without calling Hostinger.

Authentication​

Catalog Coverage​

Read-only Tools​

Write and Destructive Tools​

Authentication

Catalog Coverage

Read-only Tools

Write and Destructive Tools