Skip to content
mcp/skillhub

Namingsignal MCP Server

com.namingsignal/naming-signalv0.2.0

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

Node.jsstdioremoteofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Maintained3mo ago

Install Namingsignal MCP server

Install in Claude Code

claude mcp add namingsignal -e NAMING_SIGNAL_API_KEY='<naming-signal-api-key>' -- npx -y @namingsignal/mcp

Configuration

VariableRequiredSecretDescription
NAMING_SIGNAL_API_KEYyesyesNamingSignal 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.

Remote endpoints

  • streamable-httphttps://namingsignal.com/mcp

Freshness

Maintained — last maintenance signal 3mo ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    no data · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-07-14 · 3mo ago · official registry · v0.2.0

FAQ

›How do I install the Namingsignal MCP server in Claude Code?

Run: claude mcp add namingsignal -e NAMING_SIGNAL_API_KEY='<naming-signal-api-key>' -- npx -y @namingsignal/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Namingsignal require an API key?

Yes. It expects NAMING_SIGNAL_API_KEY, of which 1 is a secret.

›Can I use Namingsignal as a remote (hosted) MCP server?

Yes — it offers both a hosted endpoint and a local stdio package.

›Is Namingsignal in the official MCP registry?

Yes, as com.namingsignal/naming-signal.

Alternatives to Namingsignal

Other science & research MCP servers.

View all