Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@NamingSignal name ideas for a fitness app with domain checks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Evidence-first product naming for agents and founders. NamingSignal generates broad, diverse name fields, checks exact domain registry evidence (RDAP) and developer namespaces, and researches finalists with sources and timestamps instead of vibes. Registry not-found is reported as likely unregistered, never as a purchase guarantee.
This repository contains the open-source clients and the deterministic naming core:
Package | What it is | Install |
Stdio MCP server exposing five read-only naming tools backed by the hosted API |
| |
CLI with keyless local commands (RDAP checks, privacy-bounded briefs, deterministic generation, decision records) plus hosted research |
|
Site: https://namingsignal.com
Developer docs and API keys: https://namingsignal.com/developers
Hosted agent guide: https://namingsignal.com/agent-guide.txt
OpenAPI contract: https://namingsignal.com/openapi.json (a static snapshot lives in openapi.json)
Agent workflow guide: docs/agent-workflow.md
Related MCP server: DomainFinder MCP Server
The fastest integration is the hosted Streamable HTTP MCP endpoint. Create a free API key at https://namingsignal.com/developers/keys, then:
claude mcp add --transport http naming-signal https://namingsignal.com/mcp \
--header "Authorization: Bearer YOUR_NAMINGSIGNAL_KEY"Codex ~/.codex/config.toml:
experimental_use_rmcp_client = true
[mcp_servers.naming_signal]
url = "https://namingsignal.com/mcp"
bearer_token_env_var = "NAMING_SIGNAL_API_KEY"Prefer a local process? Use the stdio package instead; see packages/mcp.
npx -y @namingsignal/cli check offhook nicless --tlds com,app --jsonLive RDAP registry evidence, transparent scoring, and honest unknowns, with no account and no API key.
This repo contains the MCP and CLI clients plus the deterministic core they share: RDAP domain checking with calibration, exact namespace checks (npm, PyPI, GitHub, Apple), the brief compiler, import safety bounds, the transparent scoring rubric, and decision-record export. The hosted orchestration (model-led generation, editorial ranking, finalist research providers, accounts, and metering) runs at namingsignal.com and is not in this repo.
Issues and pull requests are welcome at https://github.com/moekoelueker/namingsignal/issues. Please do not file security reports as public issues; see https://namingsignal.com for contact details.
MIT, Copyright (c) 2026 Zena Labs LLC. See LICENSE.
NamingSignal output is preliminary business research, not legal advice, trademark clearance, or a registrar guarantee.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Generate startup names with an available .com, checked live, then screen US and EU trademarks.
Brandable business names with live domain availability + one-click buy URLs.
Trademark search, monitoring and conflict research across 30+ registers, with provenance.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/moekoelueker/namingsignal'
If you have feedback or need assistance with the MCP directory API, please join our Discord server