Spin Wheel Names
REMOTE · SPINWHEELNAMES.COM
Spin a random picker wheel, pick a random number, and search shared wheels from spinwheelnames.com.
Available components
Last scanned (5 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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. 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. 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 Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 453 tokens (~75/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Oct 26 −1
- Tool “get_wheel” rewrote its description, which is the text the model reads security
- Tool “search_wheels” rewrote its description, which is the text the model reads security
- “search_wheels” reworded the description of “query” cosmetic
- 3 Oct 26 +1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 2 Oct 26 88
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.93 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 0
- Authorization: unverified → partial ▲ security
- Tool “get_wheel” rewrote its description, which is the text the model reads security
- Tool “spin_wheel” rewrote its description, which is the text the model reads security
- Schema quality: 327 → 447 ▼ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- New resource “spin-wheel” functional
- New resource “spin-wheel-chatgpt” functional
- “spin_wheel” added an optional parameter “title” cosmetic
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 · Probed https://spinwheelnames.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spinwheelnames.com | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 27f4bda6a026db95130a365197a017fd |
| SANs: spinwheelnames.com, *.spinwheelnames.com | ||||||
| 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 spinwheelnames.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| spinwheelnames.com. | No DS | 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; frame-src 'self' https:; frame-ancestors 'self'; connect-src 'self' https:; font-src 'self' https: |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spinwheelnames.com/mcp | Verified | 200 | |
| http (plaintext) | http://spinwheelnames.com/mcp | HTTPS enforced | 301 | https://spinwheelnames.com/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 →
get_wheel ~68
Fetch a specific saved wheel from spinwheelnames.com by its slug or id, including its entries and description, and show it as an interactive wheel the user can spin.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The wheel slug or custom id (from a spinwheelnames.com URL). |
No output schema declared.
No examples provided.
pick_random_number ~68
Pick a random whole number in an inclusive range, like spinning a "pick a number" wheel. Defaults to 1-100.
| Name | Type | Req | Description |
|---|---|---|---|
| max | integer | – | Maximum value, inclusive. Defaults to 100. |
| min | integer | – | Minimum value, inclusive. Defaults to 1. |
No output schema declared.
No examples provided.
search_wheels ~93
Search publicly shared name-picker wheels already created on spinwheelnames.com by title or description (e.g. "classroom", "baby names", "raffle"). Returns links a user can open to view or reuse an existing wheel.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (1-20, default 5). |
| query | string | yes | Search text to match against wheel titles and descriptions. |
No output schema declared.
No examples provided.
spin_wheel ~140
Spin a random picker wheel over a list of entries (names, teams, prizes, tasks, anything) and return the winner. Use this whenever a user wants a fair, random pick from a list, or wants a wheel to spin. Shows an interactive wheel the user can spin again, and saves it on spinwheelnames.com so the returned url opens and shares that exact wheel. Always give the user the url.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | The list of names/entries to spin the wheel over (at least 2). |
| title | string | – | Optional short title for the wheel, e.g. "Who presents first?". |
No output schema declared.
No examples provided.
How do I install the Spin Wheel Names MCP server?
Spin Wheel Names is a hosted endpoint at https://spinwheelnames.com/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 · spinwheelnames.com
claude mcp add --transport http heyiamluke-spinwheelnames 'https://spinwheelnames.com/mcp'
What is the Spin Wheel Names MCP server?
Spin Wheel Names is an MCP server listed in the public MCP registry as io.github.heyiamluke/spinwheelnames. Spin a random picker wheel, pick a random number, and search shared wheels from spinwheelnames.com. This page covers its hosted endpoint (https://spinwheelnames.com/mcp).
Is the Spin Wheel Names MCP server safe to use?
Spin Wheel Names scores 88 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 Spin Wheel Names MCP server expose?
Spin Wheel Names exposes 4 tools: spin_wheel, pick_random_number, search_wheels, get_wheel. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Does the Spin Wheel Names MCP server require authentication?
No. We connected to Spin Wheel Names without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Spin Wheel Names MCP server still maintained?
Spin Wheel Names 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 did VerifyMCP test on the Spin Wheel Names MCP server?
VerifyMCP ran 14 checks on Spin Wheel Names, 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.