NameWheel MCP server
org.namewheel/mcpnamewheel.orgstreamable-httpv1.0.0Scanned
Fair random picks with the wheel in your chat: pick names, split teams, run certified draws.
8 tools: 7 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
7 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the NameWheel MCP server can do
The NameWheel MCP server is published by namewheel.org, a domain the MCP Registry verified. It has 8 tools. It can create or change data (7 tools: spin_wheel, make_teams, open_wheel_link, certified_draw and 3 more), but cannot delete data. 1 tool only reads.
3 tools bring in text other people can write (certified_draw, freeze_list and verify_draw).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 7Claude Code: ask
certified_drawRun 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 …Reads text others writeNo findings
Why it is in this group
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Run a certified draw
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
check_planSay 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 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check what this connection can do
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
freeze_listLock a list of entries in public before a draw, at namewheel.org/f/CODE, with a fingerprint and the exact time.Reads text others writeNo findings
Why it is in this group
- The name "freeze_list" says "list": a word for reading.
- The description's first verb is "lock": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- title: Freeze an entry list
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
make_teamsSplit a list of names into random teams or groups of even size, and show them as cards in the chat.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Split into random teams
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
open_wheel_linkMake 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…1 finding
Why it is in this group
- The name "open_wheel_link" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "open_wheel_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_wheel_link" says "open": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a wheel link
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
spin_wheelPick one or more winners at random from a list of names or options, and show the wheel spinning to the result in the chat.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Spin the wheel
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
verify_drawCheck 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 entri…Reads text others write1 finding
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "verify_draw" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a certified draw
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
my_drawsList this account's recent NameWheel certified draws (or frozen lists) with their winners and proof links, newest first.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List this account's recent NameWheel certified draws (or frozen lists) with their winners and proof links, newest first. Needs a connected NameWheel account.
Annotations the server declares
- title: List my certified draws
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.namewheel.org/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.namewheel.org
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.namewheel.org/mcp: tools/list returned 8 tools to an anonymous client, including spin_wheel (write), make_teams (write), open_wheel_link (write), certified_draw (write), freeze_list (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
- Warnopen_wheel_link
The server marks "open_wheel_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_wheel_link" says "open": a word for a change.
- Warnverify_draw
The server marks "verify_draw" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http namewheel https://mcp.namewheel.org/mcpclaude mcp add --transport http namewheel https://mcp.namewheel.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__namewheel__my_draws"
],
"ask": [
"mcp__namewheel__spin_wheel",
"mcp__namewheel__make_teams",
"mcp__namewheel__open_wheel_link",
"mcp__namewheel__certified_draw",
"mcp__namewheel__freeze_list",
"mcp__namewheel__verify_draw",
"mcp__namewheel__check_plan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as namewheel. Review it before you use it.
Capability tags behind 3 rules
- mcp__namewheel__certified_draw untrusted-input
- mcp__namewheel__freeze_list untrusted-input
- mcp__namewheel__verify_draw untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/org.namewheel/mcp/verify?hash=6f4525e44388208e07657ef9dfe8fa671db251f8bd1301914358a84396221528" | jq -e '.changed == false'Pinned hash 6f4525e44388, from Nov 18, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/org.namewheel/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/org.namewheel/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.
NameWheel MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NameWheel MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 7 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NameWheel MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NameWheel MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NameWheel MCP server have?
- 8 tools: 7 write, 1 read. spin_wheel, make_teams, open_wheel_link, certified_draw, freeze_list, verify_draw, check_plan and my_draws.
Does the NameWheel MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NameWheel MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NameWheel MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.