mcpbeat

Domain Finder MCP Server

io.github.Sra1Phani/domain-finder
answering

Domain Finder is answering right now. Last checked 10 min ago. It exposes 2 tools. Last commit 29 Jul 2026.

Check if a brand name is free across domains, GitHub, npm and PyPI, and suggest available names.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
86.8%
Uptime 24h
79 of 91 checks
2
Tools
read from the server
338 ms
Response time
average over 24h
0
Stars
last commit 29 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add domain-finder --transport http https://domain-finder-theta.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "domain-finder": {
      "url": "https://domain-finder-theta.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.domain-finder]
url = "https://domain-finder-theta.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "domain-finder": {
      "url": "https://domain-finder-theta.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "domain-finder": {
      "url": "https://domain-finder-theta.vercel.app/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

generate
generate_names
Generate candidate names from a description, each pre-checked for domain availability. Then call check_name on the favorites for the full cross-namespace picture.
name
check_name
Check whether one or more candidate names are free to use as a brand — across domains and the GitHub / npm / PyPI namespaces — in a single call.

Endpoints

URLTransportStateLatencyChecked
https://domain-finder-theta.vercel.app/api/mcp streamable-http answering 237 ms 10 min ago

Domain Finder — questions

Answers built from our own checks of this server.

What can Domain Finder do?
It exposes 2 tools, read directly from the server on our last check. Among them: check_name, generate_names. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Domain Finder working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 79 of 91 checks got a reply (86.8%), average response time 338 ms. The bar chart above shows every period we have measured.
How do I connect Domain Finder?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Domain Finder need an API key?
No. Domain Finder completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Domain Finder?
It answers our handshake in 338 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Domain Finder open source?
Yes — it is published under the NOASSERTION licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.