NameHound MCP server
Which servers in the official MCP registry are NameHound's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry nameapp.namehound/namehoundverified in the MCP registry
The registry name sits under namehound.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools1
- Server calls itselfnamehound
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 98 ms.
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer478 ms
- Space in an agent's context≈ 333 tokensthe definitions of all its tools (1), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →
check_name_availabilityUse this when someone asks whether one specific brand, business, product or project name is free as a domain name (.com, .net, .org, .app) and as a handle on Bluesky, Mastodon, GitLab, npm and PyPI, and wants the NameHound Brand Name…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"namehound": {
"type": "http",
"url": "https://namehound.app/mcp"
}
}
}Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.