Skip to content
Back to search

api-mcp-server

Model Context Protocol (MCP) server for Hostinger API.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/hostinger/api-mcp-server with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/hostinger/api-mcp-server'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hostinger--api-mcp-server/badge.svg)](/listings/hostinger--api-mcp-server)

HTML

<a href="/listings/hostinger--api-mcp-server"><img src="/api/listings/hostinger--api-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server:

https://mcp.hostinger.com

Claude Code

claude mcp add --transport http hostinger https://mcp.hostinger.com

This opens a browser window to authorize via OAuth. Once approved, the operations below are reachable through `execute` in your session.

Other MCP-compatible clients

Add `https://mcp.hostinger.com` as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears. Refer to your client's docs for how it exposes "add remote MCP server" / "custom connector" settings.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 4,905 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # hostinger-api-mcp
  2. Model Context Protocol (MCP) server for Hostinger API.
  3. ## Quick start: Hosted remote server
  4. If you don't want to install or run anything locally, connect directly to Hostinger's hosted MCP server:
  5. ```
  6. https://mcp.hostinger.com
  7. ```
  8. ### Claude Code
  9. ```bash
  10. claude mcp add --transport http hostinger https://mcp.hostinger.com
  11. ```
  12. This opens a browser window to authorize via OAuth. Once approved, the operations below are reachable through `execute` in your session.
  13. ### Codex
  14. ```bash
  15. codex mcp add hostinger --url https://mcp.hostinger.com
  16. codex mcp login hostinger
  17. ```
  18. `login` opens the same OAuth flow in your browser.
  19. ### Other MCP-compatible clients
  20. Add `https://mcp.hostinger.com` as a remote Streamable HTTP MCP server in your client's configuration and complete the OAuth prompt when it appears. Refer to your client's docs for how it exposes "add remote MCP server" / "custom connector" settings.
  21. ## Prerequisites
  22. - Node.js version 24 or higher
  23. If you don't have Node.js installed, you can download it from the [official website](https://nodejs.org/en/download/).
  24. Alternatively, you can use a package manager like [Homebrew](https://brew.sh/) (for macOS) or [Chocolatey](https://chocolatey.org/) (for Windows) to install Node.js.
  25. We recommend using [NVM (Node Version Manager)](https://github.com/nvm-sh/nvm) to install and manage installed Node.js versions.
  26. After installing NVM, you can install Node.js with the following command:
  27. ```bash
  28. nvm install v24
  29. nvm use v24
  30. ```
  31. ## Installation
  32. To install the MCP server, run one of the following command, depending on your package manager:
  33. ```bash
  34. # Install globally from npm
  35. npm install -g @hostinger/mcp
  36. # Or with yarn
  37. yarn global add @hostinger/mcp
  38. # Or with pnpm
  39. pnpm add -g @hostinger/mcp
  40. ```
  41. ## Update
  42. To update the MCP server to the latest version, use one of the following commands, depending on your package manager:
  43. ```bash
  44. # Update globally from npm
  45. npm update -g @hostinger/mcp
  46. # Or with yarn
  47. yarn global upgrade @hostinger/mcp
  48. # Or with pnpm
  49. pnpm update -g @hostinger/mcp
  50. ```
  51. ## Binaries
  52. This package installs the following MCP server commands:
  53. - `hostinger-api-mcp` — unified server over every operation (424 total)
  54. - `hostinger-agency-hosting-mcp` — 43 operations for agency-hosting
  55. - `hostinger-agent-readiness-mcp` — 4 operations for agent-readiness
  56. - `hostinger-billing-mcp` — 10 operations for billing
  57. - `hostinger-dns-mcp` — 9 operations for dns
  58. - `hostinger-domains-mcp` — 43 operations for domains
  59. - `hostinger-ecommerce-mcp` — 30 operations for ecommerce
  60. - `hostinger-gpu-mcp` — 13 operations for gpu
  61. - `hostinger-horizons-mcp` — 7 operations for horizons
  62. - `hostinger-hosting-mcp` — 59 operations for hosting
  63. - `hostinger-mail-mcp` — 39 operations for mail
  64. - `hostinger-reach-mcp` — 73 operations for reach
  65. - `hostinger-vps-mcp` — 68 operations for vps
  66. - `hostinger-wordpress-mcp` — 41 operations for wordpress
  67. Every binary exposes the same three tools; a scoped binary only searches and executes its own group's operations. `hostinger-api-mcp` remains the backwards-compatible default.
  68. ## Configuration
  69. The following environment variables can be configured when running the server:
  70. - `DEBUG`: Enable debug logging (true/false) (default: false)
  71. - `HOSTINGER_API_TOKEN`: Your API token, which will be sent in the `Authorization` header. When set, OAuth is bypassed entirely.
  72. - `API_TOKEN`: Deprecated alias for `HOSTINGER_API_TOKEN`. Will be removed in a future version — prefer `HOSTINGER_API_TOKEN`.
  73. - `OAUTH_ISSUER`: OAuth server base URL (default: `https://auth.hostinger.com`). Only used when `HOSTINGER_API_TOKEN` is not set.
  74. ## Authentication
  75. The server supports two authentication methods:
  76. ### API Token (recommended for CI/scripts)
  77. Set `HOSTINGER_API_TOKEN` in the environment (the MCP client's `env` block). When present it always takes precedence — no OAuth code runs.
  78. ### OAuth 2.0 with PKCE (interactive sign-in)
  79. When `HOSTINGER_API_TOKEN` is not set and the server runs in stdio mode, OAuth 2.0 with PKCE is used automatically on the first authenticated tool call:
  80. 1. A dynamic OAuth client is registered with the issuer (RFC 7591) — once per machine.
  81. 2. A browser window opens to the authorization page.
  82. 3. After sign-in, the server captures the redirect on a local ephemeral port, exchanges the code for tokens, and stores them.
  83. 4. Subsequent calls reuse the stored access token; expired tokens are refreshed automatically. If a refresh token is revoked, the browser flow is re-launched.
  84. Credentials are stored at:
  85. - macOS / Linux: `~/.config/hostinger-mcp/credentials.json` (mode 0600)
  86. - Windows: `%APPDATA%\hostinger-mcp\credentials.json`
  87. Credentials are shared across all Hostinger MCP binaries (`hostinger-api-mcp`, `hostinger-vps-mcp`, etc.).
  88. **Manual commands:**
  89. ```bash
  90. # Run the OAuth sign-in flow immediately (don't wait for the first tool call)
  91. hostinger-api-mcp --login
  92. # Revoke stored credentials
  93. hostinger-api-mcp --logout
  94. ```
  95. **HTTP transport note:** OAuth sign-in is not supported in `--http` mode. Set `HOSTINGER_API_TOKEN` before using `--http`.
  96. ## Usage
  97. ### JSON configuration for Claude, Cursor, etc.
  98. Register Node and the server script by absolute path, never `npx` or a bare `node`/`hostinger-api-mcp`: tools start the server in your project, where `npx` puts the project's `node_modules/.bin` first on `PATH`, a version manager (asdf, mise) runs whatever Node the project's `.tool-versions` names, and Windows looks a bare name up in the project folder first. Any of these lets a cloned repository run its own code with your Hostinger credentials. After the global install, `node -p process.execPath` prints the Node path and `npm root -g` the folder that holds `@hostinger/mcp`. Run both from your home folder.
  99. ```json
  100. {
  101. "mcpServers": {
  102. "hostinger-api": {
  103. "command": "/absolute/path/to/node",
  104. "args": ["/absolute/path/to/global/node_modules/@hostinger/mcp/src/servers/all.js"],
  105. "env": {
  106. "DEBUG": "false",
  107. "HOSTINGER_API_TOKEN": "YOUR API TOKEN"
  108. }
  109. }
  110. }
  111. }
  112. ```
  113. ### Transport Options
  114. The MCP server supports two transport modes:
  115. #### Standard I/O Transport
  116. The server can use standard input / output (stdio) transport (default). This provides local streaming:
  117. #### Streamable HTTP Transport
  118. The server can use HTTP streaming transport. This provides bidirectional streaming over HTTP:
  119. ```bash
  120. # Default HTTP transport on localhost:8100
  121. hostinger-api-mcp --http
  122. # Specify custom host and port
  123. hostinger-api-mcp --http --host 0.0.0.0 --port 8150
  124. ```
  125. #### Command Line Options
  126. ```
  127. Options:
  128. --http Use HTTP streaming transport (requires HOSTINGER_API_TOKEN env var)
  129. --stdio Use Server-Sent Events transport (default)
  130. --host {host} Hostname or IP address to listen on (default: 127.0.0.1)
  131. --port {port} Port to bind to (default: 8100)
  132. --login Run OAuth sign-in flow and exit
  133. --logout Revoke stored OAuth credentials and exit
  134. --help Show help message
  135. ```
  136. ### Using as an MCP Tool Provider
  137. This server implements the Model Context Protocol (MCP) and can be used with any MCP-compatible consumer.
  138. Example of connecting to this server using HTTP streaming transport:
  139. ```javascript
  140. import { Client } from "@modelcontextprotocol/sdk/client/index.js";
  141. import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
  142. // Create HTTP transport
  143. const transport = new StreamableHTTPClientTransport({
  144. url: "http://localhost:8100/",
  145. headers: {
  146. "Authorization": `Bearer ${process.env.HOSTINGER_API_TOKEN}`
  147. }
  148. });
  149. // Connect to the MCP server
  150. const client = new Client({
  151. name: "my-client",
  152. version: "1.0.0"
  153. }, {
  154. capabilities: {}
  155. });
  156. await client.connect(transport);
  157. // List available tools
  158. const { tools } = await client.listTools();
  159. console.log("Available tools:", tools);
  160. // Execute an operation
  161. const result = await client.callTool({
  162. name: "execute",
  163. arguments: { operation: "billing_catalog_list", params: { category: "DOMAIN" } }
  164. });
  165. console.log("Tool result:", result);
  166. ```
  167. ## Tools
  168. Every server exposes three tools:
  169. - `search` — find operations by keyword; returns each match with its `inputSchema`.
  170. - `execute` — run one operation: `{ "operation": "<name>", "params": { ... } }`.
  171. - `multi-execute` — run up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
  172. ## Operations
  173. The operations `search` offers, by binary:
  174. Operations that newer tools replace are hidden from `search`, and not documented, in every binary that also offers the replacing tool. Some keep working through `execute` until they are removed. Others only run inside the tool that replaced them: `execute` refuses them and names that tool.
  175. ### `hostinger-agency-hosting-mcp`
  176. #### changelog_list-entries
  177. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  178. - **Method**: `custom`
  179. - **Path**: `custom`
  180. #### agency-hosting_deploy-node-static-website
  181. Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites of type node-static (a Node.js-built static site that requires a build step or a plain simple static site). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the build-assets process which builds the site and deploys the result to public_html. This operation is synchronous: the build and deployment complete before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For plain PHP applications that should be extracted as-is, use agency-hosting_deploy-php-application instead. The website UID is automatically resolved from the domain.
  182. - **Method**: `custom`
  183. - **Path**: `custom`
  184. #### agency-hosting_deploy-php-application
  185. Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website's existing contents and cannot be undone — always confirm with the user before proceeding. Use this for Agency Plan websites where the archive contents should be extracted and served as-is with no build step (e.g., PHP applications). The tool resolves the website from its domain, uploads the archive to the website's file browser over TUS, and triggers the import-archive process which overwrites the website contents with the archive contents. This operation is synchronous: the archive is extracted and deployed before the tool returns, so the website is live as soon as the tool finishes successfully — there is no separate asynchronous build to wait for or poll. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the archive yourself, this tool does it end-to-end. For node-static websites that require a build step, use agency-hosting_deploy-node-static-website instead. The website UID is automatically resolved from the domain.
  186. - **Method**: `custom`
  187. - **Path**: `custom`
  188. #### agency-hosting_datacenters_list
  189. Lists the datacenters available for provisioning a new website on the given Agency Plan
  190. hosting order.
  191. Each datacenter includes a `pinger_url` you can ping from the client to measure round-trip
  192. latency; comparing the results across datacenters lets you pick the nearest one (lowest
  193. ping) before choosing its `code` as the `datacenter_code` when creating a website setup.
  194. - **Method**: `GET`
  195. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/datacenters`
  196. #### agency-hosting_domains_change-website
  197. Changes the primary domain for an Agency Plan website.
  198. Provide the current domain in the path and the new domain in the request body.
  199. Set domain to null to revert to the temporary domain.
  200. - **Method**: `PUT`
  201. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{from_domain}`
  202. #### agency-hosting_domains_link-to-website
  203. Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
  204. - **Method**: `POST`
  205. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains`
  206. #### agency-hosting_domains_list
  207. Returns a paginated list of domains associated with Agency Plan websites accessible to the authenticated client.
  208. Use the website_uuids filter to narrow results to specific websites.
  209. - **Method**: `GET`
  210. - **Path**: `/api/agency-hosting/v1/domains`
  211. #### agency-hosting_domains_unlink-from-website
  212. Unlinks a domain from the specified Agency Plan website.
  213. The website stops serving traffic on this domain immediately.
  214. Website files and database are preserved, and any other linked domains remain accessible.
  215. If this is the only domain on the website, unlinking leaves the website without an accessible domain.
  216. - **Method**: `DELETE`
  217. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}`
  218. #### agency-hosting_files_generate-upload-url
  219. Generate a file browser upload URL with authentication credentials for uploading files
  220. to an Agency Plan website's file storage.
  221. Returns `url`, `auth_key` and `rest_auth_key`. Use these to upload a file to the
  222. website's file storage via the TUS resumable upload protocol (TUS 1.0.0). Send
  223. `X-Auth: {auth_key}` and `X-Auth-Rest: {rest_auth_key}` headers on every request below.
  224. 1. Create the upload: `POST` to `{url}/{relative_file_path}?override=true` with headers
  225. `upload-length: {file size in bytes}` and `upload-offset: 0`. Expect `201 Created`.
  226. 2. Upload the file: send the file bytes to the same location (any TUS 1.0.0 client, or
  227. `PATCH` requests with an `upload-offset` header tracking progress) until complete.
  228. `relative_file_path` is the destination path inside the website's file storage, e.g.
  229. `app.zip`.
  230. Instead of a TUS client, plain `curl` also works:
  231. ```
  232. FILE=app.zip
  233. SIZE=$(stat -f%z "$FILE") # stat -c%s on Linux
  234. curl -i -X POST "{url}/${FILE}?override=true" \
  235. -H "X-Auth: {auth_key}" \
  236. -H "X-Auth-Rest: {rest_auth_key}" \
  237. -H "Tus-Resumable: 1.0.0" \
  238. -H "Upload-Length: ${SIZE}" \
  239. -H "Upload-Offset: 0"
  240. # -> 201 Created
  241. curl -i -X PATCH "{url}/${FILE}?override=true" \
  242. -H "X-Auth: {auth_key}" \
  243. -H "X-Auth-Rest: {rest_auth_key}" \
  244. -H "Tus-Resumable: 1.0.0" \
  245. -H "Content-Type: application/offset+octet-stream" \
  246. -H "Upload-Offset: 0" \
  247. --data-binary "@${FILE}"
  248. # -> 204 No Content, Upload-Offset response header equals SIZE when done
  249. ```
  250. - **Method**: `POST`
  251. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/files/upload-urls`
  252. #### agency-hosting_files_import-website-from-archive
  253. Imports an Agency Plan website from an already-uploaded archive.
  254. Upload the archive to the website's root directory via file browser first, then provide its
  255. filename in this request. Website contents are overwritten by the archive contents. Supported
  256. archive types: .zip, .tar, .tar.gz, .tgz.
  257. - **Method**: `POST`
  258. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/files/import-archive`
  259. #### agency-hosting_metrics_list-plan-order-disk-usage
  260. Returns aggregated disk and inode usage for the Agency Plan order over the
  261. selected time frame, plus the plan quotas. Figures cover the whole order
  262. account. Values may be up to one hour stale. CPU, memory, and process usage
  263. are on the resource-usage-metrics endpoint.
  264. - **Method**: `GET`
  265. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/disk-usage-metrics`
  266. #### agency-hosting_orders_list
  267. Returns a paginated list of Agency Plan orders accessible to the authenticated client.
  268. - **Method**: `GET`
  269. - **Path**: `/api/agency-hosting/v1/orders`
  270. #### agency-hosting_metrics_list-order-resource-usage
  271. Returns aggregated CPU, memory, and process usage for the Agency Plan order
  272. over the selected time frame, plus the plan quotas and a per-website
  273. breakdown. Each website is identified by uid. Suspended and deleted websites
  274. are excluded from both the order totals and the per-website breakdown.
  275. Values may be up to one hour stale. Disk and inode usage are on the
  276. disk-usage-metrics endpoint.
  277. - **Method**: `GET`
  278. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/resource-usage-metrics`
  279. #### agency-hosting_php_list-extensions-for-website
  280. Lists every PHP extension available to an Agency Plan website and whether it is currently enabled.
  281. - **Method**: `GET`
  282. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions`
  283. #### agency-hosting_php_replace-website-extensions
  284. Replaces the set of PHP extensions enabled on an Agency Plan website with the ones provided. Any toggleable extension not in the request is disabled, so call the extensions endpoint first and send the full desired set. Extensions compiled into PHP, reported with the "built-in" state, are always active and are unaffected.
  285. - **Method**: `PUT`
  286. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/extensions`
  287. #### agency-hosting_php_list-options-for-website
  288. Lists the php.ini directives that can be configured for an Agency Plan website, each with its default, the value currently in effect, and the values it accepts.
  289. - **Method**: `GET`
  290. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/options`
  291. #### agency-hosting_php_replace-website-options
  292. Replaces the custom php.ini values on an Agency Plan website with the ones provided. Any option not in the request is reset to its default, so call the options endpoint first and send the full desired set. Sending an empty array resets every option to its default.
  293. - **Method**: `PUT`
  294. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/options`
  295. #### agency-hosting_php_list-versions-for-order
  296. Lists the PHP versions available to websites created under an Agency Plan order, determined by the server the order is hosted on. Use this before creating a website; for a website that already exists, call the website-scoped versions endpoint instead.
  297. - **Method**: `GET`
  298. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/php-settings/versions`
  299. #### agency-hosting_php_list-versions-for-website
  300. Lists the PHP versions an Agency Plan website can be switched to. The version the website is currently running is returned as settings.php.version by the website details endpoint.
  301. - **Method**: `GET`
  302. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/versions`
  303. #### agency-hosting_php_update-website-version
  304. Switches an Agency Plan website to a different PHP version. Call the available versions endpoint first to see which versions can be selected. The website restarts on the new version, so requests served during the switch may fail and code that is incompatible with the target version will break.
  305. - **Method**: `PATCH`
  306. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/php-settings/version`
  307. #### agency-hosting_website-setups_create
  308. Provisions a new website on one of your Agency Plan hosting orders.
  309. Choose the datacenter, stack (`flavor`), and PHP version for the site. Optionally attach
  310. your own `domain` — omit it, set it to `null`, or leave it unavailable and a free
  311. `*.hostingersite.com` subdomain is generated instead — and/or install WordPress by
  312. supplying the `wordpress` details (admin account, site title, and language).
  313. Common setups:
  314. - **Plain PHP site**: `flavor` set to `php-fpm`, with `settings.php.version`; omit
  315. `wordpress` and `type`.
  316. - **WordPress site**: `flavor` set to the desired WordPress version (e.g. `wp-7.0`), plus
  317. the `wordpress` block (admin account, title, language).
  318. - **Static/Node.js frontend app**: `flavor` set to `php-fpm` and `type` set to
  319. `node-static`.
  320. Provisioning runs in the background, so the response returns immediately with a setup UUID
  321. that identifies the job. The new website becomes reachable once provisioning finishes.
  322. - **Method**: `POST`
  323. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/setups`
  324. #### agency-hosting_website-setups_status
  325. Returns the current status of an Agency Plan website setup started via the setups
  326. endpoint.
  327. Poll this endpoint using the `setup_uuid` returned from the provisioning request until
  328. `status` becomes `completed`, at which point `website_uid` identifies the new website.
  329. - **Method**: `GET`
  330. - **Path**: `/api/agency-hosting/v1/orders/{order_id}/websites/setups/{setup_uuid}`
  331. #### agency-hosting_ssl_reinstall-website
  332. Replaces the Let's Encrypt certificate of the domain: the current platform certificate, when
  333. one is recorded, is revoked and removed, then a new setup starts in the background. Returns at
  334. once; `Get website SSL status` reports `installing` while it runs, then `active` or `failed`.
  335. Returns 422 for free subdomains, when a certificate process is recorded for the domain (a
  336. failed setup counts until it is cleaned up), or when the domain hit its limit of three setups
  337. per seven days. Returns 429 when the same domain was requested less than a minute ago, and 403
  338. when the website is suspended or locked, and 404 when the website or the domain does not exist.
  339. - **Method**: `POST`
  340. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/reinstall`
  341. #### agency-hosting_ssl_install-website
  342. Starts a Let's Encrypt certificate setup for the domain and returns at once; the setup runs in
  343. the background. `Get website SSL status` reports `installing` while it runs, then `active` or
  344. `failed`; the `ssl_setup` entry of `List website processes` shows the same progress.
  345. Returns 422 when the domain already has a platform certificate that is not expired, when a
  346. certificate process is recorded for the domain (a failed setup counts until it is cleaned up),
  347. or when the domain hit its limit of three setups per seven days. Returns 429 when the same
  348. domain was requested less than a minute ago, 403 when the website is suspended or locked, and
  349. 404 when the website or the domain does not exist.
  350. - **Method**: `POST`
  351. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/setup`
  352. #### agency-hosting_ssl_website-status
  353. Returns the SSL state of one domain of an Agency Plan website: the certificate `status`,
  354. whether the certificate was uploaded by the customer, and when it stops being valid.
  355. `installing` means a certificate setup is running or retrying; the `ssl_setup` entry of
  356. `List website processes` shows the same progress. `active` means a valid certificate is in
  357. place: uploaded by the customer, issued by the platform, or a lifetime certificate bought for
  358. the domain. `failed` means the last setup gave up and no valid certificate is in place.
  359. `expired` means the certificate has run out. `not_installed` means the domain has no
  360. certificate and no setup process. Returns 404 when the website or the domain does not exist.
  361. - **Method**: `GET`
  362. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl/status`
  363. #### agency-hosting_ssl_uninstall-website
  364. Removes the platform-issued Let's Encrypt certificate of the domain: the certificate is revoked
  365. and deleted before the response, so the domain is no longer served with a platform certificate
  366. until a new setup completes. Also succeeds when the domain has no platform certificate to
  367. remove. Uploaded (custom) certificates are not affected.
  368. Returns 422 when a certificate process is recorded for the domain (a failed setup counts until
  369. it is cleaned up), 429 when the same domain was requested less than a minute ago, and 403 when
  370. the website is suspended or locked, and 404 when the website or the domain does not exist.
  371. - **Method**: `DELETE`
  372. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/domains/{domain}/ssl`
  373. #### agency-hosting_websites_build-nodejs-assets
  374. Builds and deploys a Node.js application for an Agency Plan website from an already-uploaded archive.
  375. Upload the archive to file browser first, then provide its relative path from document root in this request.
  376. Website contents are overwritten by the build result, which is deployed to public_html.
  377. - **Method**: `POST`
  378. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/build-assets`
  379. #### agency-hosting_cache_clear-website
  380. Clears cache for all domains associated with an Agency Plan website, including its preview domain.
  381. This operation clears all cache types for the website.
  382. - **Method**: `DELETE`
  383. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cache`
  384. #### agency-hosting_cron-jobs_list-website
  385. Returns a paginated list of cron jobs configured for an Agency Plan website.
  386. Each entry includes the schedule expression and the command executed on that schedule.
  387. - **Method**: `GET`
  388. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs`
  389. #### agency-hosting_cron-jobs_create-website
  390. Creates a cron job for an Agency Plan website from a schedule expression and a command.
  391. Returns the created cron job, including its uuid, which is required to delete the cron job.
  392. - **Method**: `POST`
  393. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs`
  394. #### agency-hosting_cron-jobs_delete-website
  395. Permanently deletes the cron job identified by its uuid from an Agency Plan website.
  396. The operation is idempotent: deleting a cron job that does not exist succeeds without error.
  397. - **Method**: `DELETE`
  398. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/cron-jobs/{uuid}`
  399. #### agency-hosting_databases_list-website
  400. Returns a paginated list of MySQL databases created for an Agency Plan website.
  401. Each entry includes the database's non-system users.
  402. - **Method**: `GET`
  403. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases`
  404. #### agency-hosting_databases_create-website
  405. Creates a MySQL database with a dedicated user for an Agency Plan website.
  406. The database name, username, and password must all be provided by the caller.
  407. - **Method**: `POST`
  408. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases`
  409. #### agency-hosting_databases_delete-website
  410. Permanently deletes a MySQL database and all its data from an Agency Plan website, including its users.
  411. The operation is idempotent: deleting a database that does not exist succeeds without error.
  412. - **Method**: `DELETE`
  413. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}`
  414. #### agency-hosting_databases_create-website-user
  415. Creates a user for an existing database on an Agency Plan website.
  416. Each database supports a single non-system user; creating a user for a database that already has one fails.
  417. - **Method**: `POST`
  418. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users`
  419. #### agency-hosting_databases_delete-website-user
  420. Permanently deletes a database user from an Agency Plan website database, revoking all access it had.
  421. The operation is idempotent: deleting a user that does not exist succeeds without error.
  422. - **Method**: `DELETE`
  423. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/databases/{database_name}/users/{database_user_name}`
  424. #### agency-hosting_websites_get
  425. Retrieves detailed information about a specific Agency Plan website, including configuration,
  426. status, metadata, hosting plan details, and resource quotas.
  427. - **Method**: `GET`
  428. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}`
  429. #### agency-hosting_websites_delete
  430. Permanently deletes an Agency Plan website. Deletion is processed asynchronously: the
  431. website is immediately transitioned to a deleting state and the underlying server
  432. resources are removed in the background.
  433. - **Method**: `DELETE`
  434. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}`
  435. #### agency-hosting_websites_list-plan
  436. Retrieve a paginated list of Agency Plan websites (H5G, Builder, and Horizons) accessible to
  437. the authenticated client.
  438. This endpoint returns websites from your hosting accounts as well as
  439. websites from other client hosting accounts that have shared access
  440. with you.
  441. The response shape differs per platform — see the `platform` field on each item.
  442. Use `website_types` to list only websites of a given detected type, e.g. only
  443. WordPress websites (`website_types=wordpress`) or only Node.js websites
  444. (`website_types=nodejs`). Combine with `order_ids`, `states`, or `domain` for more
  445. targeted results.
  446. - **Method**: `GET`
  447. - **Path**: `/api/agency-hosting/v1/websites`
  448. #### agency-hosting_websites_list-processes
  449. Lists active and recently completed asynchronous processes for an Agency Plan website.
  450. Each process has a unique ID (for tracking), a type, and a status (running, completed, failed).
  451. Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
  452. - **Method**: `GET`
  453. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/processes`
  454. #### agency-hosting_wordpress_change-version
  455. Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation.
  456. - **Method**: `PATCH`
  457. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/version`
  458. #### agency-hosting_wordpress_settings
  459. Returns the current WordPress settings for an Agency Plan website: installed core version,
  460. LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
  461. - **Method**: `GET`
  462. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings`
  463. #### agency-hosting_wordpress_list-versions
  464. Lists the WordPress core versions available for installation on an Agency Plan website.
  465. - **Method**: `GET`
  466. - **Path**: `/api/agency-hosting/v1/websites/{website_uid}/wordpress/settings/versions`
  467. ### `hostinger-agent-readiness-mcp`
  468. #### changelog_list-entries
  469. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  470. - **Method**: `custom`
  471. - **Path**: `custom`
  472. #### agent-readiness_checks_list
  473. List every check an agent readiness scan runs, with its name, category and weight.\n
  474. Use it to show the human-readable name of each `check_id` in a scan's results.
  475. - **Method**: `GET`
  476. - **Path**: `/api/agent-readiness/v1/checks`
  477. #### agent-readiness_scans_run
  478. Start a scan of how ready a public website is for AI agents to discover, read and act on.\n
  479. Scanning is asynchronous: this operation only starts the scan, and the returned scan is usually `pending`
  480. with no results yet. To get the results, poll the `Get agent readiness scan` operation with the same
  481. domain every few seconds until its status is `completed` or `failed`. The scan itself is limited to 60 seconds,
  482. plus any time it waits in the queue. A `failed` scan is not retried; run this operation again.\n
  483. Starting a scan for a domain that already has a pending scan from the last 5 minutes
  484. returns that scan instead of starting a new one.
  485. - **Method**: `POST`
  486. - **Path**: `/api/agent-readiness/v1/scans`
  487. #### agent-readiness_scans_get
  488. Get the latest agent readiness scan of a website.\n
  489. Scans started with the `Run agent readiness scan` operation are asynchronous. While the status is
  490. `pending`, the result fields are null; wait a few seconds and call this operation again until the status is
  491. `completed` or `failed`. A `failed` scan is not retried; run the scan again.\n
  492. A completed scan has a 0-100 score, a letter grade, a score per category, and the result of every
  493. check with the evidence found and how to fix it. Check names are listed by the `List checks` operation.\n
  494. Returns 404 when the domain has never been scanned; use the `Run agent readiness scan` operation first.
  495. - **Method**: `GET`
  496. - **Path**: `/api/agent-readiness/v1/scans/{domain}`
  497. ### `hostinger-billing-mcp`
  498. #### changelog_list-entries
  499. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  500. - **Method**: `custom`
  501. - **Path**: `custom`
  502. #### billing_catalog_list
  503. Retrieve catalog items available for order.
  504. Prices in catalog items is displayed as cents (without floating point),
  505. e.g: float `17.99` is displayed as integer `1799`.
  506. Use this endpoint to view available services and pricing before placing orders.
  507. - **Method**: `GET`
  508. - **Path**: `/api/billing/v1/catalog`
  509. #### billing_orders_create-purchase
  510. Create a purchase order for any Hostinger product.
  511. This unified endpoint places an order for one or more catalog items and
  512. works across all Hostinger products, leveraging the existing billing
  513. infrastructure. Use the [catalog endpoint](#tag/billing-catalog) to look
  514. up the `item_id` values available for purchase.
  515. If no payment method is provided, your default payment method will be used automatically.
  516. If the response is `202 Accepted`, the payment is still being processed and the order will
  517. complete asynchronously once the payment is confirmed.
  518. This endpoint only places the order. Product-specific provisioning
  519. (e.g. VPS setup or domain registration) is not performed here — once the
  520. order completes, use the relevant product endpoints or
  521. [hPanel](https://hpanel.hostinger.com/) to finalize setup.
  522. Use this endpoint to purchase any product available in the catalog.
  523. - **Method**: `POST`
  524. - **Path**: `/api/billing/v1/orders`
  525. #### billing_payment-methods_set-default
  526. Set the default payment method for your account.
  527. Use this endpoint to configure the primary payment method for future orders.
  528. - **Method**: `POST`
  529. - **Path**: `/api/billing/v1/payment-methods/{paymentMethodId}`
  530. #### billing_payment-methods_delete
  531. Delete a payment method from your account.
  532. Use this endpoint to remove unused payment methods from user accounts.
  533. - **Method**: `DELETE`
  534. - **Path**: `/api/billing/v1/payment-methods/{paymentMethodId}`
  535. #### billing_payment-methods_list
  536. Retrieve available payment methods that can be used for placing new orders.
  537. If you want to add new payment method,
  538. please use [hPanel](https://hpanel.hostinger.com/billing/payment-methods).
  539. Use this endpoint to view available payment options before creating orders.
  540. - **Method**: `GET`
  541. - **Path**: `/api/billing/v1/payment-methods`
  542. #### billing_subscriptions_list
  543. Retrieve a list of all subscriptions associated with your account.
  544. Use this endpoint to monitor active services and billing status.
  545. - **Method**: `GET`
  546. - **Path**: `/api/billing/v1/subscriptions`
  547. #### billing_subscriptions_disable-auto-renewal
  548. Disable auto-renewal for a subscription.
  549. Use this endpoint when disable auto-renewal for a subscription.
  550. - **Method**: `DELETE`
  551. - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/disable`
  552. #### billing_subscriptions_enable-auto-renewal
  553. Enable auto-renewal for a subscription.
  554. Use this endpoint when enable auto-renewal for a subscription.
  555. - **Method**: `PATCH`
  556. - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/auto-renewal/enable`
  557. #### billing_subscriptions_renew
  558. Create a renewal order for an existing Hostinger subscription.
  559. This endpoint places a renewal order for a single subscription, leveraging
  560. the existing billing infrastructure. Use the
  561. [subscriptions endpoint](#tag/billing-subscriptions) to look up the
  562. `subscriptionId` values available for renewal.
  563. If no payment method is provided, your default payment method will be used automatically.
  564. If the response is `202 Accepted`, the payment is still being processed and the renewal will
  565. complete asynchronously once the payment is confirmed.
  566. Use this endpoint to renew any subscription available in your account.
  567. - **Method**: `POST`
  568. - **Path**: `/api/billing/v1/subscriptions/{subscriptionId}/renew`
  569. ### `hostinger-dns-mcp`
  570. #### changelog_list-entries
  571. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  572. - **Method**: `custom`
  573. - **Path**: `custom`
  574. #### dns_snapshots_get
  575. Retrieve particular DNS snapshot with contents of DNS zone records.
  576. Use this endpoint to view historical DNS configurations for domains.
  577. - **Method**: `GET`
  578. - **Path**: `/api/dns/v1/snapshots/{domain}/{snapshotId}`
  579. #### dns_snapshots_list
  580. Retrieve DNS snapshots for a domain.
  581. Use this endpoint to view available DNS backup points for restoration.
  582. - **Method**: `GET`
  583. - **Path**: `/api/dns/v1/snapshots/{domain}`
  584. #### dns_snapshots_restore
  585. Restore DNS zone to the selected snapshot.
  586. Use this endpoint to revert domain DNS to a previous configuration.
  587. - **Method**: `POST`
  588. - **Path**: `/api/dns/v1/snapshots/{domain}/{snapshotId}/restore`
  589. #### dns_records_list
  590. Retrieve DNS zone records for a specific domain.
  591. Use this endpoint to view current DNS configuration for domain management.
  592. - **Method**: `GET`
  593. - **Path**: `/api/dns/v1/zones/{domain}`
  594. #### dns_records_update
  595. Update DNS records for the selected domain.
  596. Using `overwrite = true` will replace existing records with the provided ones.
  597. Otherwise existing records will be updated and new records will be added.
  598. Use this endpoint to modify domain DNS configuration.
  599. - **Method**: `PUT`
  600. - **Path**: `/api/dns/v1/zones/{domain}`
  601. #### dns_records_delete
  602. Delete DNS records for the selected domain.
  603. To filter which records to delete, add the `name` of the record and `type` to the filter.
  604. Multiple filters can be provided with single request.
  605. If you have multiple records with the same name and type, and you want to delete only part of them,
  606. refer to the `Update zone records` endpoint.
  607. Use this endpoint to remove specific DNS records from domains.
  608. - **Method**: `DELETE`
  609. - **Path**: `/api/dns/v1/zones/{domain}`
  610. #### dns_records_reset
  611. Reset DNS zone to the default records.
  612. Use this endpoint to restore domain DNS to original configuration.
  613. - **Method**: `POST`
  614. - **Path**: `/api/dns/v1/zones/{domain}/reset`
  615. #### dns_records_validate
  616. Validate DNS records prior to update for the selected domain.
  617. If the validation is successful, the response will contain `200 Success` code.
  618. If there is validation error, the response will fail with `422 Validation error` code.
  619. Use this endpoint to verify DNS record validity before applying changes.
  620. - **Method**: `POST`
  621. - **Path**: `/api/dns/v1/zones/{domain}/validate`
  622. ### `hostinger-domains-mcp`
  623. #### changelog_list-entries
  624. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  625. - **Method**: `custom`
  626. - **Path**: `custom`
  627. #### domains_verifications_direct
  628. Retrieve a list of pending and completed domain verifications.
  629. - **Method**: `GET`
  630. - **Path**: `/api/v2/direct/verifications/active`
  631. #### domains_availability_suggest-names-from-description
  632. Suggest available domain names based on a free-text description of your project.
  633. Suggestions are generated by an AI model, so they differ between calls.
  634. Endpoint has rate limit of 90 requests per minute.
  635. Use this endpoint to find a domain name when you only know what the website is about.
  636. - **Method**: `POST`
  637. - **Path**: `/api/domains/v1/availability/alternatives-from-description`
  638. #### domains_availability_suggest-names-from
  639. Suggest available domain names based on a domain name you already have in mind.
  640. Suggestions are generated by an AI model, so they differ between calls.
  641. Endpoint has rate limit of 90 requests per minute.
  642. Use this endpoint when the domain you wanted is taken and you need close alternatives.
  643. - **Method**: `POST`
  644. - **Path**: `/api/domains/v1/availability/alternatives-from-domain`
  645. #### domains_availability_check
  646. Check availability of domain names across multiple TLDs.
  647. Multiple TLDs can be checked at once.
  648. If you want alternative domains with response, provide only one TLD and set `with_alternatives` to `true`.
  649. TLDs should be provided without leading dot (e.g. `com`, `net`, `org`).
  650. Premium domains are included: an available premium domain has `is_available` and `is_premium` set to `true`.
  651. Endpoint has rate limit of 90 requests per minute.
  652. Use this endpoint to verify domain availability before purchase.
  653. - **Method**: `POST`
  654. - **Path**: `/api/domains/v1/availability`
  655. #### domains_forwarding_get
  656. Retrieve domain forwarding data.
  657. Returns 404 when the domain has no forwarding.
  658. Use this endpoint to view current redirect configuration for domains.
  659. - **Method**: `GET`
  660. - **Path**: `/api/domains/v1/forwarding/{domain}`
  661. #### domains_forwarding_update
  662. Update domain forwarding configuration.
  663. Updating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
  664. switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
  665. elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
  666. with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
  667. current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
  668. user before updating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
  669. propagate.
  670. Use this endpoint to modify existing redirect configuration for domains.
  671. - **Method**: `PUT`
  672. - **Path**: `/api/domains/v1/forwarding/{domain}`
  673. #### domains_forwarding_delete
  674. Delete domain forwarding data.
  675. Use this endpoint to remove redirect configuration from domains.
  676. - **Method**: `DELETE`
  677. - **Path**: `/api/domains/v1/forwarding/{domain}`
  678. #### domains_forwarding_create
  679. Create domain forwarding configuration.
  680. Creating a forwarding changes the domain's DNS. If the domain does not use Hostinger nameservers, they are
  681. switched to Hostinger's nameservers automatically, so website, email and other services whose DNS is hosted
  682. elsewhere stop working. The root (@) A and AAAA records in the domain's Hostinger DNS zone are also replaced
  683. with records pointing to Hostinger, even when the domain already uses Hostinger nameservers. The domain's
  684. current nameservers are returned by the [domain details endpoint](#tag/domains-portfolio); confirm with the
  685. user before creating a forwarding on a domain that uses other nameservers. DNS changes can take some time to
  686. propagate.
  687. Use this endpoint to set up domain redirects to other URLs.
  688. - **Method**: `POST`
  689. - **Path**: `/api/domains/v1/forwarding`
  690. #### domains_whois_pending-irtp-verification
  691. Retrieve a pending IRTP verification for a domain.
  692. Both the old and new registrant must confirm it before the WHOIS change takes effect.
  693. Returns 404 when the domain has no pending IRTP verification.
  694. Use this endpoint to check the status of a WHOIS change awaiting registrant confirmation.
  695. - **Method**: `GET`
  696. - **Path**: `/api/domains/v1/irtp/{domain}`
  697. #### domains_whois_cancel-pending-irtp-verification
  698. Cancel a pending IRTP verification.
  699. Use this endpoint to back out of a WHOIS change that is stuck waiting on registrant confirmation,
  700. for example when the confirmation email cannot be received, without waiting out the 5-day expiry.
  701. - **Method**: `DELETE`
  702. - **Path**: `/api/domains/v1/irtp/{domain}`
  703. #### domains_move_incoming
  704. Retrieve the incoming move for a specified domain.
  705. Returns 404 when no account is moving this domain to you.
  706. Use this endpoint to check whether a domain addressed to you is still waiting to be accepted.
  707. - **Method**: `GET`
  708. - **Path**: `/api/domains/v1/move/incoming/{domain}`
  709. #### domains_move_accept-incoming
  710. Accept an incoming move for a specified domain.
  711. The provided WHOIS profiles become the contacts of the domain, so they must belong
  712. to your account and satisfy the requirements of the TLD. Only the contact types the
  713. domain actually uses are applied, but all four profile IDs have to be provided.
  714. The move has to still be waiting for your decision, already accepted moves
  715. cannot be accepted again.
  716. Accepting does not complete the move. A confirmation email is sent to the email address of
  717. the new owner contact, and the domain changes hands only after the change is confirmed from it.
  718. Until then the move stays in the `activating` status, which can be followed with the
  719. [incoming move endpoint](#tag/domains-move).
  720. Use this endpoint to take ownership of a domain offered to you.
  721. - **Method**: `PUT`
  722. - **Path**: `/api/domains/v1/move/incoming/{domain}`
  723. #### domains_move_reject-incoming
  724. Reject an incoming move for a specified domain.
  725. The domain stays in the account which initiated the move.
  726. Moves you have already accepted cannot be rejected anymore.
  727. Use this endpoint to decline a domain you do not want to take over.
  728. - **Method**: `DELETE`
  729. - **Path**: `/api/domains/v1/move/incoming/{domain}`
  730. #### domains_move_incoming-list
  731. Retrieve all domains other Hostinger accounts are moving to your account.
  732. Moves of every status are returned, including the ones which already completed.
  733. Use this endpoint to find domains waiting for you to accept them.
  734. - **Method**: `GET`
  735. - **Path**: `/api/domains/v1/move/incoming`
  736. #### domains_move_outgoing
  737. Retrieve the outgoing move for a specified domain.
  738. Returns 404 when the domain has no move in progress.
  739. Use this endpoint to track the status of a move you have initiated for a single domain.
  740. - **Method**: `GET`
  741. - **Path**: `/api/domains/v1/move/outgoing/{domain}`
  742. #### domains_move_start-outgoing
  743. Initiate a move of a specified domain to another Hostinger account.
  744. The receiving account has to already exist and accept the move before the domain changes hands.
  745. The domain must be active. The subscription it belongs to is resolved automatically,
  746. and the request is rejected with a 404 status code when the domain has no domain
  747. subscription of its own.
  748. The move is also refused unless the domain:
  749. - was registered at least 4 days ago
  750. - does not expire within the next 10 days
  751. - has an extension that supports moves
  752. - has no move already in progress
  753. - was not moved in the last 10 days
  754. - is not a premium domain
  755. - is not still processing a recent renewal
  756. A move refused for one of these rules is rejected with a 404 status code and error code 2048,
  757. with a message naming the rule. The receiving account is checked first, and when it cannot
  758. be used the message stays generic.
  759. Domains protected by premium protection require an additional verification step,
  760. such requests are rejected with a 428 status code.
  761. Use this endpoint to hand a domain over to another Hostinger user.
  762. - **Method**: `POST`
  763. - **Path**: `/api/domains/v1/move/outgoing/{domain}`
  764. #### domains_move_cancel-outgoing
  765. Cancel an outgoing move for a specified domain.
  766. The move can only be cancelled while the receiving account has not accepted it yet.
  767. The domain stays in your account.
  768. Use this endpoint to withdraw a move you no longer want to complete.
  769. - **Method**: `DELETE`
  770. - **Path**: `/api/domains/v1/move/outgoing/{domain}`
  771. #### domains_move_outgoing-list
  772. Retrieve all domains you are moving to other Hostinger accounts.
  773. Only moves which have not completed yet are returned.
  774. Use this endpoint to track moves you have initiated and the accounts they are addressed to.
  775. - **Method**: `GET`
  776. - **Path**: `/api/domains/v1/move/outgoing`
  777. #### domains_portfolio_authorization-code
  778. Retrieve the authorization (EPP) code for a specified domain so it can be transferred
  779. away from Hostinger to another registrar.
  780. Requesting a new code invalidates any code retrieved previously.
  781. Use this endpoint to obtain the code required to transfer a domain to another registrar.
  782. - **Method**: `GET`
  783. - **Path**: `/api/domains/v1/portfolio/{domain}/auth-code`
  784. #### domains_portfolio_claim-free
  785. Claim a free domain available on your account and register it.
  786. Unlike purchasing a domain, this consumes a free domain you already have,
  787. so no payment method is required.
  788. A free domain and a free domain transfer from the same plan are alternatives:
  789. claiming the free domain removes the plan's free domain transfer
  790. (`type: free_domain_transfer`). Before making request, confirm with the user which
  791. of the two they want. Right after a claim, the removed free domain transfer may
  792. still appear in the [domain list endpoint](#tag/domains-portfolio) for a short
  793. time; do not claim it.
  794. A successful response means the domain is registered. If registration fails, login to
  795. [hPanel](https://hpanel.hostinger.com/) and check domain registration status.
  796. If no WHOIS information is provided, default contact information for that TLD will be used.
  797. Before making request, ensure WHOIS information for desired TLD exists in your account.
  798. Some TLDs require `additional_details` to be provided and these will be validated before claiming.
  799. Requests which cannot be fulfilled are rejected with an error code in the response body,
  800. for example `2037` when no free domain is available.
  801. Use this endpoint to register a domain using a free domain from your account.
  802. - **Method**: `POST`
  803. - **Path**: `/api/domains/v1/portfolio/claim`
  804. #### domains_portfolio_enable-lock
  805. Enable domain lock for the domain.
  806. When domain lock is enabled,
  807. the domain cannot be transferred to another registrar without first disabling the lock.
  808. Use this endpoint to secure domains against unauthorized transfers.
  809. - **Method**: `PUT`
  810. - **Path**: `/api/domains/v1/portfolio/{domain}/domain-lock`
  811. #### domains_portfolio_disable-lock
  812. Disable domain lock for the domain.
  813. Domain lock needs to be disabled before transferring the domain to another registrar.
  814. Use this endpoint to prepare domains for transfer to other registrars.
  815. - **Method**: `DELETE`
  816. - **Path**: `/api/domains/v1/portfolio/{domain}/domain-lock`
  817. #### domains_portfolio_get
  818. Retrieve detailed information for specified domain.
  819. A domain is found here only once it is registered. Until then, `Get domain list` shows it, and
  820. its `verification` field says what registration waits for when the domain is held for
  821. verification.
  822. After registration, the registry may require the owner contact to be verified by email, phone
  823. number or contact name before a deadline, after which the domain is suspended. The
  824. `contact_verification` field shows what needs verifying, its state and the deadline.
  825. Use this endpoint to view comprehensive domain configuration and status.
  826. - **Method**: `GET`
  827. - **Path**: `/api/domains/v1/portfolio/{domain}`
  828. #### domains_portfolio_list
  829. Retrieve all domains associated with your account.
  830. A plan can include both a free domain (`type: free_domain`) and a free domain
  831. transfer (`type: free_domain_transfer`). They are alternatives: claiming one
  832. removes the other, which may still be listed for a short time after the claim.
  833. A domain held for verification before it is registered has `status: pending_verification`,
  834. and its `verification` field says what registration waits for: a manual review, an SMS code,
  835. or owner contact verification.
  836. Use this endpoint to view user's domain portfolio.
  837. - **Method**: `GET`
  838. - **Path**: `/api/domains/v1/portfolio`
  839. #### domains_portfolio_purchase
  840. Purchase and register a new domain name.
  841. If registration fails, login to [hPanel](https://hpanel.hostinger.com/) and check domain registration status.
  842. If no payment method is provided, your default payment method will be used automatically.
  843. If the response is `202 Accepted`, the payment is still being processed and the domain was
  844. **not** registered. Once the order completes, register the domain from
  845. [hPanel](https://hpanel.hostinger.com/).
  846. If no WHOIS information is provided, default contact information for that TLD will be used.
  847. Before making request, ensure WHOIS information for desired TLD exists in your account.
  848. Some TLDs require `additional_details` to be provided and these will be validated before completing purchase.
  849. Use this endpoint to register new domains for users.
  850. - **Method**: `POST`
  851. - **Path**: `/api/domains/v1/portfolio`
  852. #### domains_portfolio_enable-privacy-protection
  853. Enable privacy protection for the domain.
  854. When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database.
  855. Use this endpoint to protect domain owner's personal information from public view.
  856. - **Method**: `PUT`
  857. - **Path**: `/api/domains/v1/portfolio/{domain}/privacy-protection`
  858. #### domains_portfolio_disable-privacy-protection
  859. Disable privacy protection for the domain.
  860. When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database.
  861. Use this endpoint to make domain owner's information publicly visible.
  862. - **Method**: `DELETE`
  863. - **Path**: `/api/domains/v1/portfolio/{domain}/privacy-protection`
  864. #### domains_portfolio_renewal-information
  865. Retrieve renewal information for a specified domain, including its status, current
  866. expiration date, whether it can be renewed, whether it is in its grace or redemption period,
  867. and when each of those periods ends.
  868. Use this endpoint to build renewal automation and expiry monitoring for a single domain.
  869. - **Method**: `GET`
  870. - **Path**: `/api/domains/v1/portfolio/{domain}/renewal`
  871. #### domains_portfolio_complete-setup
  872. Register a domain you have already paid for but which has not been set up yet.
  873. Use this endpoint when an order completed without registering the domain, for example when
  874. `Purchase new domain` returned `202 Accepted` and the domain was added to your account without
  875. being registered, or when an earlier setup attempt failed. No new order is placed and no payment
  876. is taken: the subscription you already own is used, for the period you already paid for.
  877. A domain is left awaiting setup when the details needed to register it were missing or invalid
  878. as the order completed. Domains ordered elsewhere can be awaiting setup for the same reason.
  879. Complete the missing information, then call this endpoint. If the order itself has not completed
  880. yet, the domain is not on your account, wait until it appears in `Get domain list`.
  881. If `domain_contacts` is omitted, the default WHOIS profile of that TLD is used for all four
  882. roles. The profile must exist and be complete for the TLD, an incomplete profile is the most
  883. common reason a domain is left awaiting setup. Create one with `Create WHOIS profile`.
  884. Some TLDs require `additional_details`. These are validated before setup, so a missing or
  885. invalid value is rejected without any registration being attempted.
  886. The domain is set up with the default nameservers and with privacy protection. Use
  887. `Update domain nameservers` and `Disable privacy protection` afterwards to change either.
  888. A successful response means the setup request was accepted, not that the domain is already
  889. registered. Poll `Get domain list` for the outcome, the domain appears in `Get domain details`
  890. only once it is registered. When the domain is held for verification, its `verification` field
  891. in `Get domain list` says what registration waits for.
  892. Use this endpoint to finish registering a domain that is awaiting setup on your account.
  893. - **Method**: `POST`
  894. - **Path**: `/api/domains/v1/portfolio/{domain}/setup`
  895. #### domains_portfolio_update-nameservers
  896. Set nameservers for a specified domain.
  897. Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.
  898. Use this endpoint to configure custom DNS hosting for domains.
  899. - **Method**: `PUT`
  900. - **Path**: `/api/domains/v1/portfolio/{domain}/nameservers`
  901. #### domains_transfer_claim-free
  902. Claim a free domain transfer available on your account and start the transfer.
  903. Unlike purchasing a transfer, this consumes a free domain transfer you already have,
  904. so no payment method is required.
  905. A free domain and a free domain transfer from the same plan are alternatives:
  906. claiming the free domain transfer removes the plan's free domain
  907. (`type: free_domain`). Before making request, confirm with the user which of the
  908. two they want. Right after a claim, the removed free domain may still appear in
  909. the [domain list endpoint](#tag/domains-portfolio) for a short time; do not claim it.
  910. Before making request, unlock the domain at the current registrar and, if its TLD uses one,
  911. get its authorization code. The transfer is validated first, so domains which cannot be
  912. transferred, or are missing a required authorization code, are rejected before the free
  913. domain transfer is consumed.
  914. A successful response means the transfer has been started. Completion depends on the current
  915. registrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).
  916. If no WHOIS information is provided, default contact information for that TLD will be used.
  917. Before making request, ensure WHOIS information for desired TLD exists in your account.
  918. Requests which cannot be fulfilled are rejected with an error code in the response body.
  919. Use this endpoint to transfer a domain using a free domain transfer from your account.
  920. - **Method**: `POST`
  921. - **Path**: `/api/domains/v1/transfers/claim`
  922. #### domains_transfer_get
  923. Retrieve the transfer for a specified domain.
  924. Use this endpoint to track an incoming or outgoing registrar transfer and its status.
  925. - **Method**: `GET`
  926. - **Path**: `/api/domains/v1/transfers/{domain}`
  927. #### domains_transfer_list
  928. Retrieve all domain transfers in your portfolio.
  929. Use this endpoint to monitor incoming and outgoing registrar transfers across your domains.
  930. - **Method**: `GET`
  931. - **Path**: `/api/domains/v1/transfers`
  932. #### domains_transfer_start
  933. Transfer a domain from another registrar to your account.
  934. The transfer runs on a domain transfer service you have already purchased.
  935. Before making request, unlock the domain at the current registrar and, if its TLD uses one,
  936. get its authorization code.
  937. A successful response means the transfer has been started. Completion depends on the current
  938. registrar and can be followed with the [transfer list endpoint](#tag/domains-transfer).
  939. If no WHOIS information is provided, default contact information for that TLD will be used.
  940. Before making request, ensure WHOIS information for desired TLD exists in your account.
  941. Use this endpoint to bring domains registered elsewhere into your account.
  942. - **Method**: `POST`
  943. - **Path**: `/api/domains/v1/transfers`
  944. #### domains_whois_change-for
  945. Change WHOIS contact profile for a domain.
  946. Repoints the given contact roles to a new WHOIS profile and submits the change to the registry.
  947. The profile currently assigned to those roles is resolved automatically;
  948. the request fails if the given roles are not all on the same profile today.
  949. Changing transfer sensitive fields on the owner contact starts an IRTP verification.
  950. The change is processed asynchronously.
  951. Use this endpoint to move a registered domain onto different contact information.
  952. - **Method**: `PUT`
  953. - **Path**: `/api/domains/v1/whois/change`
  954. #### domains_whois_set-as-default
  955. Set WHOIS contact profile as default.
  956. The default profile is pre-selected for the TLD it belongs to when registering new domains.
  957. Use this endpoint to avoid picking contact information for every registration.
  958. - **Method**: `PUT`
  959. - **Path**: `/api/domains/v1/whois/default/{whoisId}`
  960. #### domains_whois_unset-default
  961. Unset WHOIS contact profile as default.
  962. The profile itself is kept, it is only no longer pre-selected for its TLD.
  963. Use this endpoint to stop reusing contact information for new registrations.
  964. - **Method**: `DELETE`
  965. - **Path**: `/api/domains/v1/whois/default/{whoisId}`
  966. #### domains_whois_get
  967. Retrieve a WHOIS contact profile.
  968. Use this endpoint to view domain registration contact information.
  969. - **Method**: `GET`
  970. - **Path**: `/api/domains/v1/whois/{whoisId}`
  971. #### domains_whois_delete
  972. Delete WHOIS contact profile.
  973. Use this endpoint to remove unused contact profiles from account.
  974. - **Method**: `DELETE`
  975. - **Path**: `/api/domains/v1/whois/{whoisId}`
  976. #### domains_whois_list
  977. Retrieve WHOIS contact profiles.
  978. Use this endpoint to view available contact profiles for domain registration.
  979. - **Method**: `GET`
  980. - **Path**: `/api/domains/v1/whois`
  981. #### domains_whois_create
  982. Create WHOIS contact profile.
  983. Use this endpoint to add new contact information for domain registration.
  984. The keys required in `whois_details` and `tld_details` depend on the TLD, country and entity type, and can be
  985. country-specific: for Lithuania, for example, `state_lt` and `zip_lt` are required instead of `state` and
  986. `zip`. A 422 response lists every required key that is missing or has an invalid value under
  987. `errors.whois_details`, and under `errors.tld_details` when `tld_details` is sent. Each error states the
  988. key's constraint and, where the key takes a fixed set of values, the allowed values, so all of them can be
  989. corrected in one retry.
  990. - **Method**: `POST`
  991. - **Path**: `/api/domains/v1/whois`
  992. #### domains_whois_usage
  993. Retrieve domain list where provided WHOIS contact profile is used.
  994. Use this endpoint to view which domains use specific contact profiles.
  995. - **Method**: `GET`
  996. - **Path**: `/api/domains/v1/whois/{whoisId}/usage`
  997. ### `hostinger-ecommerce-mcp`
  998. #### changelog_list-entries
  999. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  1000. - **Method**: `custom`
  1001. - **Path**: `custom`
  1002. #### ecommerce_discounts_list
  1003. List a store's discounts. Filter by free text over code and name, or by disabled state.
  1004. Amounts for fixed discounts are integers in the smallest currency unit; percentage
  1005. discounts carry a whole-number value between 1 and 100.
  1006. - **Method**: `GET`
  1007. - **Path**: `/api/ecommerce/v1/stores/{store_id}/discounts`
  1008. #### ecommerce_discounts_create
  1009. Create a discount for a store. Fixed discounts take an amount in the smallest currency
  1010. unit (e.g. $10 is 1000); percentage discounts take a whole-number value between 1 and 100.
  1011. Free-shipping discounts ignore value. Returns the created discount.
  1012. - **Method**: `POST`
  1013. - **Path**: `/api/ecommerce/v1/stores/{store_id}/discounts`
  1014. #### ecommerce_miscellaneous_custom-storefront-setup-instructions
  1015. Retrieve step-by-step setup instructions, formatted as Markdown, for connecting a custom sales
  1016. channel to your store and keeping your catalog, orders, shipping and payments in sync through
  1017. the Ecommerce API.
  1018. - **Method**: `GET`
  1019. - **Path**: `/api/ecommerce/v1/miscellaneous/custom-storefront-instructions`
  1020. #### ecommerce_orders_cancel
  1021. Cancel the order and optionally email the customer. Returns the updated order summary.
  1022. - **Method**: `POST`
  1023. - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/cancel`
  1024. #### ecommerce_orders_fulfil
  1025. Create a fulfilment for the order and attach tracking in one call. Omit items to fulfil
  1026. every remaining unfulfilled item. Returns the updated order summary.
  1027. - **Method**: `POST`
  1028. - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}/fulfill`
  1029. #### ecommerce_orders_list-store
  1030. List a store's orders newest first as summaries. Filter by status, payment or fulfilment
  1031. status, customer email, order number or a free-text query. Amounts are in the smallest
  1032. currency unit. Retrieve a single order for its line items, addresses and fulfilments.
  1033. - **Method**: `GET`
  1034. - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders`
  1035. #### ecommerce_orders_retrieve
  1036. Retrieve one order in full: line items (each with the id the fulfil endpoint needs),
  1037. addresses, the totals breakdown and fulfilments with tracking. Amounts are in the
  1038. smallest currency unit.
  1039. - **Method**: `GET`
  1040. - **Path**: `/api/ecommerce/v1/stores/{store_id}/orders/{order_id}`
  1041. #### ecommerce_payments_enable-manual-method
  1042. Enable a manual payment method so the store can accept orders without an online payment provider.
  1043. - **Method**: `POST`
  1044. - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-methods/manual`
  1045. #### ecommerce_payments_create-provider-connect-link
  1046. Create an onboarding link for connecting a payment gateway to the store. Returns the gateway
  1047. onboarding URL for the merchant to open and a deep-link into the store admin.
  1048. - **Method**: `POST`
  1049. - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-providers/{provider_id}/connect-link`
  1050. #### ecommerce_payments_list-store-providers
  1051. List a store's payment providers, split into providers already connected to the store and
  1052. gateways available to install. Never exposes gateway credentials, secrets, or configuration.
  1053. - **Method**: `GET`
  1054. - **Path**: `/api/ecommerce/v1/stores/{store_id}/payment-providers`
  1055. #### ecommerce_products_create-image-upload-url
  1056. Returns a signed URL to upload a product image to (multipart/form-data POST). Then call the
  1057. attach-image endpoint with the returned object_name to scan and attach it to the product.
  1058. - **Method**: `POST`
  1059. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images/upload-url`
  1060. #### ecommerce_products_delete
  1061. Delete a product and its variants from the store. A subscription product with active
  1062. subscribers is archived instead of deleted so its data stays available.
  1063. - **Method**: `DELETE`
  1064. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}`
  1065. #### ecommerce_products_update
  1066. Update a product's name, description, status, SEO settings or collections. Set status to
  1067. published to make it buyable, draft to hide it, or archived to retire it. SEO settings (title,
  1068. description, slug) left out keep their values. collection_changes adds or removes collections
  1069. without touching the others. Variants, prices and inventory are managed through the variant
  1070. endpoints, not here. Returns the updated product summary.
  1071. - **Method**: `PATCH`
  1072. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}`
  1073. #### ecommerce_products_create-digital
  1074. Create a published digital product with a single variant and an optional external download link.
  1075. - **Method**: `POST`
  1076. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/digital`
  1077. #### ecommerce_products_list
  1078. List a store's products newest first as lean summaries (name, status, thumbnail, variant
  1079. count and price range). Prices are integers in the smallest currency unit and live on
  1080. variants. Filter by status, free text or a set of product ids. Use include=variants to
  1081. embed each product's variants with prices and inventory, and include=media to embed its media.
  1082. - **Method**: `GET`
  1083. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products`
  1084. #### ecommerce_products_create-physical
  1085. Create a published physical product with a single variant priced in the store currency.
  1086. - **Method**: `POST`
  1087. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/physical`
  1088. #### ecommerce_products_upload-and-attach-image
  1089. Fetch a raster image (JPEG, PNG, GIF or WebP, max 15MB) from a URL and attach it to a product in a
  1090. single call. Image downloads require HTTPS on port 443 without embedded credentials. At most one redirect
  1091. is allowed, and its destination must meet the same requirements. Private or reserved network
  1092. destinations, unsupported URLs and longer redirect chains are rejected. The image is virus-scanned
  1093. and validated by content, then stored on the CDN. Set is_thumbnail to make it the product's primary image.
  1094. - **Method**: `POST`
  1095. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/images`
  1096. #### ecommerce_sales-channels_list
  1097. List a store's active sales channels with their full metadata.
  1098. - **Method**: `GET`
  1099. - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels`
  1100. #### ecommerce_sales-channels_create
  1101. Create a sales channel for a store. A "custom" channel is headless: build your own frontend and keep
  1102. your catalog, orders, shipping and payments in sync through the Ecommerce API. A "quick-link" channel
  1103. is a hosted one-page store whose handle is auto-generated.
  1104. - **Method**: `POST`
  1105. - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels`
  1106. #### ecommerce_sales-channels_update
  1107. Update a custom sales channel. The merchant-facing `name` and the public `url`
  1108. (returned as the channel `domain`) can be changed. Pass `null` to clear a value.
  1109. - **Method**: `PATCH`
  1110. - **Path**: `/api/ecommerce/v1/stores/{store_id}/sales-channels/{sales_channel_id}`
  1111. #### ecommerce_shipping_set-store
  1112. Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.
  1113. - **Method**: `POST`
  1114. - **Path**: `/api/ecommerce/v1/stores/{store_id}/shipping`
  1115. #### ecommerce_stores_delete
  1116. Soft-delete a store owned by your account.
  1117. The underlying store data is preserved; only the store is marked as deleted.
  1118. - **Method**: `DELETE`
  1119. - **Path**: `/api/ecommerce/v1/stores/{store_id}`
  1120. #### ecommerce_stores_list
  1121. Retrieve the stores associated with your account.
  1122. - **Method**: `GET`
  1123. - **Path**: `/api/ecommerce/v1/stores`
  1124. #### ecommerce_stores_create
  1125. Create a new store for your account.
  1126. A primary sales channel is created alongside the store.
  1127. - **Method**: `POST`
  1128. - **Path**: `/api/ecommerce/v1/stores`
  1129. #### ecommerce_stores_metadata
  1130. Get a store's readiness metadata: whether payment methods and shipping are configured,
  1131. plus its default currency. Useful to verify prerequisites before building a storefront.
  1132. - **Method**: `GET`
  1133. - **Path**: `/api/ecommerce/v1/stores/{store_id}/metadata`
  1134. #### ecommerce_product-variants_update-in-batch
  1135. Update up to 100 existing variants in place by id — title, SKU, inventory, stock tracking
  1136. and prices. Variants omitted from the request are left untouched. Prices replace the variant's
  1137. existing prices in full. Returns the updated variants.
  1138. - **Method**: `PATCH`
  1139. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/batch`
  1140. #### ecommerce_product-variants_delete
  1141. Delete a single variant from the product.
  1142. - **Method**: `DELETE`
  1143. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants/{variant_id}`
  1144. #### ecommerce_product-variants_list
  1145. List a product's variants, ordered by rank, with their options, prices and inventory.
  1146. Prices are integers in the smallest currency unit and live on variants.
  1147. - **Method**: `GET`
  1148. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants`
  1149. #### ecommerce_product-variants_create
  1150. Add a variant to a product along one or more option dimensions (e.g. Size, Color). Options
  1151. missing from the product are created automatically; provide a value for every option the
  1152. product already has. Prices are integers in the smallest currency unit and default to the
  1153. store currency. Returns the created variant.
  1154. - **Method**: `POST`
  1155. - **Path**: `/api/ecommerce/v1/stores/{store_id}/products/{product_id}/variants`
  1156. ### `hostinger-gpu-mcp`
  1157. #### changelog_list-entries
  1158. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  1159. - **Method**: `custom`
  1160. - **Path**: `custom`
  1161. #### gpu_instances_get
  1162. Retrieve detailed information about a specified GPU instance, including its SSH keys.
  1163. Use this endpoint to follow the instance `status` after creating or deleting it.
  1164. - **Method**: `GET`
  1165. - **Path**: `/api/gpu/v1/instances/{instanceId}`
  1166. #### gpu_instances_delete
  1167. Delete a specified GPU instance.
  1168. The instance is destroyed asynchronously: a successful request returns immediately and the instance
  1169. `status` moves to `destroying`. Deleting fails while the instance is in `created`, `destroying`,
  1170. `destroyed` or `abuse` status, or while another action is in progress on it.
  1171. Use this endpoint to stop billing for a GPU instance you no longer need.
  1172. - **Method**: `DELETE`
  1173. - **Path**: `/api/gpu/v1/instances/{instanceId}`
  1174. #### gpu_exposed-services_delete
  1175. Delete a specified exposed service of a GPU instance.
  1176. The service is removed asynchronously: a successful request returns immediately and the service
  1177. stops being reachable from the internet shortly after.
  1178. Use this endpoint to close public access to a service on your GPU instance.
  1179. - **Method**: `DELETE`
  1180. - **Path**: `/api/gpu/v1/instances/{instanceId}/exposed-services/{exposedServiceId}`
  1181. #### gpu_exposed-services_list
  1182. Retrieve the services exposed on a specified GPU instance.
  1183. A newly created service is listed once it gets its public hostname and external port.
  1184. Use this endpoint to find the public address of services running on your GPU instance.
  1185. - **Method**: `GET`
  1186. - **Path**: `/api/gpu/v1/instances/{instanceId}/exposed-services`
  1187. #### gpu_exposed-services_create
  1188. Expose a service running on a specified GPU instance to the internet.
  1189. The service is exposed asynchronously: a successful request returns immediately, and the service
  1190. appears in the exposed services list once it gets its public hostname and external port.
  1191. Fails when the instance already has the maximum of 4 exposed services.
  1192. Use this endpoint to make an application on your GPU instance publicly reachable.
  1193. - **Method**: `POST`
  1194. - **Path**: `/api/gpu/v1/instances/{instanceId}/exposed-services`
  1195. #### gpu_instances_list
  1196. Retrieve all GPU instances of your account.
  1197. Use this endpoint to view your GPU instances with their status, pool, instance type and OS template.
  1198. - **Method**: `GET`
  1199. - **Path**: `/api/gpu/v1/instances`
  1200. #### gpu_instances_create
  1201. Create a new GPU instance.
  1202. Pick `pool_instance_id` from the pool instance types list and `os_template_id` from the OS templates
  1203. available for that instance type. Your account must have enough credits to run the instance for its
  1204. first hour.
  1205. The instance is created asynchronously: a successful request returns immediately, and the instance
  1206. appears in the instance list while its `status` moves from `created` through `creating` to `running`.
  1207. Use this endpoint to provision GPU compute.
  1208. - **Method**: `POST`
  1209. - **Path**: `/api/gpu/v1/instances`
  1210. #### gpu_instances_metrics
  1211. Retrieve utilisation metrics of a specified GPU instance for the last hour.
  1212. Each data point contains CPU, memory and GPU utilisation, used GPU memory and GPU throughput.
  1213. The list is empty until the instance is provisioned.
  1214. Use this endpoint to monitor GPU instance load.
  1215. - **Method**: `GET`
  1216. - **Path**: `/api/gpu/v1/instances/{instanceId}/metrics`
  1217. #### gpu_catalog_pool-groups
  1218. Retrieve GPU pool groups, ordered by name.
  1219. Each group bundles the pools of one GPU model and lists its currently available pools,
  1220. whether any of them is available and the lowest hourly price, in credits, among its instance types.
  1221. The price is returned even when the group is out of stock.
  1222. Use this endpoint to show which GPU models can be ordered and from what price.
  1223. - **Method**: `GET`
  1224. - **Path**: `/api/gpu/v1/pools/groups`
  1225. #### gpu_catalog_pool-instance-types
  1226. Retrieve the instance types offered by a specified GPU pool, ordered by CPU core count.
  1227. Each instance type describes its CPU, memory and storage, and its hourly price.
  1228. Only instance types that can currently be ordered are returned.
  1229. Use this endpoint to choose the `pool_instance_id` for a new GPU instance.
  1230. - **Method**: `GET`
  1231. - **Path**: `/api/gpu/v1/pools/{poolId}/instances`
  1232. #### gpu_catalog_pool-os-templates
  1233. Retrieve the OS templates that can be installed on a specified GPU pool instance type.
  1234. Use this endpoint to choose the `os_template_id` for a new GPU instance.
  1235. - **Method**: `GET`
  1236. - **Path**: `/api/gpu/v1/pools/{poolId}/instances/{poolInstanceId}/os-templates`
  1237. #### gpu_catalog_pool
  1238. Retrieve all available GPU pools, ordered by name.
  1239. A pool serves GPU accelerators of one model from a single region.
  1240. Use this endpoint to choose a pool before listing its instance types.
  1241. - **Method**: `GET`
  1242. - **Path**: `/api/gpu/v1/pools`
  1243. ### `hostinger-horizons-mcp`
  1244. #### changelog_list-entries
  1245. What's new and what's coming at Hostinger: list entries of the public Hostinger changelog (release notes, product updates, recent changes, new features and improvements) and of the public roadmap (upcoming features not released yet). Released entries come newest first; upcoming items come soonest expected release first. Reads released changelog entries by default; pick upcoming for the roadmap or all for both. Filter by product or date. Each entry has its title, summary, product, URL, status (released or upcoming), and plan when the entry states one; released entries have their date, upcoming items their expected release date when set. Needs no API token.
  1246. - **Method**: `custom`
  1247. - **Path**: `custom`
  1248. #### horizons_websites_clone
  1249. Clone a Hostinger Horizons website into a new website.\n
  1250. Use this tool when the user wants a copy of an existing website, for example to try out
  1251. changes without touching the original.\n
  1252. This tool returns the ID and URL of the newly created copy.
  1253. The original website is left untouched.\n
  1254. To edit the copy, use the `Edit website` tool with the returned website ID, or the user can
  1255. open the provided website URL in Hostinger Horizons interface.
  1256. - **Method**: `POST`
  1257. - **Path**: `/api/horizons/v1/websites/{websiteId}/clone`
  1258. #### horizons_websites_list

Lines 2,001–4,905 are not shown. The link to the file on GitHub has every line.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.