DomainKits

Active Domain Search

active

Read-onlyIdempotent

Search active registered domains from a database of more than 360 million names, filtered by keyword, TLD, length, and character set. Covers generic TLDs plus more than 100 country-code TLDs, including second-level registrations such as .com.br, .co.uk and .com.tw (tld 'br' returns the whole .br family, 'com.br' returns that suffix alone). Which country-code TLDs you can see depends on your plan; asking for one outside it returns a message saying so. A market-analysis instrument for keyword distribution and saturation; results are registered domains, not available for registration.

Related: expired, whois, dns.

Input Schema

Name	Required	Description
`tld`	No	Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level registrations ('br' includes 'com.br'). When keyword is omitted, this is the browse target (TLD browse mode requires a registered account).
`page`	No	Page number for pagination
`sort`	No	Sort order
`type`	No	Character set filter
`length`	No	Domain name length filter
`status`	No	Filter by status: 'forsale' for domains listed for sale
`keyword`	No	Brand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account.
`position`	No	Keyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching.
`no_hyphen`	No	Exclude hyphenated domains (true/false)
`no_number`	No	Exclude domains containing numbers (true/false)
`tld_count_max`	No	Maximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.
`tld_count_min`	No	Minimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.

Output Schema

Name	Required	Description
`data`	No
`page`	No
`error`	No	Error message when success is false
`total`	No	Number of results on this page
`success`	Yes
`max_page`	No
`total_found`	No	Total matching results across all pages; the primary metric for comparative analysis

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)"New value: +"Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A two-letter country code also covers its second-level registrations ('br' includes 'com.br'). When keyword is omitted, this is the browse target (TLD browse mode requires a registered account)."

Changed1 schema field changedOct 3, 2026

changedOutput schema / properties / data / items / properties / marketplace / description

Previous value: -"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname. Present only when the domain is listed for sale."New value: +"Sale platform code where the domain is listed: se=Sedo, go=GoDaddy, at=Atom, vn=Venture, pd=PerfectDomain, gn=Gname, hu=HugeDomains. Present only when the domain is listed for sale."

Changed1 schema field changedSep 30, 2026

changedOutput schema / properties / total_found / description

Previous value: -"Total matching results across all pages — primary metric for comparative analysis"New value: +"Total matching results across all pages; the primary metric for comparative analysis"

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / keyword / description

Previous value: -"Brand or industry term (min 2 chars). Omit to use TLD browse mode."New value: +"Brand or industry term (min 2 chars). Omit to use TLD browse mode, which requires a registered account."

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target"New value: +"Filter by TLD (e.g., 'com', 'net', 'org'); when keyword is omitted, this is the browse target (TLD browse mode requires a registered account)"

Changed2 schema fields changedAug 28, 2026

addedInput schema / properties / tld_count_max

Added value: +{
+  "description": "Maximum cross-TLD registration count for the name. Integer 0-10000. See tld_count_min.",
+  "type": "string"
+}

addedInput schema / properties / tld_count_min

Added value: +{
+  "description": "Minimum cross-TLD registration count for the name. Integer 0-10000. Combine with tld_count_max for a range; set both equal for an exact count.",
+  "type": "string"
+}

Changed5 schema fields changedAug 17, 2026

changedInput schema / properties / length / enum

Previous value: -[
-  "<5",
-  "5-10",
-  "11-15",
-  ">15"
-]New value: +[
+  "<5",
+  "5-10",
+  "11-15",
+  "15+"
+]

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."New value: +"Keyword placement in domain name. Default is 'all' (substring match). Unlike the other search tools, this one has no minimum-length restriction on substring matching."

changedInput schema / properties / position / enum

Previous value: -[
-  "start",
-  "end",
-  "middle",
-  "contain"
-]New value: +[
+  "start",
+  "end",
+  "middle",
+  "all"
+]

changedInput schema / properties / status / description

Previous value: -"Filter by status — 'forsale' for domains listed for sale"New value: +"Filter by status: 'forsale' for domains listed for sale"

addedInput schema / properties / status / enum
```
Added value: +[
+  "forsale"
+]
```

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name. Default is 'contain' (substring match)."New value: +"Keyword placement in domain name. Default is 'start' (prefix match) — pass position=contain explicitly for substring matching. Unlike the other search tools, this one has no minimum-length restriction on substring matching."

AddedJul 27, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavioral facts: which ccTLDs are visible depends on the caller's plan, an out-of-plan TLD returns an explanatory message rather than an error, and TLD browse mode requires a registered account. It also clarifies TLD family semantics ('br' vs 'com.br') that affect result scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope statement is front-loaded and each sentence carries information (corpus size, ccTLD nuance, plan gating, use-case framing) with no filler. The ccTLD parenthetical is dense and overlaps slightly with the schema, keeping it just short of ideal economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% parameter coverage, the description need not explain return values. It supplies the missing context an agent needs for a 12-parameter search tool: corpus scope, plan-based visibility limits, and the registered-vs-available distinction.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and 12 of 12 parameters are documented in the schema with enums and defaults. The description's parameter-related content (tld family expansion, keyword-omitted browse mode) largely restates what the schema already says, so it adds little beyond the structured baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search active registered domains') and defines the corpus (360M names, generic plus 100+ ccTLDs). It explicitly distinguishes itself from the availability siblings by stating 'results are registered domains, not available for registration,' so an agent will not confuse it with `available` or `bulk_available`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context of use ('a market-analysis instrument for keyword distribution and saturation') and rules out the availability use case, plus names related tools (expired, whois, dns). It stops short of saying when to prefer each of those relatives over this tool, so the routing guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DomainKits tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.