mcpbeat

Name Tools MCP Server

com.startupnamegenerator/name-tools
answering

Name Tools is answering right now. Last checked 14 min ago. 118 installs a week from npm. Last commit 26 Jun 2026.

Generate startup names with an available .com, checked live, then screen US and EU trademarks.

Installs per day peak 30 · avg 10 · +123% w/w
a month agotoday
Uptime history 39 hours of history · worst hour 0%
39 hours agonow
68.1%
Uptime 24h
62 of 91 checks
—
Tools
hidden behind auth
836 ms
Response time
average over 24h
118
Installs / week
npm and PyPI

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://startupnamegenerator.com/api/mcp streamable-http needs key 246 ms 14 min ago

Name Tools — questions

Answers built from our own checks of this server.

Why is there no tool list for Name Tools?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 68.1% of checks in the last 24 hours got a reply.
Is Name Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 91 checks got a reply (68.1%), average response time 836 ms. The bar chart above shows every period we have measured.
How do I connect Name Tools?
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. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Name Tools need an API key?
Yes. Every time we knock, Name Tools answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Name Tools?
It answers our handshake in 836 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Name Tools?
The npm package startupnamegenerator-mcp was installed 118 times in the last week. Week over week that is +123%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Name Tools open source?
Yes — it is published under the MIT licence, written in JavaScript 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.