domains_checkDomainAvailabilityV1
Check availability of domain names across multiple TLDs. Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set with_alternatives to true. TLDs should be provided without leading dot (e.g. com, net, org). Endpoint has rate limit of 10 req...
This record as markdown: /tools/io-github-hostinger-hostinger-api-mcp/domains-checkdomainavailabilityv1.md
What domains_checkDomainAvailabilityV1 does on Hostinger Api
AI agents call domains_checkDomainAvailabilityV1 to retrieve information from Hostinger Api without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tlds | array | Yes | TLDs list |
domain | string | Yes | Domain name (without TLD) |
with_alternatives | boolean | — | Should response include alternatives |
Parameters from the server's own tool schema.
Why domains_checkDomainAvailabilityV1 is rated Low
This tool performs a read-only query against the Hostinger API to check domain name availability. It has no side effects, does not create, modify, delete, or execute any operations. The rate limit (10 requests per minute) and the emphasis on checking before purchase further confirm it is a passive information retrieval tool.
From the tool's definition Tool description states 'Check availability of domain names' and 'verify domain availability before purchase' — these are query operations that retrieve availability status without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
The rule that runs domains_checkDomainAvailabilityV1 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hostinger Api, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domains_checkDomainAvailabilityV1, this is the rule to start with:
domains_checkDomainAvailabilityV1 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hostinger Api, apply this rule, and every domains_checkDomainAvailabilityV1 call is checked against it from then on.
Questions about domains_checkDomainAvailabilityV1
Check availability of domain names across multiple TLDs. Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set with_alternatives to true. TLDs should be provided without leading dot (e.g. com, net, org). Endpoint has rate limit of 10 requests per minute. Use this endpoint to verify domain availability before purchase. It is categorised as a Read tool in the Hostinger Api MCP Server, which means it retrieves data without modifying state.
domains_checkDomainAvailabilityV1 accepts 3 parameters: tlds, domain, with_alternatives. Required: tlds, domain. The full parameter table on this page comes from the server's own tool schema.
Register the Hostinger Api MCP server in PolicyLayer and add a rule for domains_checkDomainAvailabilityV1: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Hostinger Api. Nothing to install.
domains_checkDomainAvailabilityV1 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the domains_checkDomainAvailabilityV1 rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for domains_checkDomainAvailabilityV1. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
domains_checkDomainAvailabilityV1 is provided by the Hostinger Api MCP server (hostinger-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hostinger Api, and thousands of servers like it.
This server
Across the catalogue