What is the key difference between CatchDoms — Expired Domains API and MCP Uptime Kuma?

CatchDoms — Expired Domains API belongs to the Monitoring category with cloud HTTP/SSE execution, while MCP Uptime Kuma belongs to the Monitoring category with local stdio execution.

How do I install CatchDoms — Expired Domains API or MCP Uptime Kuma in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are CatchDoms — Expired Domains API and MCP Uptime Kuma free or paid?

CatchDoms — Expired Domains API operates under a Freemium model (API Key required). MCP Uptime Kuma operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

CatchDoms — Expired Domains API lists 4 tools with 3 views and 4 GitHub stars. MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars.

Can I use both CatchDoms — Expired Domains API and MCP Uptime Kuma together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

CatchDoms — Expired Domains API vs MCP Uptime Kuma

In-depth architectural comparison of the CatchDoms — Expired Domains API and MCP Uptime Kuma MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

CatchDoms — Expired Domains API

Monitoring · Remote HTTP/SSE

Quality: 51/100 (Good) | Auth: API Key required

MCP Uptime Kuma

Monitoring · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose CatchDoms — Expired Domains API if you need specialized Monitoring tools running via a hosted cloud SSE transport. Choose MCP Uptime Kuma if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose CatchDoms — Expired Domains API when:

You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: search_domains, get_domain, list_filters.

Explore CatchDoms — Expired Domains API Details

Choose MCP Uptime Kuma when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
Primary tools included: getMonitorSummary, listMonitors, listMonitorTypes.

Feature & Specification Comparison

Specification	CatchDoms — Expired Domains API Monitoring	MCP Uptime Kuma Monitoring
Summary	Search 40K+ expired domains from 12 auction platforms with SEO metrics and scores.	A Model Context Protocol (MCP) server for Uptime Kuma version 2.
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

CatchDoms — Expired Domains API Tools (4)

search_domains

Search for domains with filters. Returns up to 100 results sorted by quality.

get_domain

Get full details for a specific domain.

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.

MCP Uptime Kuma Tools (22)

getMonitorSummary

Get a quick overview of all monitors with their current status. Supports filtering.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

CatchDoms — Expired Domains API Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "catchdoms-expired-domains-api": {
      "url": "https://catchdoms.com/mcp/catchdoms/free"
    }
  }
}

MCP Uptime Kuma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@davidfuchs/mcp-uptime-kuma",
        "mcp-uptime-kuma-get-jwt"
      ],
      "env": {
        "UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
        "UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
        "UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
        "UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
        "UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
        "UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
      }
    }
  }
}

Frequently Asked Questions

CatchDoms — Expired Domains API is categorized under Monitoring and uses a remote streaming HTTP/SSE transport. In contrast, MCP Uptime Kuma belongs to Monitoring using local stdio subprocess. Select CatchDoms — Expired Domains API when you need capabilities focused on monitoring and MCP Uptime Kuma when you require tools for monitoring.

More alternatives to CatchDoms — Expired Domains API More alternatives to MCP Uptime Kuma Monitoring category hub