NestDaddy

Naming Signal

com.namingsignal/naming-signal · v0.2.0

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

Connect Remote server

Terminal
claude mcp add --transport http naming-signal https://namingsignal.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "naming-signal": {
      "url": "https://namingsignal.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "naming-signal": {
      "type": "http",
      "url": "https://namingsignal.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://namingsignal.com/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server asks for a key before it lists its tools. Connect it with your own key to see them.

Headers

NameDescription
Authorization
Required, secret
Bearer <NamingSignal user API key>. Create and revoke keys at https://namingsignal.com/developers. Every tool call is metered and rate limited through the account attached to the key.

Details

Endpointhttps://namingsignal.com/mcp (Streamable HTTP)
Package@namingsignal/[email protected] (NPM, stdio)
First published14 Jul 2026
Last updated14 Jul 2026
Registry namecom.namingsignal/naming-signal

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.