Server providing Argo CD integration for MCP clients.
Nothing to run from here
Hostinger Api is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
17k
downloads a day
local
runs on your machine
106k
downloads in 30d
What it does
MCP server for Hostinger API
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user hostinger-api-mcp '--' npx -y @hostinger/mcp
# 2 — ask your agent for something these tools do
# hosting_deployWordpressPlugin, hosting_listJsDeployments, hosting_showJsDeploymentLogs and 197 more
Hostinger Api costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
hostinger1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Hostinger Api as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user hostinger-api-mcp '--' npx -y @hostinger/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take HOSTINGER_API_TOKEN (Hostinger API token. Optional — when unset, the server falls back to interactive OAuth sign-in.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
200 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment. Upload credentials are generated and used internally — do not call a separate upload-url endpoint or upload the files yourself, this tool does it end-to-end.
No parameter schema on file.
List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.
No parameter schema on file.
Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
No parameter schema on file.
Returns the list of cron jobs configured for the specified account, including their schedule and command.
No parameter schema on file.
Creates a cron job for the specified account from a schedule expression and a command. Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output.
No parameter schema on file.
Permanently deletes the cron job identified by its uid. The uid is returned by the list cron jobs endpoint.
No parameter schema on file.
Returns the output captured from the last execution of the cron job identified by its uid. The uid is returned by the list cron jobs endpoint.
No parameter schema on file.
Changes the password for the specified database user. The database name must be the full name returned by the list databases endpoint. The password must also be updated in any website configuration that uses this database.
No parameter schema on file.
Returns a paginated list of databases for the specified account. Use the domain and is_assigned filters to find databases assigned to a specific domain.
No parameter schema on file.
Creates a database with a database user and password for the specified account. The database name and user are automatically prefixed with the account username when needed.
No parameter schema on file.
Permanently deletes a database and its remote connections. The database name must be the full name returned by the list databases endpoint.
No parameter schema on file.
Allows a remote host to connect to the specified database. Provide an IPv4/IPv6 address, or \
No parameter schema on file.
Permanently removes a remote-access rule, revoking the given host
No parameter schema on file.
Returns the remote-access rules for the specified account: the remote hosts (IPv4/IPv6 addresses, or \
No parameter schema on file.
Repairs corrupted database tables asynchronously. Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint.
No parameter schema on file.
Returns a direct sign-on link to phpMyAdmin for the specified database. Use this when a visual database interface is needed for SQL queries, imports, exports, or table management. The database name must be the full name returned by the list databases endpoint.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve all parked or alias domains created under the selected website. Use this endpoint to inspect parked domain configuration for a specific website, including the parent domain and root directory assigned to each parked domain.
No parameter schema on file.
Create a parked or alias domain for the selected website. Provide a domain name or IP address to park on the website so it serves the same content as the parent domain.
No parameter schema on file.
Delete an existing parked or alias domain from the selected website. Use this endpoint to remove parked domains that are no longer needed.
No parameter schema on file.
Retrieve all subdomains created under the selected website. Use this endpoint to inspect subdomain configuration for a specific website, including the parent domain and root directory assigned to each subdomain.
No parameter schema on file.
Create a new subdomain for the selected website. Provide a subdomain prefix and, optionally, a custom directory or the website public directory to use as the subdomain root.
No parameter schema on file.
Delete an existing subdomain from the selected website. Use this endpoint to remove subdomains that are no longer needed.
No parameter schema on file.
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
No parameter schema on file.
Generate a file browser upload URL with authentication credentials for uploading files directly to a website
No parameter schema on file.
List files and directories under a website
No parameter schema on file.
Get a single file
No parameter schema on file.
Start a Node.js build process using files already present on the website
No parameter schema on file.
Resets all PHP extensions of the website to their default state. Use it to recover from extension conflicts or restore the original configuration.
No parameter schema on file.
Returns the full phpinfo page (HTML) for the website. Use it to debug PHP issues or inspect the complete PHP environment of the website.
No parameter schema on file.
Enables or disables PHP extensions (modules) for the website. Use the Get PHP details endpoint to check the current extension states before changing them.
No parameter schema on file.
Changes the PHP version of the website. Use the Get PHP details endpoint to see the versions available for the website.
No parameter schema on file.
Returns a paginated list of redirects configured for the selected website.
No parameter schema on file.
Creates a redirect from a URL on the selected website to another URL or IP address.
No parameter schema on file.
Permanently deletes the redirect identified by its source URL. Pass the from value exactly as returned by the list redirects endpoint.
No parameter schema on file.
Deploy a static application from an archive file. WARNING: this overwrites the website
No parameter schema on file.
Get a single automation with the counts of contacts that entered it, are moving through it, finished it or failed on the way. This describes the automation itself. To see the workflow it runs, use the steps endpoint.
No parameter schema on file.
Get the workflow of an automation as a flat list of steps. The steps form a tree rather than a straight line: follow parent_uuid to reconstruct the branches, and use step_order to order the steps that share a parent. An automation with no steps yet returns an empty list.
No parameter schema on file.
Get a single campaign with its sender, subject, template reference, targeting and delivery progress. This describes how the campaign was set up and how far it has got. For opens, clicks and unsubscribes use the campaign statistics endpoint.
No parameter schema on file.
Get the performance of a campaign: delivery, opens, clicks and unsubscribes, with the matching rates. Every count is unique contacts rather than raw events, so a contact who opens the same email five times is counted once.
No parameter schema on file.
Delete a contact with the specified UUID. This endpoint permanently removes a contact from the email marketing system. Deprecated. This endpoint cannot target a profile, so it always falls back to the client
No parameter schema on file.
Delete a custom contact field. Every value contacts hold for the field is deleted with it, and for the choice types so are its options. The contacts themselves are not affected.
No parameter schema on file.
Get the custom contact fields defined in a profile. Custom fields let you store your own attributes on contacts. The returned uuids are what you pass to the contact update endpoint to set values, and choice fields also list the options available to pick from.
No parameter schema on file.
Define a new custom contact field in a profile. The slug is derived from the label and, like the field type, cannot be changed later. Use the returned uuid to set values on contacts.
No parameter schema on file.
Get a list of all contact groups. This endpoint returns a list of contact groups that can be used to organize contacts.
No parameter schema on file.
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.
No parameter schema on file.
Get the full details of a single contact. Alongside the contact
No parameter schema on file.
Permanently delete a contact from a profile. The contact is removed together with its custom field values and tag assignments.
No parameter schema on file.
Update a contact
No parameter schema on file.
Get a paginated list of contacts belonging to a profile. Contacts can be filtered by subscription status, by tag, and by an email search term. The meta.total field of the response is the number of contacts matching the filters, so calling this endpoint without filters gives the profile
No parameter schema on file.
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.
No parameter schema on file.
Get a list of all contact segments. This endpoint returns a list of contact segments that can be used to organize contacts. Deprecated. This endpoint cannot target a profile, so it always falls back to the client
No parameter schema on file.
Count the contacts currently matching a segment without listing them. Cheaper than paging through the segment contacts endpoint when only the size is needed.
No parameter schema on file.
Retrieve contacts associated with a specific segment for a given profile. This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID, scoped to a specific profile.
No parameter schema on file.
Get a single segment of a profile, including the conditions that define it. To retrieve the contacts currently matching those conditions, use the segment contacts endpoint instead.
No parameter schema on file.
Delete a segment. Only the segment definition is removed. The contacts that matched it are left untouched.
No parameter schema on file.
List every attribute a segment condition can filter on, with the operators each attribute accepts, the value format they expect and, where the value is constrained, the allowed values. The list is profile specific: it includes the profile
No parameter schema on file.
Get a paginated list of the segments defined in a profile. Each entry carries the number of contacts currently matching it, which is recalculated on read rather than stored. Use count_type to count either every matching contact or only the subscribed ones.
No parameter schema on file.
Create a segment in a profile. A segment is a saved set of conditions rather than a fixed list, so its membership changes as contacts change. Creating one does not modify any contact.
No parameter schema on file.
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. Deprecated. This endpoint cannot target a profile, so it always falls back to the client
No parameter schema on file.
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. Deprecated. This endpoint cannot target a profile, so it always falls back to the client
No parameter schema on file.
Assign a tag to a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Assigning a tag the contact already carries succeeds without duplicating it.
No parameter schema on file.
Remove a tag from a single contact. Unlike the bulk endpoint this is applied immediately rather than queued. Neither the tag nor the contact is deleted.
No parameter schema on file.
Assign a tag to many contacts at once. Pass contact_uuids to target specific contacts, or all_contacts to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. Contacts that already carry the tag are left alone.
No parameter schema on file.
Remove a tag from many contacts at once. Pass contact_uuids to target specific contacts, or all_contacts to target every contact in the profile. The work is queued, so a success response means it was accepted rather than finished. The tag itself and the contacts are not deleted.
No parameter schema on file.
Delete a tag and remove it from every contact carrying it. The contacts themselves are not deleted. This is idempotent: deleting a tag that does not exist in the profile still succeeds.
No parameter schema on file.
Rename a tag. The contacts assigned to the tag are unaffected. Names are unique within a profile, so renaming a tag to a name that is already taken is rejected.
No parameter schema on file.
Get all tags defined in a profile. Tags are the way contacts are grouped in Reach, and can be used to filter the contact list or to build segments.
No parameter schema on file.
Create tags in a profile. Names that already exist in the profile are not duplicated: the existing tag is returned instead, so the call is safe to repeat. Every tag in the request is returned, whether it was created now or already existed.
No parameter schema on file.
Get a single form with the URL of its hosted template and the tags it applies to the contacts it captures. There is no ready-made embed snippet in the response - either serve the template HTML yourself or build your own embed around the form uuid.
No parameter schema on file.
Permanently delete a form together with its template. A form that has already captured submissions cannot be deleted, so that the contacts it collected are never silently discarded - pause the form instead to stop it collecting new ones. Views alone do not block deletion.
No parameter schema on file.
Get a paginated list of the signup forms in a profile. Each form carries a reference to the template that renders it. Get the form details for a directly usable template URL and for the tags the form puts on the contacts it captures.
No parameter schema on file.
Retrieve the DNS configuration status for a profile
No parameter schema on file.
This endpoint returns all profiles available to the client, including their basic information.
No parameter schema on file.
Retrieve all available data centers. Use this endpoint to view location options before deploying VPS instances.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Deactivate a firewall for a specified virtual machine. Use this endpoint to remove firewall protection from VPS instances.
No parameter schema on file.
Retrieve firewall by its ID and rules associated with it. Use this endpoint to view specific firewall configuration and rules.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve all available firewalls. Use this endpoint to view existing firewall configurations.
No parameter schema on file.
Create a new firewall. Use this endpoint to set up new firewall configurations for VPS security.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve post-install script by its ID. Use this endpoint to view specific automation script details.
No parameter schema on file.
Update a specific post-install script. Use this endpoint to modify existing automation scripts.
No parameter schema on file.
Delete a post-install script from your account. Use this endpoint to remove unused automation scripts.
No parameter schema on file.
Retrieve post-install scripts associated with your account. Use this endpoint to view available automation scripts for VPS deployment.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve public keys associated with your account. Use this endpoint to view available SSH keys for VPS authentication.
No parameter schema on file.
Add a new public key to your account. Use this endpoint to register SSH keys for VPS authentication.
No parameter schema on file.
Retrieve detailed information about a specific OS template for virtual machines. Use this endpoint to view specific template specifications before deployment.
No parameter schema on file.
Retrieve available OS templates for virtual machines. Use this endpoint to view operating system options before creating or recreating VPS instances.
No parameter schema on file.
Retrieve detailed information about a specific action performed on a specified virtual machine. Use this endpoint to monitor specific VPS operation status and details.
No parameter schema on file.
Retrieve public keys attached to a specified virtual machine. Use this endpoint to view SSH keys configured for specific VPS instances.
No parameter schema on file.
Retrieve backups for a specified virtual machine. Use this endpoint to view available backup points for VPS data recovery.
No parameter schema on file.
Reset hostname and PTR record of a specified virtual machine to default value. Use this endpoint to restore default hostname configuration for VPS instances.
No parameter schema on file.
Retrieve detailed information about a specified virtual machine. Use this endpoint to view comprehensive VPS configuration and status.
No parameter schema on file.
Retrieve all available virtual machines. Use this endpoint to view available VPS instances.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Create or update a PTR (Pointer) record for a specified virtual machine. Use this endpoint to configure reverse DNS lookup for VPS IP addresses.
No parameter schema on file.
Delete a PTR (Pointer) record for a specified virtual machine. Once deleted, reverse DNS lookups to the virtual machine
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Set root password for a specified virtual machine. Requirements for password are same as in the [recreate virtual machine endpoint](/#tag/vps-virtual-machine/POST/api/vps/v1/virtual-machines/{virtualMachineId}/recreate). Use this endpoint to update administrator credentials for VPS instances.
No parameter schema on file.
Setup newly purchased virtual machine with initial state. Use this endpoint to configure and initialize purchased VPS instances.
No parameter schema on file.
Retrieve snapshot for a specified virtual machine. Use this endpoint to view current VPS snapshot information.
No parameter schema on file.
Delete a snapshot of a specified virtual machine. Use this endpoint to remove VPS snapshots.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Enable or disable an AI option for the Hostinger Tools plugin on the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Trigger a background scan to detect WordPress installations for the account. This operation is asynchronous: a successful response only means the scan has been queued. Poll GET /api/hosting/v1/wordpress/installations to fetch the detected installations once the scan completes.
No parameter schema on file.
Import WordPress website to the specified domain. WARNING: this overwrites the website
No parameter schema on file.
List available WordPress core updates for the specified installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Show the WordPress core version for the specified installation, along with known vulnerabilities affecting it. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Purge the LiteSpeed Cache for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Show the LiteSpeed Cache status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Create temporary auto-login links for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Show the maintenance mode status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Enable or disable maintenance mode for the specified WordPress installation, based on the enabled flag. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Show the Memcached object cache status for the specified WordPress installation. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Activate or deactivate the Memcached object cache for the specified WordPress installation, based on the enabled flag. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Deploy a WordPress plugin from an already uploaded directory. This endpoint allows you to deploy a WordPress plugin that has been uploaded to the website
No parameter schema on file.
List plugins recommended for installation on a WordPress installation that are not yet installed. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
List plugins installed on a WordPress installation, including their status, available updates and known vulnerabilities. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
Search the WordPress.org plugin directory for plugins available to install. Use the returned slug values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
No parameter schema on file.
List curated plugin suggestions grouped by website type. Use the returned slug values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/plugins/install.
No parameter schema on file.
Check whether WooCommerce is installed on any WordPress installation of a domain. Optionally filter by domain to scope the check.
No parameter schema on file.
Deploy a WordPress theme from an already uploaded directory. This endpoint allows you to deploy a WordPress theme that has been uploaded to the website
No parameter schema on file.
List themes installed on a WordPress installation, including their status, available updates and known vulnerabilities. Provide the WordPress installation (software) identifier in the path. It can be obtained from GET /api/hosting/v1/wordpress/installations (the id field).
No parameter schema on file.
List WordPress themes available to install. Use the returned slug values with POST /api/hosting/v1/accounts/{username}/wordpress/{software}/themes/install.
No parameter schema on file.
Deploy a node-static Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website
No parameter schema on file.
Deploy a PHP (or other non-build) Agency Plan (h5g) website from an archive file. WARNING: this overwrites the website
No parameter schema on file.
Changes the primary domain for an Agency Plan website. Provide the current domain in the path and the new domain in the request body. Set domain to null to revert to the temporary domain.
No parameter schema on file.
Links a domain to the specified Agency Plan website so it can serve traffic for that domain.
No parameter schema on file.
Returns a paginated list of domains associated with Agency Plan websites accessible to the authenticated client. Use the website_uuids filter to narrow results to specific websites.
No parameter schema on file.
Generate a file browser upload URL with authentication credentials for uploading files to an Agency Plan website
No parameter schema on file.
Imports an Agency Plan website from an already-uploaded archive. Upload the archive to the website
No parameter schema on file.
Returns aggregated disk and inode usage for the Agency Plan order over the selected time frame, plus the plan quotas. Figures cover the whole order account. Values may be up to one hour stale. CPU, memory, and process usage are on the resource-usage-metrics endpoint.
No parameter schema on file.
Returns a paginated list of Agency Plan orders accessible to the authenticated client.
No parameter schema on file.
Lists every PHP extension available to an Agency Plan website and whether it is currently enabled.
No parameter schema on file.
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 \
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Returns the current status of an Agency Plan website setup started via the setups endpoint. Poll this endpoint using the setup_uuid returned from the provisioning request until status becomes completed, at which point website_uid identifies the new website.
No parameter schema on file.
Clears cache for all domains associated with an Agency Plan website, including its preview domain. This operation clears all cache types for the website.
No parameter schema on file.
Returns a paginated list of cron jobs configured for an Agency Plan website. Each entry includes the schedule expression and the command executed on that schedule.
No parameter schema on file.
Creates a cron job for an Agency Plan website from a schedule expression and a command. Returns the created cron job, including its uuid, which is required to delete the cron job.
No parameter schema on file.
Permanently deletes the cron job identified by its uuid from an Agency Plan website. The operation is idempotent: deleting a cron job that does not exist succeeds without error.
No parameter schema on file.
Returns a paginated list of MySQL databases created for an Agency Plan website. Each entry includes the database
No parameter schema on file.
Creates a MySQL database with a dedicated user for an Agency Plan website. The database name, username, and password must all be provided by the caller.
No parameter schema on file.
Permanently deletes a MySQL database and all its data from an Agency Plan website, including its users. The operation is idempotent: deleting a database that does not exist succeeds without error.
No parameter schema on file.
Creates a user for an existing database on an Agency Plan website. Each database supports a single non-system user; creating a user for a database that already has one fails.
No parameter schema on file.
Permanently deletes a database user from an Agency Plan website database, revoking all access it had. The operation is idempotent: deleting a user that does not exist succeeds without error.
No parameter schema on file.
Retrieves detailed information about a specific Agency Plan website, including configuration, status, metadata, hosting plan details, and resource quotas.
No parameter schema on file.
Permanently deletes an Agency Plan website. Deletion is processed asynchronously: the website is immediately transitioned to a deleting state and the underlying server resources are removed in the background.
No parameter schema on file.
Lists active and recently completed asynchronous processes for an Agency Plan website. Each process has a unique ID (for tracking), a type, and a status (running, completed, failed). Poll this endpoint after initiating async operations (SSL setup, backups, cloning) to track progress.
No parameter schema on file.
Changes the installed WordPress core version on an Agency Plan website to one of the versions available for installation.
No parameter schema on file.
Returns the current WordPress settings for an Agency Plan website: installed core version, LiteSpeed Cache plugin status, object cache status, and maintenance mode status.
No parameter schema on file.
Lists the WordPress core versions available for installation on an Agency Plan website.
No parameter schema on file.
Retrieve a list of pending and completed domain verifications.
No parameter schema on file.
Suggest available domain names based on a free-text description of your project. Suggestions are generated by an AI model, so they differ between calls. Endpoint has rate limit of 90 requests per minute. Use this endpoint to find a domain name when you only know what the website is about.
No parameter schema on file.
Suggest available domain names based on a domain name you already have in mind. Suggestions are generated by an AI model, so they differ between calls. Endpoint has rate limit of 90 requests per minute. Use this endpoint when the domain you wanted is taken and you need close alternatives.
No parameter schema on file.
Retrieve domain forwarding data. Use this endpoint to view current redirect configuration for domains.
No parameter schema on file.
Update domain forwarding configuration. Use this endpoint to modify existing redirect configuration for domains.
No parameter schema on file.
Delete domain forwarding data. Use this endpoint to remove redirect configuration from domains.
No parameter schema on file.
Create domain forwarding configuration. Use this endpoint to set up domain redirects to other URLs.
No parameter schema on file.
Retrieve a pending IRTP verification for a domain. Both the old and new registrant must confirm it before the WHOIS change takes effect. Use this endpoint to check the status of a WHOIS change awaiting registrant confirmation.
No parameter schema on file.
Cancel a pending IRTP verification. Use this endpoint to back out of a WHOIS change that is stuck waiting on registrant confirmation, for example when the confirmation email cannot be received, without waiting out the 5-day expiry.
No parameter schema on file.
Retrieve the incoming move for a specified domain. Returns 404 when no account is moving this domain to you. Use this endpoint to check whether a domain addressed to you is still waiting to be accepted.
No parameter schema on file.
Reject an incoming move for a specified domain. The domain stays in the account which initiated the move. Moves you have already accepted cannot be rejected anymore. Use this endpoint to decline a domain you do not want to take over.
No parameter schema on file.
Retrieve all domains other Hostinger accounts are moving to your account. Moves of every status are returned, including the ones which already completed. Use this endpoint to find domains waiting for you to accept them.
No parameter schema on file.
Retrieve the outgoing move for a specified domain. Returns 404 when the domain has no move in progress. Use this endpoint to track the status of a move you have initiated for a single domain.
No parameter schema on file.
Cancel an outgoing move for a specified domain. The move can only be cancelled while the receiving account has not accepted it yet. The domain stays in your account. Use this endpoint to withdraw a move you no longer want to complete.
No parameter schema on file.
Retrieve all domains you are moving to other Hostinger accounts. Only moves which have not completed yet are returned. Use this endpoint to track moves you have initiated and the accounts they are addressed to.
No parameter schema on file.
Retrieve the authorization (EPP) code for a specified domain so it can be transferred away from Hostinger to another registrar. Requesting a new code invalidates any code retrieved previously. Use this endpoint to obtain the code required to transfer a domain to another registrar.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve detailed information for specified domain. Use this endpoint to view comprehensive domain configuration and status.
No parameter schema on file.
Retrieve all domains associated with your account. Use this endpoint to view user
No parameter schema on file.
Enable privacy protection for the domain. When privacy protection is enabled, domain owner
No parameter schema on file.
Disable privacy protection for the domain. When privacy protection is disabled, domain owner
No parameter schema on file.
Retrieve renewal information for a specified domain, including its status and current expiration date. Use this endpoint to build renewal automation and expiry monitoring for a single domain.
No parameter schema on file.
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.
No parameter schema on file.
Retrieve the transfer for a specified domain. Use this endpoint to track an incoming or outgoing registrar transfer and its status.
No parameter schema on file.
Retrieve all domain transfers in your portfolio. Use this endpoint to monitor incoming and outgoing registrar transfers across your domains.
No parameter schema on file.
Set WHOIS contact profile as default. The default profile is pre-selected for the TLD it belongs to when registering new domains. Use this endpoint to avoid picking contact information for every registration.
No parameter schema on file.
Unset WHOIS contact profile as default. The profile itself is kept, it is only no longer pre-selected for its TLD. Use this endpoint to stop reusing contact information for new registrations.
No parameter schema on file.
Retrieve a WHOIS contact profile. Use this endpoint to view domain registration contact information.
No parameter schema on file.
Delete WHOIS contact profile. Use this endpoint to remove unused contact profiles from account.
No parameter schema on file.
Retrieve WHOIS contact profiles. Use this endpoint to view available contact profiles for domain registration.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hostinger Api or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 2.16.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings4 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest75e7d0ed8d6339b1ea83b72b9db80e7d8fc4393bf1e1f671b5bafabd7ceaa8dc
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest75e7d0ed8d6339b1
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.16.0. Pin a release below and the command asks for exactly that one.
2.16.0
14 Oct 2026
latestNo release note was published with this version.
2.15.0
14 Oct 2026
No release note was published with this version.
2.13.1
14 Oct 2026
No release note was published with this version.
2.13.0
12 Oct 2026
No release note was published with this version.
2.11.0
9 Oct 2026
No release note was published with this version.
2.9.1
8 Oct 2026
No release note was published with this version.
2.9.0
7 Oct 2026
No release note was published with this version.
2.8.0
6 Oct 2026
No release note was published with this version.
2.7.3
5 Oct 2026
No release note was published with this version.
2.7.0
1 Oct 2026
No release note was published with this version.
2.6.0
30 Sep 2026
No release note was published with this version.
1.63.4
25 Sep 2026
No release note was published with this version.
1.63.3
23 Sep 2026
No release note was published with this version.
1.61.1
17 Sep 2026
No release note was published with this version.
1.60.2
16 Sep 2026
No release note was published with this version.
1.59.0
11 Sep 2026
No release note was published with this version.
1.58.0
9 Sep 2026
No release note was published with this version.
1.57.0
4 Sep 2026
No release note was published with this version.
1.55.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hostinger Api can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.