# NameWheel (remote · mcp.namewheel.org)

Fair random picks with the wheel in your chat: pick names, split teams, run certified draws.

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

## Components

- remote · `mcp.namewheel.org`: 87/100 (this document), [markdown](https://verifymcp.io/servers/org-namewheel-mcp/mcp.md), [page](https://verifymcp.io/servers/org-namewheel-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.namewheel.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-07.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1513 tokens (~137/item across 11 items; 8 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the NameWheel MCP server?

NameWheel is a hosted endpoint at https://mcp.namewheel.org/mcp, so there is nothing to install locally. 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 --transport http org-namewheel-mcp 'https://mcp.namewheel.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-namewheel-mcp": {
      "url": "https://mcp.namewheel.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-namewheel-mcp": {
      "type": "http",
      "url": "https://mcp.namewheel.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-namewheel-mcp]
url = "https://mcp.namewheel.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-namewheel-mcp": {
      "type": "remote",
      "url": "https://mcp.namewheel.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-namewheel-mcp --url 'https://mcp.namewheel.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-namewheel-mcp:
    url: "https://mcp.namewheel.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-namewheel-mcp": {
      "Transport": "http",
      "Url": "https://mcp.namewheel.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-namewheel-mcp -t streamable-http -u 'https://mcp.namewheel.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-namewheel-mcp": {
      "type": "http",
      "url": "https://mcp.namewheel.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-06 (score 87, 0)

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

### 2026-11-02 (score 87, +1)

- [security] Stability: 0.97 → pass

### 2026-10-31 (score 86, +1)

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

### 2026-10-29 (score 85, +1)

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

### 2026-10-26 (score 84, +1)

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

### 2026-10-24 (score 83, +1)

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

### 2026-10-22 (score 82, +1)

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

### 2026-10-20 (score 81, +1)

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

## MCP tools (8)

### `spin_wheel` (~225 tokens)

Spin the wheel

Pick one or more winners at random from a list of names or options, and show the wheel spinning to the result in the chat. Use it whenever the person wants something chosen at random: a student to answer, who goes first, where to eat, a raffle winner among friends. Works without an account. The pick is fair (a cryptographic random number generator), but it is not a certified record; when other people need to be able to check the result later, use certified_draw instead.

Input parameters:

- `allow_repeat_winners` (boolean): With more than one winner, may the same entry win twice? Default false: each winner leaves the wheel.
- `entries` (array, required): The names or options, one per item, exactly as the person gave them. Repeating a name gives it another slot (another chance), as on the NameWheel website.
- `title` (string): A short title for the wheel, such as 'Period 3 cold call' or 'Who presents first'.
- `winners` (integer): How many winners to pick. Default 1.

### `make_teams` (~196 tokens)

Split into random teams

Split a list of names into random teams or groups of even size, and show them as cards in the chat. Use it for class groups, project teams, game sides, rotations. Give either how many teams or how many people per team. Works without an account.

Input parameters:

- `entries` (array, required): The names or options, one per item, exactly as the person gave them. Repeating a name gives it another slot (another chance), as on the NameWheel website.
- `team_names` (array): Names for the teams, in order. Default Team 1, Team 2...
- `team_size` (integer): How many people per team, instead of a number of teams.
- `teams` (integer): How many teams. Default 2 when team_size is not given.
- `title` (string): A short title for the wheel, such as 'Period 3 cold call' or 'Who presents first'.

### `open_wheel_link` (~133 tokens)

Get a wheel link

Make a namewheel.org link that opens the full NameWheel wheel with these names already loaded, for spinning on a projector, a stream or a shared screen with sound, modes and themes. Works without an account. Commas inside a name become spaces in the link.

Input parameters:

- `entries` (array, required): The names or options, one per item, exactly as the person gave them. Repeating a name gives it another slot (another chance), as on the NameWheel website.
- `title` (string): A short title for the wheel, such as 'Period 3 cold call' or 'Who presents first'.

### `certified_draw` (~284 tokens)

Run a certified draw

Run a TrueSpin certified draw on NameWheel: the winner is sealed by NameWheel's server before it is revealed, randomness from this connection is added, and the result is published on a permanent public proof page (namewheel.org/v/CODE) that anyone can check, with a button that recomputes the draw. Use it when the result must be provable to other people: a class prize, a team decision, a draw announced to a group. IMPORTANT: the title, every entry and the winner become public on the proof page, so only use names the person is happy to publish, and tell them so. Needs a connected NameWheel account (free). To draw against a list locked earlier with freeze_list, pass frozen_code instead of entries.

Input parameters:

- `entries` (array): The names or options, one per item, exactly as the person gave them. Repeating a name gives it another slot (another chance), as on the NameWheel website.
- `entropy` (string): Optional words or a number from the person, mixed into the draw's randomness.
- `frozen_code` (string): Code or link of a list frozen earlier with freeze_list (namewheel.org/f/CODE). The draw uses exactly that list.
- `title` (string, required): The draw's public title, such as 'Year 9 reading prize' or 'Who presents first'.

### `freeze_list` (~146 tokens)

Freeze an entry list

Lock a list of entries in public before a draw, at namewheel.org/f/CODE, with a fingerprint and the exact time. Nobody can add or remove a name after that, and when certified_draw later uses this list (frozen_code), the frozen page links to the result. Use it when entries close before the draw happens. The title and every entry are public. Needs a connected NameWheel account (free).

Input parameters:

- `entries` (array, required): The names or options, one per item, exactly as the person gave them. Repeating a name gives it another slot (another chance), as on the NameWheel website.
- `title` (string, required): The list's public title.

### `verify_draw` (~134 tokens)

Check a certified draw

Check whether a NameWheel certified draw is genuine, from its code or its namewheel.org/v/ link: recomputes the winner from the published secret, the added randomness and the entries, checks the commitment made before the spin, and checks NameWheel's Ed25519 signature on the record. Also says how many draws the host ran on this exact list. Use it when someone asks whether a draw or a giveaway result was real. Works without an account.

Input parameters:

- `code` (string, required): The draw code (8 letters and digits) or its link, such as namewheel.org/v/DG5J6VD7.

### `my_draws` (~70 tokens)

List my certified draws

List this account's recent NameWheel certified draws (or frozen lists) with their winners and proof links, newest first. Needs a connected NameWheel account.

Input parameters:

- `frozen_lists` (boolean): List frozen entry lists instead of draws.
- `limit` (integer): How many to list. Default 10.

### `check_plan` (~78 tokens)

Check what this connection can do

Say what this NameWheel connection can do: without an account (spins, teams, wheel links, checking draws) or with a connected account (certified draws, frozen lists, the account's draws), and how many certified draws are left today. Use it when the person asks about limits, their account, or why a request was refused.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-namewheel-mcp/mcp#diagnostics

## Score history

- 2026-11-07: 87
- 2026-11-06: 87
- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 77
- 2026-10-10: 76
- 2026-10-05: 74

## Common questions

### What is the NameWheel MCP server?

NameWheel is an MCP server listed in the public MCP registry as org.namewheel/mcp. Fair random picks with the wheel in your chat: pick names, split teams, run certified draws. This page covers its hosted endpoint (https://mcp.namewheel.org/mcp).

### Is the NameWheel MCP server safe to use?

NameWheel scores 87 out of 100 on VerifyMCP. 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 NameWheel MCP server expose?

NameWheel exposes 8 tools: spin_wheel, make_teams, open_wheel_link, certified_draw, freeze_list, and 3 more. Their descriptions and schemas cost roughly 1,266 tokens of context every time the server is loaded.

### Does the NameWheel MCP server require authentication?

No. We connected to NameWheel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NameWheel MCP server still maintained?

NameWheel is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NameWheel MCP server?

VerifyMCP ran 14 checks on NameWheel, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.namewheel.org/mcp
- Repository: https://github.com/namewheel/mcp
- Website: https://namewheel.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-namewheel-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-namewheel-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-namewheel-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-namewheel-mcp/mcp