All servers / Web / Unique Domains MCP server
Unique Domains MCP server
MCP server that lets your assistant find the strongest domain names you can still buy, and check any one: is it taken, what nine registrars charge, what similar
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.1.9. Package: @uniquedomains/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (38.6 seconds including download)
- Tools offered: 55
- Last published: 2026-11-17
- Weekly downloads (npm): 1,663
- License: MIT · Direct dependencies: 2
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
ud_get_name2 of 2 parameters describedThe answer for one domain name: status, drop day, price today, registry facts, word facts and similar sales. Use it first when someone asks if a domain name is taken, available or for sale, what it costs to register and to renew, or wants a name idea checked before buying it. The status `not_checked` means no answer: the name may be taken. Pass `name` (such as get.plumbing).
ud_get_name_registry2 of 2 parameters describedThe registry record of one name: dates, registrar, status codes, nameservers, DNSSEC and holder. Use it when someone asks who holds a name, which registrar it is at, when it was registered or when it expires: the record a WHOIS lookup shows. Pass `name` (such as get.plumbing).
ud_get_name_dns2 of 2 parameters describedThe DNS records of one name, with its parking venue. Use it when someone asks whether a name has a website behind it, points anywhere or is parked, and with which parking service. Pass `name` (such as get.plumbing).
ud_get_name_comps2 of 2 parameters describedThe similar-sales aggregate of one name and how many endings its word sold on. Use it when someone asks what similar names sold for, or wants a price reference before buying or selling a name. It answers a count and a median of similar sales, not a value for the name itself. Pass `name` (such as get.plumbing).
ud_get_name_auction2 of 2 parameters describedThe open auction of one name, if any: venue, deadline, bid and the first-year cost. Use it when someone asks whether a name is at auction now, its current bid or its deadline. Pass `name` (such as get.plumbing).
ud_resolve_word2 of 2 parameters describedTurns what a caller typed into the catalog word it names, or up to five candidates. Use it first when a word is misspelled, plural or unclear, to find the catalog word the word tools take. Pass `q` (such as harbors).
ud_list_word_categories1 of 1 parameter describedThe catalog's word categories, by name. Use it when someone wants the word categories to browse or filter by. Its one input, `fields`, is optional.
ud_get_word_endings2 of 2 parameters describedA word's endings: counts, the key endings, and the endings the word is available on and for sale on. Use it when someone is naming a business, product or project and has a word in mind: it shows which endings, such as .com, .io or .ai, are still available or for sale for that word. Its lists `availableOn` and `forSaleOn` name every ending the word is open on, so one call answers the whole question. Pass `word` (such as organic); the other inputs are optional.
ud_get_word_notability2 of 2 parameters describedA word's Wikipedia page and Wikidata entry: title, backlinks, languages and description. Use it when someone asks how widely known a word is as a public topic. Pass `word` (such as harbor).
ud_get_word_market2 of 2 parameters describedA word's sales and auction aggregates. Use it when someone asks how a word sells across endings: counts, prices and auctions. Pass `word` (such as harbor).
ud_list_domains14 of 14 parameters describedOne-word catalog names under filters. Use it when someone looks for domain names they can still buy: one-word names that are available or for sale, filtered by ending, length, price or style, not by topic. Neutral order, one page at a time. Every input is optional; `limit` sets the page size.
ud_get_domain2 of 2 parameters describedOne catalog name, by name or catalog id. Use it when someone asks about one catalog name and holds its name or its catalog id. Pass `nameOrId` (such as get.plumbing).
ud_get_domain_drops4 of 4 parameters describedThe names dropping on one day, counted by ending. Use it when someone asks about expiring or dropping domain names: how many drop on a day, from today to 6 days ahead, and on which endings. Every input is optional; `limit` sets the page size.
ud_list_domain_hacks13 of 13 parameters describedDomain hacks: names whose ending completes the word. Use it when someone wants a short name in which the ending spells the last letters of the word. Every input is optional; `limit` sets the page size.
ud_get_catalog_stats1 of 1 parameter describedCatalog headline totals. Use it when someone asks how many names the catalog tracks and how many are open. Its one input, `fields`, is optional.
ud_list_tlds9 of 9 parameters describedEvery root TLD with its registry facts and launch phases, alphabetical. Use it when someone wants to browse endings by type, country or status; it answers one page at a time. Every input is optional; `limit` sets the page size.
ud_get_tld2 of 2 parameters describedOne TLD in full: registry facts, phases, market, quality band and registrar prices. Use it when someone weighs one ending, such as .ai or .io, or asks what it costs: who runs it, its launch phases, its market and what registrars charge for it, the first year and to renew. Pass `tld` (such as ai).
ud_get_tld_stats3 of 3 parameters describedThe ending's market figures, and with history its daily rows. Use it when someone asks how one ending's market is doing, such as its registrations or sales over time. Pass `tld` (such as ai); the other inputs are optional.
ud_list_tld_phases2 of 2 parameters describedEvery dated launch phase of the ending, chronological. Use it when someone asks when an ending opens, such as its sunrise or general availability dates. Pass `tld` (such as web).
ud_list_tld_changes4 of 4 parameters describedThe ending's public registry changes, newest first. Use it when someone asks what changed at an ending's registry lately. Pass `tld` (such as web); the other inputs are optional.
ud_list_tld_keywords3 of 3 parameters describedThe keywords the catalog attaches to the ending, by type. Use it when someone asks which words or topics an ending suits. Pass `tld` (such as ai); the other inputs are optional.
ud_list_tld_applications10 of 10 parameters describedICANN's 2026 new gTLD round, A to Z, with two simple bands. Use it when someone asks who applied for new endings in the 2026 round, or which strings are contested. Every input is optional; `limit` sets the page size.
ud_list_tld_application_changes5 of 5 parameters describedEvery status or contention change of the round, newest first. Use it when someone asks what moved in the 2026 round lately, such as a withdrawal or a contention change. Every input is optional; `limit` sets the page size.
ud_get_tld_application_string2 of 2 parameters describedOne applied-for string: its applications and its change history. Use it when someone asks about one applied-for ending, such as who applied for it. Pass `string` (such as account).
ud_list_registrars1 of 1 parameter describedThe nine registrars whose daily price lists are compared, in catalog order. Use it when someone asks which registrars the price comparisons cover. Its one input, `fields`, is optional.
ud_list_registrar_prices2 of 2 parameters describedA registrar's list prices, alphabetical by ending. Use it when someone asks what one registrar charges for its endings, first year and renewal. Pass `registrar` (such as namecheap); the other inputs are optional.
ud_list_registrar_changes2 of 2 parameters describedA registrar's confirmed list-price changes, newest first. Use it when someone asks how one registrar's prices changed lately. Pass `registrar` (such as namecheap).
ud_list_tld_prices2 of 2 parameters describedEvery registrar's list price for one ending, with the cheapest and trap marks. Use it when someone asks where one ending is cheapest to register or to renew. Pass `tld` (such as io).
ud_list_price_changes1 of 1 parameter describedConfirmed registrar price changes across the nine, newest first. Use it when someone asks which registrar prices changed lately. Every input is optional.
ud_list_price_traps1 of 1 parameter describedEndings whose cheapest first year renews at a trap price, alphabetical. Use it when someone asks which endings cost much more to renew than to register, or wants to avoid a cheap first year followed by a costly renewal. Every input is optional.
ud_list_venues1 of 1 parameter describedThe parking and marketplace venues with a profile and their rounded footprint. Use it when someone asks which marketplaces or parking services list names, and how many. Its one input, `fields`, is optional.
ud_get_venue2 of 2 parameters describedOne venue's profile with its verified listing terms. Use it when someone asks about one marketplace's or parking service's terms, such as its commission. Pass `id` (such as afternic).
ud_list_iana_registrars4 of 4 parameters describedThe IANA registrar list, by IANA id. Use it when someone asks for accredited registrars beyond the nine compared; it answers one page at a time. Every input is optional; `limit` sets the page size.
ud_get_iana_registrar2 of 2 parameters describedOne IANA registrar by id. Use it when someone holds an IANA registrar number and asks who it is. Pass `id` (such as 1861).
ud_get_market_sales1 of 1 parameter describedThe domain sales pulse as headline aggregates: windows, price bands and the sold-before count. Use it when someone asks how domain names are selling overall: how many sold lately, at what median and in which price bands. Totals, not single sales. Its one input, `fields`, is optional.
ud_list_market_sales_series2 of 2 parameters describedOne sales series by day, week or month, oldest first. Use it when someone wants sales over time, to chart them or compare periods. Pass `kind` (such as week).
ud_list_market_sales_endings1 of 1 parameter describedEach ending's 12-month and 30-day sales figures, alphabetical. Use it when someone asks which endings sell and for how much, such as what .ai or .io names sell for: a count and a median per ending. Its one input, `fields`, is optional.
ud_get_market_sales_lengths1 of 1 parameter describedSales by label length for .com, .ai, .io and .co. Use it when someone asks how the length of a name relates to its sale price. Its one input, `fields`, is optional.
ud_list_market_sales_movers1 of 1 parameter describedUp to ten words whose sales moved over the last 30 days. Use it when someone asks which words are selling more or less lately. Its one input, `fields`, is optional.
ud_get_market_sales_word2 of 2 parameters describedOne word's sales market over 12 months: count, median, endings sold on and the latest sale's month. Use it when someone asks how one word has sold over the last year. Pass `word` (such as hive).
ud_get_market_auctions1 of 1 parameter describedToday's domain auctions by venue, ending and length, the next seven days and the tracked counts. Use it when someone asks how many domain names are at auction or closing today, by venue, ending and length. Totals, not a list of names. Its one input, `fields`, is optional.
ud_list_market_auctions_sample1 of 1 parameter describedThe day's fixed sample of up to 20 single-word names at auction, by deadline. Use it when someone asks what is at auction today or wants auction names to look at. A fixed daily sample of single-word names, not every auction. Its one input, `fields`, is optional.
ud_list_market_auction_venues1 of 1 parameter describedThe seven auction venues with their verified rules and today's counts. Use it when someone asks how an auction venue works, or how many auctions it runs today. Its one input, `fields`, is optional.
ud_list_trends7 of 7 parameters describedEvery published trend with its latest edition figures and its first and last edition day. Use it when someone looks for rising topics to name a project after; it answers one page at a time. Every input is optional; `limit` sets the page size.
ud_get_trend2 of 2 parameters describedOne trend: its latest row, its head words, its figures at every edition and its observations. Use it when someone asks about one trend: how it grew and its key words. Pass `slug` (such as ambient-lights).
ud_list_trend_categories1 of 1 parameter describedThe trend categories, to narrow the trends by. Use it when someone wants trends from one field only, such as business or health. Its one input, `fields`, is optional.
ud_list_events4 of 4 parameters describedThe industry events of one month, in date order, then the events still without a date. Use it when someone asks about domain or internet industry events in a month. Every input is optional.
ud_get_event2 of 2 parameters describedOne industry event with its organizer, location and description. Use it when someone asks for the details of one event. Pass `slug` (such as registrar-day-afnic-2027).
ud_get_agenda5 of 5 parameters describedThe whole public agenda of one month: industry events, TLD launch phases and registry changes. Use it when someone asks what happens in a month: events, ending launches and registry changes. Every input is optional.
ud_get_latest_edition2 of 2 parameters describedThe latest daily edition of Business Ideas or Trending Domains: trends with open names, for founders or for investors. Use it when someone wants name ideas for a new business, or names to buy around rising topics; it carries the edition's open names only, and at most 20 trends while `trendCount` counts the whole edition. Pass `persona` (such as founder).
ud_get_edition3 of 3 parameters describedOne dated daily edition of Business Ideas or Trending Domains: founders read the first, investors the second. Use it when someone asks about a past day's edition. Before 2026-11-10 a day may hold the investors' edition only, which founders read too: the answer then says `investor`. Pass `persona` (such as founder) and `date` (such as 2026-11-10).
ud_get_meta_enums1 of 1 parameter describedEvery list of values the answers use, such as statuses, venues and bands. Use it when an answer holds a code and someone needs its meaning. An auction answer names its own venue on each row, which may be one this list leaves out. Its one input, `fields`, is optional.
ud_list_meta_datasets1 of 1 parameter describedThe free GitHub datasets that hold the same rows as these answers. Use it when someone wants the data in bulk, as files. Its one input, `fields`, is optional.
ud_list_meta_trademark_classes1 of 1 parameter describedThe 45 Nice classes a trademark is filed under. Use it when a trademark answer names a class number and someone needs what it covers. Its one input, `fields`, is optional.
ud_get_meta_providers1 of 1 parameter describedRegistrar identities and the auction venue and parking service catalogs. Use it when someone needs the registrars, auction venues and parking services an answer may name. An auction answer names its own venue on each row, which may be one this list leaves out. Its one input, `fields`, is optional.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.