DomainKits

Newly Registered Domains Search

nrds

Read-onlyIdempotent

Search newly registered domains from the last 60 days by keyword, or browse a single TLD without a keyword (browsing requires a registered account). Covers generic TLDs plus these country-code TLDs: .ai, .io, .co, .si, .sh, .so, .cc, and .br, .mx, .cl, .gg, .id, .my including their second-level registrations such as .com.br, .com.mx, .co.id and .com.my (tld 'br' returns the whole .br family, 'com.br' returns that suffix alone); government, military, education and non-profit categories are not included. Which country-code TLDs you can see depends on your plan; asking for one outside it returns a message saying so. Filter by recency, registration term, length, character set, and sale status; returns the cross-TLD count for each name. New registrations are folded in continuously, typically 15 to 20 minutes after registration. Dates here are day-level, not clock times; when you need the exact registration time, use nrds_live.

Related tools: nrds_live, whois, dns, ns_reverse, typosquat

Input Schema

TableJSON Schema

Name	Required	Description
`tld`	No	Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A family country code ('br', 'mx', 'cl', 'gg', 'id', 'my') covers all of its second-level registrations.
`page`	No	Page number for pagination
`sort`	No	Sort order
`type`	No	Character set filter
`length`	No	Domain name length filter
`period`	No	Registration term length in years
`exclude`	No	Negative keywords to exclude
`keyword`	No	Search term (min 2 chars). Substring matching applies at every length, including 2-character terms.
`has_sale`	No	Filter to domains listed for sale
`position`	No	Keyword placement in domain name. Default is 'all' (substring match).
`no_hyphen`	No	Exclude hyphenated domains
`no_number`	No	Exclude domains containing numbers
`days_range`	No	Registration recency
`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. Matches the prefix_tld_count field in results. Domains first seen only hours ago (live rows) carry a count of 1.

Output Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'"New value: +"Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'. A family country code ('br', 'mx', 'cl', 'gg', 'id', 'my') covers all of its second-level registrations."

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / tld / description

Previous value: -"Filter by TLD (e.g., 'com', 'ai', 'io')"New value: +"Filter by TLD, e.g. 'com', 'ai', or a second-level suffix such as 'com.br'"

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."

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. Matches the prefix_tld_count field in results. Domains first seen only hours ago (live rows) carry a count of 1.",
+  "type": "string"
+}

Changed2 schema fields changedAug 21, 2026

changedInput schema / properties / keyword / description

Previous value: -"Search term (min 2 chars). IMPORTANT: 2-character keywords match the START of the name only; 'contain' and 'end' are unavailable at this length and total_found will exclude mid-name matches. Use 3+ characters for true substring matching."New value: +"Search term (min 2 chars). Substring matching applies at every length, including 2-character terms."

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name. Default is 'all' (substring match). Ignored when keyword is 2 characters (always start)."New value: +"Keyword placement in domain name. Default is 'all' (substring match)."

Changed2 schema fields changedAug 17, 2026

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name. Default is 'contain'. Ignored when keyword is 2 characters (always start)."New value: +"Keyword placement in domain name. Default is 'all' (substring match). Ignored when keyword is 2 characters (always start)."

changedInput schema / properties / position / enum

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

Changed2 schema fields changedAug 13, 2026

changedInput schema / properties / keyword / description

Previous value: -"Search term (min 2 chars)"New value: +"Search term (min 2 chars). IMPORTANT: 2-character keywords match the START of the name only; 'contain' and 'end' are unavailable at this length and total_found will exclude mid-name matches. Use 3+ characters for true substring matching."

changedInput schema / properties / position / description

Previous value: -"Keyword placement in domain name"New value: +"Keyword placement in domain name. Default is 'contain'. Ignored when keyword is 2 characters (always start)."

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 establish read-only/idempotent/non-destructive, but the description adds substantial context: the 60-day window, which ccTLDs and second-level registrations are covered, that categories like government/education are excluded, that plan limits produce an explanatory message rather than an error, and the 15-20 minute ingestion latency. This is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Front-loaded with purpose and scope, and every sentence carries information (coverage, exclusions, latency, sibling routing). It is a dense single block, however, and the TLD enumeration is lengthy where a compact list or structure would read faster.

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?

For a 15-parameter tool with full schema coverage, an output schema and rich annotations, the description supplies everything needed to call it correctly: scope, coverage limits, account/plan constraints, data freshness and the sibling to use for exact timestamps. Return values need not be described since an output schema exists.

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 7 of 15 parameters carry enums, so the schema already documents each filter. The description largely restates the same filter set and the tld family behavior that the schema's tld description already explains, adding little beyond it; baseline 3 applies.

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?

States a specific verb and resource ('Search newly registered domains from the last 60 days') plus the alternate browse mode, and explicitly contrasts itself with nrds_live. An agent can tell it apart from siblings like nrds_live, whois and dns without opening a schema.

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?

Gives clear routing ('when you need the exact registration time, use nrds_live') and a real prerequisite ('browsing requires a registered account'), plus plan-dependent TLD visibility. It names the key alternative with its condition but does not say when this tool should be avoided versus the other domain siblings (whois, dns, typosquat) beyond the related-tools list.

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.

Newly Registered Domains Search

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources