Zovo Name Wheel
REMOTE · NAME-WHEEL.ZOVO.ONE
Spin the wheel right in the chat.
Available components
Last scanned (21 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 22 Oct 2026.
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1082 tokens (~270/item across 4 items; 3 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 74
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 22 Oct 2026 · Probed https://name-wheel.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a7bd22ed4200243c13b8f3e12fade750 |
| SANs: zovo.one, name-wheel.zovo.one, *.name-wheel.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of name-wheel.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://name-wheel.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://name-wheel.zovo.one/mcp | HTTPS enforced | 301 | https://name-wheel.zovo.one/mcp |
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 →
make_teams Make random teams ~343
Use this when the user wants a random team generator: split a list of names into random teams or groups by number of teams or by team size, for a class, a game, a workshop, or a sports session. Team sizes differ by at most 1. Optional rules keep certain pairs apart or groups together. Returns each team's members. Does not balance by skill or rating (assignment is random), and is not for scheduling or seating charts. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| keep_apart | array | – | Optional pairs who must be on different teams, e.g. [["Ana", "Ben"], ["Chloe", "Dev"]]. |
| keep_together | array | – | Optional groups who must be on the same team, e.g. [["Eli", "Fay"]]. |
| names | array | yes | Everyone to split into teams, 2 to 200 names, e.g. ["Ana", "Ben", "Chloe", "Dev"]. |
| team_count | number | – | Number of teams to make, a whole number from 2 up to the number of names, e.g. 3. Use this or team_size. Default 2. |
| team_names | array | – | Optional team names in order, e.g. ["Red", "Blue", "Green"]. Missing names default to Team 1, Team 2, ... |
| team_size | number | – | Target people per team, e.g. 4. Makes as many teams as needed so no team is larger than this; sizes differ by at most 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| keep_apart | array | yes | – |
| keep_together | array | yes | – |
| kind | string | yes | – |
| people | number | yes | – |
| renamed_duplicates | array | yes | – |
| sizes | array | yes | – |
| team_count | number | yes | – |
| teams | array | yes | – |
No examples provided.
pick_random_number Pick random numbers ~241
Use this when the user wants a random number generator or number wheel: pick one or more random whole numbers between a min and a max (inclusive), with or without repeats, e.g. a random student number or who goes next. Uses cryptographic, unbiased randomness. Do not use for lottery or Powerball numbers, betting, or login credentials and security codes. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many numbers to pick, a whole number from 1 to 500, default 1, e.g. 5. |
| max | number | – | Largest possible whole number, inclusive, -1000000000 to 1000000000, default 100, e.g. 30 for a class of 30. |
| min | number | – | Smallest possible whole number, inclusive, -1000000000 to 1000000000, default 1, e.g. 1. |
| unique | boolean | – | If true (default) no number repeats, e.g. false to allow repeats like dice rolls. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| kind | string | yes | – |
| max | number | yes | – |
| min | number | yes | – |
| numbers | array | yes | – |
| unique | boolean | yes | – |
No examples provided.
spin_wheel Spin the wheel ~371
Use this when the user wants to spin the wheel, use a wheel spinner or random name picker, pick a random name or option from a list (wheel spinner with names, yes or no wheel, food wheel, custom wheel), or call on people one at a time. Draws 1 or more different winners with cryptographic, unbiased randomness and shows an animated wheel that lands on the winner. Repeated entries (matched ignoring case) or weights give bigger slices. Returns the winners, each entry's chance, and the remaining entries when remove_winners is true. For fun, classroom, and team decisions only; not for lotteries, gambling, or prize draws that have legal requirements. Does not store results between calls.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | How many different winners to draw in this spin, a whole number from 1 to 50, default 1, e.g. 3 to pick 3 students. |
| entries | array | yes | The names or options on the wheel, 2 to 200, e.g. ["Ana", "Ben", "Chloe"]. A repeated entry gets a bigger slice: ["Pizza", "Pizza", "Tacos"] gives Pizza 2 of 3 slots. |
| remove_winners | boolean | – | If true, the winners are taken off the wheel and the remaining entries are returned for the next spin, e.g. true for calling on each student once. |
| title | string | – | Optional wheel title shown above the wheel, e.g. "Who presents first?". |
| weights | array | – | Optional whole-number weight (1-1000) per entry, same order and length as entries, e.g. [3, 1, 1] makes the first entry three times as likely. Leave out for equal chances. |
| Name | Type | Req | Description |
|---|---|---|---|
| chance_percent | – | yes | – |
| entries | array | yes | – |
| equal_chance_percent | number|null | yes | – |
| kind | string | yes | – |
| remaining | array | yes | – |
| remaining_weights | – | yes | – |
| removed | boolean | yes | – |
| title | string | yes | – |
| weights | – | yes | – |
| winner_indexes | array | yes | – |
| winners | array | yes | – |
No examples provided.
How do I install the Zovo Name Wheel MCP server?
Zovo Name Wheel is a hosted endpoint at https://name-wheel.zovo.one/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.
remote · name-wheel.zovo.one
claude mcp add --transport http theluckystrike-name-wheel 'https://name-wheel.zovo.one/mcp'
What is the Zovo Name Wheel MCP server?
Zovo Name Wheel is an MCP server listed in the public MCP registry as io.github.theluckystrike/name-wheel. Spin the wheel right in the chat. This page covers its hosted endpoint (https://name-wheel.zovo.one/mcp).
Is the Zovo Name Wheel MCP server safe to use?
Zovo Name Wheel scores 74 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 Zovo Name Wheel MCP server expose?
Zovo Name Wheel exposes 3 tools: spin_wheel, make_teams, pick_random_number. Their descriptions and schemas cost roughly 955 tokens of context every time the server is loaded.
Does the Zovo Name Wheel MCP server require authentication?
No. We connected to Zovo Name Wheel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Name Wheel MCP server still maintained?
Zovo Name Wheel is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.