Naming Signal MCP Server

by namingsignal Your server? Claim it

answering

Naming Signal is answering right now. Last checked 1 min ago. 32 installs a week from npm.

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

Installs per day peak 12 · avg 5 · +59% w/w

a month agotoday

Uptime history 47 days of history · worst day 18%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

802 ms

Response time

average over 24h

Installs / week

npm and PyPI

Nothing serious here today

Today is the operative word: we check Naming Signal every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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"
    }
  }
}

This one needs environment variables set before it will start: NAMING_SIGNAL_API_KEY (NamingSignal user API key created at https://namingsignal.com/developers. Required for hosted tool calls.), NAMING_SIGNAL_API_URL (API origin. Defaults to https://namingsignal.com; set http://localhost:3000 for a local development server.). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://namingsignal.com/mcp	streamable-http	needs key	892 ms	1 min ago

Alternatives to Naming Signal

same job, measured the same way

SprintCheckout

by sprintcheckout

Read payment settings, orders and receipts, create payment links and API keys.

answering

Taskive

by taskive

AI-native project management + agent memory: tasks, sprints, risk, burnout, knowledge search.

answering

jira-mini-mcp

by proprock

Minimal Jira Cloud MCP server: broad reads, a narrow 3-tool write surface, optional read-only mode.

local only

Markboard

by markboard

Read and update Markboard kanban boards: cards, checklists, labels, comments and files.

answering

Buggazi

by jyswee

Project management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes.

1 128 installs/wk 2 tools answering

Sprintra

by sprintra-io

The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP.

32 installs/wk answering

ResearchSprint

by conversiondigital-cmyk

AI research reports: market analysis, competitor intel, blog posts. USDC payment.

4 tools answering

Claudia

by yuvalsuede

Task management for AI agents with hierarchical tasks, dependencies, sprints, and coordination.

40 installs/wk local only

Naming Signal — questions

Answers built from our own checks of this server.

Why is there no tool list for Naming Signal?

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: 100.0% of checks in the last 24 hours got a reply.

Is Naming Signal working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 802 ms. The bar chart above shows every period we have measured.

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. You will need your own key: it refuses anonymous clients.

Does Naming Signal need an API key?

Yes. Every time we knock, Naming Signal 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 Naming Signal?

It answers our handshake in 802 ms on average, which is faster than 14% 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 32 times in the last week. Week over week that is +59%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.