Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Fair Draw

REMOTE · FAIR-DRAW.ZOVO.ONE

Organize a prize draw that everyone can check.

+3 this week 73 Trust /100

Last scanned (11 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 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 912 tokens (~182/item across 5 items; 4 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

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 →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 67

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://fair-draw.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 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.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 fair-draw.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. 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=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://fair-draw.zovo.one/mcp Verified 200
http (plaintext) http://fair-draw.zovo.one/mcp HTTPS enforced 301 https://fair-draw.zovo.one/mcp
MCP tools · 4 exposed · ~805 tokens

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 →

Tool Tokens
add_draw_entries ~182

Use this when the organizer wants to add entrant names to a draw made with create_prize_draw, before the winners are drawn. Takes the private organizer link and a list of up to 100 names per call (send more in further calls). Duplicate names (ignoring case) are skipped and reported. Does not draw; does not remove names.

NameTypeReqDescription
manage_urlstringyesThe private organizer link of the draw, e.g. https://fair-draw.zovo.one/m/AbC123.../XyZ789... (contains /m/).
namesarrayyesEntrant display names to add, up to 100 per call (send more in further calls), each up to 40 characters, one person per item, e.g. ["Ana", "Ben K.", "Chloe"]. First names or nicknames only.
NameTypeReqDescription
actionstringyes–
addednumber––
backupsarrayyes–
backups_wantednumberyes–
commitmentstringyes–
drawn_atstring|nullyes–
entriesnumberyes–
entry_list_hashstring|nullyes–
expires_atstringyes–
manage_urlstringyes–
namesarrayyes–
names_shownnumberyes–
notestring––
prizestringyes–
public_entrybooleanyes–
public_urlstringyes–
seedstring|nullyes–
skippedarray––
skipped_countnumber––
statusstringyes–
titlestringyes–
winnersarrayyes–
winners_wantednumberyes–

No examples provided.

create_prize_draw ~381

Use this when the user wants a fair random pick of winners from a group: a giveaway, door prize, raffle without tickets, classroom or team pick. Publishes a draw page with a public link where entrants add their names (or only the organizer adds them), and returns a private organizer link. Optionally adds a first list of names. Up to 500 entries, 1 to 20 winners, up to 10 backups. For free draws only: set free_entry to true to confirm nobody pays to enter; it does not handle money. Does not draw yet; use draw_winners for that.

NameTypeReqDescription
backupsinteger–Number of backup winners drawn in order after the winners, 0 to 10 (default 0). Example: 2.
free_entrybooleanyesSet true to confirm nobody pays to enter and no money is pooled; this tool does not handle money.
namesarray–Entrant display names, up to 500, each up to 40 characters, one person per item, e.g. ["Ana", "Ben K.", "Chloe"]. First names or nicknames only.
notestring–Optional short note shown on the page, up to 400 characters, e.g. Draw on Friday at the team call.
prizestring–What the winners get, up to 200 characters, e.g. One 50-minute massage voucher.
public_entryboolean–true (default) = people add their own name on the public page; false = only the organizer adds names.
titlestringyesShort title of the draw, up to 120 characters, e.g. Team lunch voucher draw.
winnersinteger–Number of winners, 1 to 20 (default 1). Example: 2.
NameTypeReqDescription
actionstringyes–
addednumber––
backupsarrayyes–
backups_wantednumberyes–
commitmentstringyes–
drawn_atstring|nullyes–
entriesnumberyes–
entry_list_hashstring|nullyes–
expires_atstringyes–
manage_urlstringyes–
namesarrayyes–
names_shownnumberyes–
notestring––
prizestringyes–
public_entrybooleanyes–
public_urlstringyes–
seedstring|nullyes–
skippedarray––
skipped_countnumber––
statusstringyes–
titlestringyes–
winnersarrayyes–
winners_wantednumberyes–

No examples provided.

draw_winners ~137

Use this when the organizer is ready to pick the winners of a draw made with create_prize_draw. Takes the private organizer link. Closes entries, picks the winners and backups with the published method, and reveals the seed on the public page so anyone can verify. The result is final: running it again returns the same winners. Needs at least one entry. Does not add or remove names and does not redraw.

NameTypeReqDescription
manage_urlstringyesThe private organizer link of the draw, e.g. https://fair-draw.zovo.one/m/AbC123.../XyZ789... (contains /m/).
NameTypeReqDescription
actionstringyes–
addednumber––
backupsarrayyes–
backups_wantednumberyes–
commitmentstringyes–
drawn_atstring|nullyes–
entriesnumberyes–
entry_list_hashstring|nullyes–
expires_atstringyes–
manage_urlstringyes–
namesarrayyes–
names_shownnumberyes–
notestring––
prizestringyes–
public_entrybooleanyes–
public_urlstringyes–
seedstring|nullyes–
skippedarray––
skipped_countnumber––
statusstringyes–
titlestringyes–
winnersarrayyes–
winners_wantednumberyes–

No examples provided.

show_draw_results ~105

Use this when the user wants the state of a draw made with create_prize_draw: number of entries, the names, the commitment, and after the draw the winners, backups and proof values. Takes the private organizer link. Does not change the draw.

NameTypeReqDescription
manage_urlstringyesThe private organizer link of the draw, e.g. https://fair-draw.zovo.one/m/AbC123.../XyZ789... (contains /m/).
NameTypeReqDescription
actionstringyes–
addednumber––
backupsarrayyes–
backups_wantednumberyes–
commitmentstringyes–
drawn_atstring|nullyes–
entriesnumberyes–
entry_list_hashstring|nullyes–
expires_atstringyes–
manage_urlstringyes–
namesarrayyes–
names_shownnumberyes–
notestring––
prizestringyes–
public_entrybooleanyes–
public_urlstringyes–
seedstring|nullyes–
skippedarray––
skipped_countnumber––
statusstringyes–
titlestringyes–
winnersarrayyes–
winners_wantednumberyes–

No examples provided.

Install

How do I install the Zovo Fair Draw MCP server?

Zovo Fair Draw is a hosted endpoint at https://fair-draw.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 · fair-draw.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-fair-draw 'https://fair-draw.zovo.one/mcp'
Common questions

What is the Zovo Fair Draw MCP server?

Zovo Fair Draw is an MCP server listed in the public MCP registry as io.github.theluckystrike/fair-draw. Organize a prize draw that everyone can check. This page covers its hosted endpoint (https://fair-draw.zovo.one/mcp).

Is the Zovo Fair Draw MCP server safe to use?

Zovo Fair Draw scores 73 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 Fair Draw MCP server expose?

Zovo Fair Draw exposes 4 tools: create_prize_draw, add_draw_entries, draw_winners, show_draw_results. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.

Does the Zovo Fair Draw MCP server require authentication?

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

Is the Zovo Fair Draw MCP server still maintained?

Zovo Fair Draw is still listed as active in the MCP registry. We last reached this channel on 21 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 Zovo Fair Draw MCP server?

VerifyMCP ran 14 checks on Zovo Fair Draw, 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.