Naming Signal

com.namingsignalPublished by namingsignal.comOfficial publisherv0.2.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant run evidence-first naming work: briefs, naming sprints, exact domain checks and finalist research, read-only.

What you can do
Naming Signal supports naming projects through an assistant. According to the registry description it covers briefs, naming sprints, exact domain checks and finalist research, and it is described as read-only. The manifest does not list individual tools, so the exact operations are not documented here. It is reachable as a hosted remote endpoint or as a local npm package over stdio.
When to use it
Useful when you are naming a product, company or project and want the assistant to work from a brief, generate and compare candidates, check exact domain availability and research finalists. Less relevant if you only need general brainstorming without domain checks or structured naming steps.
Requirements
A NamingSignal user API key, supplied as NAMING_SIGNAL_API_KEY or as an Authorization bearer header, created on the provider's developer page. The hosted endpoint requires network access; the local npm package runs over stdio. NAMING_SIGNAL_API_URL is optional and defaults to the hosted origin.
Before you install
The API key is a secret and should be kept out of shared configuration. Every tool call is metered and rate limited through the account attached to the key, so usage may be billed or capped depending on your plan. The server is described as read-only, but naming requests and briefs are sent to the provider's service.

Installation

In SourceWeft

  1. Open Naming Signal in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.namingsignal%2Fnaming-signal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "naming-signal": {
      "type": "http",
      "url": "https://namingsignal.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.