Naming-signal MCP Server

Naming-signal is an MCP integration. Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only.

Hosted connection

The registry lists a streamable-http connection at https://namingsignal.com/mcp. The endpoint declares these request headers: Authorization.

Packages and local setup

The published npm package is @namingsignal/mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares NAMING_SIGNAL_API_KEY (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project website. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.