suggest_and_check_domains generates from prefixes, suffixes, compounds and portmanteau blends and then resolves each candidate, so the list you read back has already had the taken names filtered out of it. Availability comes from DNS plus WHOIS rather than a reseller's inventory, which is the honest way to answer the question and also the reason coverage is bounded — list_supported_tlds exists so you can see which extensions the server can actually resolve before you plan a sweep around one.
A domain availability checker exposing 4 tools: verify exact names, sweep one brand across popular TLDs, generate name variations from keywords and check them all, and list the TLDs the server can resolve.
- Exact names verified rather than suggested: check_domains takes the names you already have in mind and resolves each through DNS and WHOIS.
- One brand across the extensions people actually register: check_brand_domains sweeps a single name over a default TLD set running from .com and .net through .io, .dev, .app, .ai and .gg, with more than 30 supported in total including .lol, .wtf and .cool.
- Naming ideas and the availability check in the same call: suggest_and_check_domains builds variations from your keywords using prefixes such as get- and try-, suffixes such as -hq and -lab, keyword compounds and portmanteau blends, then checks each one, bounded by max_variations.
- The coverage stated up front: list_supported_tlds returns every TLD the server can check over WHOIS, grouped by category.
Nothing to supply up front. DNS and WHOIS queries have to be able to leave the machine the server runs on, since availability is decided by those lookups rather than by a registrar's API.
One command — npx mcp-domain-radar