Catchdoms MCP Server

CatchDoms exposes an **Expired Domains API** and an **MCP (Model Context Protocol) server** that aggregate expired domains from **16 auction

Local serverstdio

What is the Catchdoms MCP MCP server?

CatchDoms exposes an Expired Domains API and an MCP (Model Context Protocol) server that aggregate expired domains from 16 auction platforms (Dynadot, GoDaddy, DropCatch, SnapNames, Catched, Gname, BloomUp, UKBackorder. That is what the catchdoms mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The tools it exposes

The server publishes 4 tools. What each one is for:

  • search_domains — Search for domains with filters. Returns up to 100 results sorted by quality
  • get_domain — The get_domain tool exposed by this server
  • list_filters — Get available filter options with counts — sources, TLDs, and languages
  • get_stats — Get platform statistics — total domains, new today, by source, SEO coverage

What it needs from you

Configuration is passed through the environment: YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Catchdoms MCP's toolset — search_domains, get_domain, list_filters and 1 more — is a fair guide to whether it matches your workflow. It is maintained by sambel; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Catchdoms MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
search_domainsSearch for domains with filters. Returns up to 100 results sorted by quality.
get_domainThe get_domain tool exposed by this server.
list_filtersGet available filter options with counts — sources, TLDs, and languages.
get_statsGet platform statistics — total domains, new today, by source, SEO coverage.

How to install the Catchdoms MCP MCP server

{
  "mcpServers": {
    "catchdoms": {
      "url": "https://catchdoms.com/mcp/catchdoms/free",
      "transport": "sse"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Catchdoms MCP to search domains.
  • Use Catchdoms MCP to get domain.
  • Use Catchdoms MCP to list filters.

Frequently asked questions

It connects Catchdoms MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (search_domains, get_domain, list_filters, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Catchdoms MCP directly.