Nameable
NPM · NAMEABLE
Check whether a name is free on package registries, app stores, agent directories and domains.
Available components
Last scanned (4 hours ago)
Scores higher than 76% of npm servers
Category Search and Retrieval
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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to minanyang/nameable). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 382 tokens (~382/item across 1 items; 1 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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 0
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.1.1 → 2.2.0 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 +11
- Known CVEs: unverified → fail ▼ security
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 2.1.0 → 2.1.1 functional
- 28 Oct 26 −5
- Known CVEs: fail → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 2.0.1 → 2.1.0 functional
- Package version: 2.0.1 → 2.0.2 functional
- 27 Oct 26 59
First indexed and scored.
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 5 Nov 2026 · Analysed npm/nameable@2.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | minanyang/nameable |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/minanyang/nameable/.github/workflows/release.yml@refs/tags/v2.2.0 |
| Rekor log index | 3692004319 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:204edf4b7498a21a8e7f93d15082f49e581f9490610a6d111cde9df229d2e9b3352fbd593a79ad2c584230e55ac38c4e6b32d3cfa3a82248a7b269600 |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
check_names Check name availability ~382
Check whether names are free on package registries, GitHub, agent and editor directories, app stores, Taiwan trademarks and domains. Each result has a status: - available: nobody holds it and the registry would accept it. certainty "confirmed" means every rule that public data allows was checked; "probable" means one could not be, and note says which. - reclaimable: held before but released; it can be taken again. - taken: someone holds it; url shows who. Where names are not exclusive (MCP Registry, Google Play, Gemini CLI gallery, trademarks) it means another entry uses the name, and note says it does not block a new one. - unavailable: nobody holds it exactly, but the registry would refuse it (invalid, reserved, too similar to an existing name, or blocked for now after a deletion); note says why. - unknown: no trustworthy answer (network error, rate limit). Never treat it as free. Pick only the channels that matter for the project instead of checking everything.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | Channels to check (default: all). One of: npm, pypi, crates, homebrew, rubygems, packagist, pub, nuget, docker, github, mcp-registry, smithery, claude-plugins, cursor, gemini, vscode, open-vsx, jetbr… |
| names | array | yes | Candidate names, checked on every selected channel |
| refresh | boolean | – | Download registry name lists again even when the cached copy is fresh |
| tlds | array | – | TLDs for "domain", at most 20 (default: com, dev) |
| Name | Type | Req | Description |
|---|---|---|---|
| reports | array | yes | – |
| schema | number | yes | – |
No examples provided.
How do I install the Nameable MCP server?
Nameable runs locally as an npm package, launched with npx -y nameable. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nameable
claude mcp add minanyang-nameable -- npx -y nameable
What is the Nameable MCP server?
Nameable is an MCP server listed in the public MCP registry as io.github.minanyang/nameable. Check whether a name is free on package registries, app stores, agent directories and domains. This page covers its npm package (nameable).
Is the Nameable MCP server safe to use?
Nameable scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Nameable MCP server expose?
Nameable exposes 1 tool: check_names. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
Is the Nameable MCP server still maintained?
Nameable is still listed as active in the MCP registry. We last reached this channel on 5 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 Nameable MCP server under?
Nameable declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.