Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.namingsignal/naming-signal

NPM · @NAMINGSIGNAL/MCP · 2 COMPONENTS · SCANNED AUG 3

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

+23 this week 59 Trust /100
Trust breakdown (6 categories)

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. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @namingsignal/mcp

# add to Claude Code
claude mcp add com-namingsignal-naming-signal -- npx -y @namingsignal/mcp
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-namingsignal-naming-signal --command npx --arg -y --arg @namingsignal/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-namingsignal-naming-signal:
    command: "npx"
    args: ["-y", "@namingsignal/mcp"]
// mcp.json
{
  "mcpServers": {
    "com-namingsignal-naming-signal": {
      "command": "npx",
      "args": [
        "-y",
        "@namingsignal/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +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.

  • 2 Aug 26 +45
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Security disclosure: unverified → fail functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → good functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Dependency health: unverified → partial functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 1 Aug 26 −5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 36

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@namingsignal/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~495 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
analyze_candidates ~78

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

NameTypeReqDescription
contextstringyes
namesarrayyes
tldsarray
verbosebooleanReturn full research evidence instead of the compact per-name shape

No output schema declared.

No examples provided.

check_names ~90

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

NameTypeReqDescription
contextstringOptional product context for transparent scoring
includeNamespacesboolean
namesarrayyes
tldsarray
verbosebooleanReturn full evidence objects instead of the compact per-name shape

No output schema declared.

No examples provided.

compile_project_brief ~64

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

NameTypeReqDescription
contextstringyesProduct context, prompt, or README text
sourcestringHuman-readable provenance label

No output schema declared.

No examples provided.

create_naming_sprint ~218

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.

NameTypeReqDescription
availabilityRulestring
contextstringyesProduct description, prompt, or README text
countinteger
dislikedNamesarrayExamples or patterns the next round should avoid
existingNamesarrayNames already generated in this project; all are excluded from the new round
feedbackstringFounder feedback for an iterative round
includeLedgerbooleanReturn the complete checked candidate ledger in addition to the bounded shortlist
likedNamesarrayExamples whose qualities should guide the next round
tldsarray
topintegerNumber of ranked survivors returned inline
verbosebooleanReturn full evidence objects instead of the compact per-name shape

No output schema declared.

No examples provided.

get_purchase_links ~45

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

NameTypeReqDescription
domainsarrayyes

No output schema declared.

No examples provided.