Home / MCP registry index / domains.unique/mcp-server

Unique.domains

domains.unique/mcp-server in the official MCP registry. Endpoint https://mcp.unique.domains/mcp. Source: github.com/UniqueDomains/mcp-server.

The registry describes it as: Domain status, WHOIS records, nine registrars' daily prices, renewal traps and auctions. No key.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http unique https://mcp.unique.domains/mcp

{
  "mcpServers": {
    "unique": {
      "url": "https://mcp.unique.domains/mcp"
    }
  }
}

code --add-mcp '{"name":"unique","type":"http","url":"https://mcp.unique.domains/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

ud_get_name ud_get_name_registry ud_get_name_dns ud_get_name_comps ud_get_name_auction ud_resolve_word ud_list_word_categories ud_get_word_endings ud_get_word_notability ud_list_domains ud_get_domain ud_get_domain_drops ud_list_domain_hacks ud_get_catalog_stats ud_list_tlds ud_get_tld ud_get_tld_stats ud_list_tld_phases ud_list_tld_changes ud_list_tld_keywords ud_list_tld_applications ud_list_tld_application_changes ud_get_tld_application_string ud_list_registrars ud_list_registrar_prices ud_list_registrar_changes ud_list_price_changes ud_list_price_traps ud_list_venues ud_get_venue ud_list_iana_registrars ud_get_iana_registrar ud_get_market_sales ud_list_market_sales_series ud_list_market_sales_endings ud_get_market_sales_lengths ud_list_market_sales_movers ud_get_market_auctions ud_list_market_auctions_sample ud_list_market_auction_venues ud_list_trends ud_get_trend ud_list_trend_categories ud_list_events ud_get_event ud_get_agenda ud_get_latest_edition ud_get_edition ud_get_meta_enums ud_get_meta_freshness ud_list_meta_datasets ud_list_meta_trademark_classes ud_get_meta_providers

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-09): 0f24c905d1133af3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/domains-unique-mcp-server/badge.svg)](https://lazaretto.dev/mcp-registry/domains-unique-mcp-server)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.