# Nameable (npm · nameable)

Check whether a name is free on package registries, app stores, agent directories and domains.

- Trust score: 83/100 (high trust)
- Change this week: +18
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `nameable`: 83/100 (this document), [markdown](https://verifymcp.io/servers/minanyang-nameable/nameable.md), [page](https://verifymcp.io/servers/minanyang-nameable/nameable)

## Channel facts

- Registry: `npm`
- Package: `nameable`
- Version: `2.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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to minanyang/nameable).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add minanyang-nameable -- npx -y nameable
```

### Cursor

```json
{
  "mcpServers": {
    "minanyang-nameable": {
      "command": "npx",
      "args": [
        "-y",
        "nameable"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "minanyang-nameable": {
      "command": "npx",
      "args": [
        "-y",
        "nameable"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add minanyang-nameable -- npx -y nameable
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "minanyang-nameable": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nameable"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add minanyang-nameable --command npx --arg -y --arg nameable
```

### Hermes

```yaml
mcp_servers:
  minanyang-nameable:
    command: "npx"
    args: ["-y", "nameable"]
```

### Netclaw

```json
{
  "McpServers": {
    "minanyang-nameable": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "nameable"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add minanyang-nameable -t stdio -c npx -a -y nameable
```

### Other

```json
{
  "mcpServers": {
    "minanyang-nameable": {
      "command": "npx",
      "args": [
        "-y",
        "nameable"
      ]
    }
  }
}
```

## 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-11-04 (score 83, 0)

- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 2.1.1 → 2.2.0

### 2026-11-03 (score 83, +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.

### 2026-11-01 (score 82, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 65, +11)

- [security regression] Known CVEs: unverified → fail
- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00
- [functional] Package version: 2.1.0 → 2.1.1

### 2026-10-28 (score 54, −5)

- [security regression] Known CVEs: fail → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 2.0.1 → 2.1.0
- [functional] Package version: 2.0.1 → 2.0.2

### 2026-10-27 (score 59)

First indexed and scored.

## MCP tools (1)

### `check_names` (~382 tokens)

Check name availability

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.

Input parameters:

- `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, required): 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)

Output parameters:

- `reports` (array)
- `schema` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/minanyang-nameable/nameable#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 65
- 2026-10-28: 54
- 2026-10-27: 59

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/nameable
- Socket report: https://socket.dev/npm/package/nameable
- Repository: https://github.com/minanyang/nameable
- Changelog RSS feed: https://verifymcp.io/servers/minanyang-nameable/nameable.xml
- Changelog JSON feed: https://verifymcp.io/servers/minanyang-nameable/nameable.json
- HTML version of this page: https://verifymcp.io/servers/minanyang-nameable/nameable