com.namingsignal/naming-signal
NPM · @NAMINGSIGNAL/MCP · 2 COMPONENTS
Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only.
Available components
Last scanned (17 hours ago)
Scores higher than 53% of npm servers
Category Marketing and SEO
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 129 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 −1
- Stability: pass → 0.93 functional
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@namingsignal/mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_candidates Analyze one to three finalists ~78
Run deeper source-backed namesake, namespace, domain, and preliminary trademark-risk research for one to three finalists. Returns unknowns and manual checks explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | – |
| names | array | yes | – |
| tlds | array | – | – |
| verbose | boolean | – | Return full research evidence instead of the compact per-name shape |
No output schema declared.
No examples provided.
check_names Check names and selected domain endings ~90
Check exact domain registry evidence and optional developer namespaces for one or more names. Unknown, timeout, unsupported, or conflicting evidence never becomes available.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional product context for transparent scoring |
| includeNamespaces | boolean | – | – |
| names | array | yes | – |
| tlds | array | – | – |
| verbose | boolean | – | Return full evidence objects instead of the compact per-name shape |
No output schema declared.
No examples provided.
compile_project_brief Compile an editable naming brief ~64
Turn a sentence, product prompt, README, or agent summary into a bounded, editable project brief. Missing fields remain explicit rather than invented.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Product context, prompt, or README text |
| source | string | – | Human-readable provenance label |
No output schema declared.
No examples provided.
create_naming_sprint Create and check a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| availabilityRule | string | – | – |
| context | string | yes | 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 |
No output schema declared.
No examples provided.
get_purchase_links Get registrar verification 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
No output schema declared.
No examples provided.
How do I install the com.namingsignal/naming-signal MCP server?
com.namingsignal/naming-signal runs locally as an npm package, launched with npx -y @namingsignal/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @namingsignal/mcp
claude mcp add com-namingsignal-naming-signal -- npx -y @namingsignal/mcp
What is the com.namingsignal/naming-signal MCP server?
com.namingsignal/naming-signal is an MCP server listed in the public MCP registry as com.namingsignal/naming-signal. Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only. This page covers its npm package (@namingsignal/mcp).
Is the com.namingsignal/naming-signal MCP server safe to use?
com.namingsignal/naming-signal scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.namingsignal/naming-signal MCP server expose?
com.namingsignal/naming-signal exposes 5 tools: compile_project_brief, create_naming_sprint, check_names, analyze_candidates, get_purchase_links. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.
Is the com.namingsignal/naming-signal MCP server still maintained?
com.namingsignal/naming-signal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.namingsignal/naming-signal MCP server under?
com.namingsignal/naming-signal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.namingsignal/naming-signal MCP server?
VerifyMCP ran 16 checks on com.namingsignal/naming-signal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.