mcpbeat

Naming Signal MCP Server

com.namingsignal/naming-signal
not responding

Naming Signal is listed as active in the registry but did not answer our last check. 43 installs a week from npm.

Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only.

Installs per day peak 44 · avg 5 · +43% w/w
a month agotoday
Uptime history 41 hours of history · worst hour 0%
41 hours agonow
38.5%
Uptime 24h
35 of 91 checks
—
Tools
hidden behind auth
876 ms
Response time
average over 24h
43
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 11 min ago.

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

Endpoints

URLTransportStateLatencyChecked
https://namingsignal.com/mcp streamable-http answering 73 ms 11 min ago

Naming Signal — questions

Answers built from our own checks of this server.

Is Naming Signal working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 35 of 91 checks got a reply (38.5%), average response time 876 ms. The bar chart above shows every period we have measured.
The registry lists Naming Signal as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Naming Signal?
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 Naming Signal need an API key?
No. Naming Signal completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
How fast is Naming Signal?
It answers our handshake in 876 ms on average, which is faster than 8% 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 Naming Signal?
The npm package @namingsignal/mcp was installed 43 times in the last week. Week over week that is +43%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.