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 Raffle Tickets

REMOTE · RAFFLE-TICKETS.ZOVO.ONE

Print numbered raffle tickets with matching stubs for a fundraiser.

+3 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

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 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
Schema Quality & AI Usability68
  • 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 1160 tokens (~386/item across 3 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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 72

    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://raffle-tickets.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 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA256 5cdeaff60651c8190eab5bdc2d24b065
SANs: zovo.one, raffle-tickets.zovo.one, *.raffle-tickets.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 raffle-tickets.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://raffle-tickets.zovo.one/mcp Verified 200
http (plaintext) http://raffle-tickets.zovo.one/mcp HTTPS enforced 301 https://raffle-tickets.zovo.one/mcp
MCP tools · 2 exposed · ~1,085 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
draw_raffle_winners ~472

Use this when the user wants to draw a raffle winner, pick random winners from ticket numbers or names, or use a raffle number generator with no repeats. Draws winners (and optional alternates) without replacement with a secure random number generator from a range such as 1-500, several sold ranges, or a list of names (a name listed twice has two entries); can exclude numbers and assign prizes in draw order. Returns the ordered winners and a draw log PDF and CSV with time, method, entry count and an entry-list fingerprint. Each call is a new draw, so do not call it again to change a result. Does not sell tickets or take payments, and is not legal advice: raffle rules vary by place.

NameTypeReqDescription
alternatesnumber|string|null–Backup winners drawn after the winners, in order, for unclaimed prizes. Default 0.
entries––What is in the drum: sold ticket numbers, ranges or names, as a list or pasted lines. Ranges like 1-250 or A-0001 to A-0100 are expanded. A name listed 3 times has 3 entries. Example: "1-250, 301-420…
event_namestring|null–Event name for the draw log, e.g. Spring Gala Raffle.
exclude––Numbers or names to leave out before the draw, e.g. void tickets or earlier winners: "17, 42".
first_numbernumber|string|null–Instead of entries: the first ticket number of a range, e.g. 1.
last_numbernumber|string|null–Instead of entries: the last ticket number of a range, e.g. 500.
one_prize_per_personboolean|string|null–With names: skip further entries of someone who already won. Default true.
prizes––Prizes in draw order; the first winner gets the first prize. Example: ["TV", "Gift card", "Mug"].
winnersnumber|string|null–How many winners to draw, 1 to 100. Default 1, or the number of prizes when prizes are given.
NameTypeReqDescription
alternatesarrayyes–
assumptionsarrayyes–
downloadsobjectyes–
drawn_at_new_yorkstringyes–
drawn_at_utcstringyes–
eligible_countnumberyes–
entry_countnumberyes–
entry_fingerprint_sha256stringyes–
entry_typestringyes–
event_namestringyes–
excluded_countnumberyes–
kindstringyes–
methodstringyes–
warningsarrayyes–
winnersarrayyes–

No examples provided.

generate_raffle_tickets ~613

Use this when the user wants printable raffle tickets, a raffle ticket template, or numbered tickets with stubs for a fundraiser. Returns a print-ready PDF with 10 or 8 numbered tickets per US Letter or A4 sheet, each with a stub carrying the same number, dashed cut lines, and the event name, date, prizes, price and contact line; numbers run in order across sheets with no gaps or repeats. Up to 2,000 tickets per call. Does not sell tickets, collect payments or check whether a raffle is legal where the user lives.

NameTypeReqDescription
colorstring|null–Accent colour as a name or hex, e.g. blue, green or #1D5FC4. Default red.
contactstring|null–Organizer contact line, e.g. PTA - pta@example.org - (555) 010-2000.
countnumber|string|null–How many tickets, 1 to 2,000. Default 100. Example: 200.
datestring|null–Draw date and time as you want it printed, e.g. May 3, 2027 at 7 pm or 2027-05-03.
digitsnumber|string|null–Minimum digits per number with leading zeros, e.g. 4 gives 0001. Default 4.
end_numbernumber|string|null–Last ticket number instead of count, e.g. 500 for tickets 1 to 500.
event_namestring|null–Event or fundraiser name printed on each ticket, e.g. Spring Gala Raffle. Default: Raffle.
fine_printstring|null–Short line such as Need not be present to win.
locationstring|null–Where the draw happens, e.g. Lincoln High School gym.
paperstring|null–letter (US Letter, default) or a4.
per_pagenumber|string|null–Tickets per sheet: 10 (2 x 5, each 3.75 x 2 in) or 8 (2 x 4, each 3.75 x 2.5 in). Default 10.
prefixstring|null–Text before each number, e.g. A- gives A-0001. Default none.
pricenumber|string|null–Ticket price as printed, e.g. 5 (printed $5), "$5 or 5 for $20", or "€2".
prizes––Prize lines, up to 3 printed, e.g. ["Grand prize: 55-inch TV", "2nd: $100 gift card"] or one line.
start_numbernumber|string|null–First ticket number. Default 1. Example: 1001.
stub_fields––Write-in lines on the stub, up to 3. Default Name and Phone. Example: Name, Phone, Email.
NameTypeReqDescription
assumptionsarrayyes–
downloadsobjectyes–
event_namestringyes–
first_numberstringyes–
kindstringyes–
last_numberstringyes–
paperstringyes–
per_pagenumberyes–
pricestringyes–
prizesarrayyes–
sheetsnumberyes–
stub_fieldsarrayyes–
ticket_countnumberyes–
ticket_sizestringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Raffle Tickets MCP server?

Zovo Raffle Tickets is a hosted endpoint at https://raffle-tickets.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 · raffle-tickets.zovo.one

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

What is the Zovo Raffle Tickets MCP server?

Zovo Raffle Tickets is an MCP server listed in the public MCP registry as io.github.theluckystrike/raffle-tickets. Print numbered raffle tickets with matching stubs for a fundraiser. This page covers its hosted endpoint (https://raffle-tickets.zovo.one/mcp).

Is the Zovo Raffle Tickets MCP server safe to use?

Zovo Raffle Tickets scores 78 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 Raffle Tickets MCP server expose?

Zovo Raffle Tickets exposes 2 tools: generate_raffle_tickets, draw_raffle_winners. Their descriptions and schemas cost roughly 1,085 tokens of context every time the server is loaded.

Does the Zovo Raffle Tickets MCP server require authentication?

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

Is the Zovo Raffle Tickets MCP server still maintained?

Zovo Raffle Tickets 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 Raffle Tickets MCP server?

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