# com.namingsignal/naming-signal (npm · @namingsignal/mcp)

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

- Trust score: 59/100 (low)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `namingsignal.com`: 36/100, [markdown](https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal.md), [page](https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal)
- npm · `@namingsignal/mcp`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp.md), [page](https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp)

## Channel facts

- Registry: `npm`
- Package: `@namingsignal/mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 856 tokens (~171/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-namingsignal-naming-signal -- npx -y @namingsignal/mcp
```

### Codex

```bash
codex mcp add com-namingsignal-naming-signal -- npx -y @namingsignal/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-namingsignal-naming-signal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@namingsignal/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-namingsignal-naming-signal --command npx --arg -y --arg @namingsignal/mcp
```

### Hermes

```yaml
mcp_servers:
  com-namingsignal-naming-signal:
    command: "npx"
    args: ["-y", "@namingsignal/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-namingsignal-naming-signal": {
      "command": "npx",
      "args": [
        "-y",
        "@namingsignal/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 58, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → good
- [functional improvement] License: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-08-01 (score 13, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 18, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 36)

First indexed and scored.

## MCP tools (5)

### `compile_project_brief` (~64 tokens)

Compile an editable naming brief

Turn a sentence, product prompt, README, or agent summary into a bounded, editable project brief. Missing fields remain explicit rather than invented.

Input parameters:

- `context` (string, required): Product context, prompt, or README text
- `source` (string): Human-readable provenance label

### `create_naming_sprint` (~218 tokens)

Create and check a naming sprint

Generate and check a naming sprint across four directions. Use any count from 10 to 200; 100–200 for an initial sprint or 40 for a feedback round. Pass prior names as existingNames so an iteration never repeats the retained ledger.

Input parameters:

- `availabilityRule` (string)
- `context` (string, required): Product description, prompt, or README text
- `count` (integer)
- `dislikedNames` (array): Examples or patterns the next round should avoid
- `existingNames` (array): Names already generated in this project; all are excluded from the new round
- `feedback` (string): Founder feedback for an iterative round
- `includeLedger` (boolean): Return the complete checked candidate ledger in addition to the bounded shortlist
- `likedNames` (array): Examples whose qualities should guide the next round
- `tlds` (array)
- `top` (integer): Number of ranked survivors returned inline
- `verbose` (boolean): Return full evidence objects instead of the compact per-name shape

### `check_names` (~90 tokens)

Check names and selected domain endings

Check exact domain registry evidence and optional developer namespaces for one or more names. Unknown, timeout, unsupported, or conflicting evidence never becomes available.

Input parameters:

- `context` (string): Optional product context for transparent scoring
- `includeNamespaces` (boolean)
- `names` (array, required)
- `tlds` (array)
- `verbose` (boolean): Return full evidence objects instead of the compact per-name shape

### `analyze_candidates` (~78 tokens)

Analyze one to three finalists

Run deeper source-backed namesake, namespace, domain, and preliminary trademark-risk research for one to three finalists. Returns unknowns and manual checks explicitly.

Input parameters:

- `context` (string, required)
- `names` (array, required)
- `tlds` (array)
- `verbose` (boolean): Return full research evidence instead of the compact per-name shape

### `get_purchase_links` (~45 tokens)

Get registrar verification links

Create exact-domain Porkbun search links for a fresh manual availability and price check. This never purchases, reserves, or claims a domain is available.

Input parameters:

- `domains` (array, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 13
- 2026-07-31: 18
- 2026-07-30: 36
- 2026-07-28: 36
- 2026-07-27: 36

## Links

- npm package: https://www.npmjs.com/package/@namingsignal/mcp
- Socket report: https://socket.dev/npm/package/@namingsignal/mcp
- Website: https://namingsignal.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-namingsignal-naming-signal/namingsignal-mcp