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 Secret Santa

REMOTE · SECRET-SANTA.ZOVO.ONE

Draw names for a holiday gift exchange, an office party or a family Secret Santa.

+3 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

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 794 tokens (~198/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 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 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 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://secret-santa.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 secret-santa.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://secret-santa.zovo.one/mcp Verified 200
http (plaintext) http://secret-santa.zovo.one/mcp HTTPS enforced 301 https://secret-santa.zovo.one/mcp
MCP tools · 3 exposed · ~692 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
create_secret_santa ~424

Use this when the user wants to draw names for a Secret Santa or holiday gift exchange and give each person a private link. Takes 3 to 60 names, optional couples or households who must not draw each other, one-way exclusions (for example last year's match), a budget, an exchange date and a note. Publishes a hosted page: each private link shows one person whom they buy for, the budget, the date and the match's wishlist, and each person can add their own wishlist. Returns one private link per person and an organizer link; the draw itself is not returned. Explains why when no draw is possible. Does not send emails or texts. Do not use for White Elephant games or for picking one winner.

NameTypeReqDescription
budgetstring–Spending limit as text, e.g. $25 or 20-30 EUR.
couplesarray–Groups whose members must not draw each other (couples, households), e.g. [["Ana","Bo"]].
event_namestring–Name shown on every page, e.g. Office Secret Santa 2026.
exchange_datestring–Day of the gift exchange as YYYY-MM-DD, e.g. 2026-12-18.
exclusionsarray–One-way rules, e.g. [{"giver":"Cy","cannot_draw":"Dee"}] for last year's match.
no_two_person_loopsboolean–true = no two people draw each other (A gives to B and B gives to A). Default false.
notestring–Short note from the organizer shown on every private page, e.g. Wrap it and bring it to the party. No links.
participantsarrayyesEveryone taking part, 3 to 60 first names or nicknames, each unique, e.g. ["Ana","Bo","Cy","Dee"].
time_zonestring–IANA time zone for showing when links were opened, e.g. America/Chicago. Default America/New_York.
NameTypeReqDescription
budgetstring|nullyes–
can_redrawbooleanyes–
closedbooleanyes–
eventstringyes–
exchange_datestring|nullyes–
expires_onstringyes–
manageUrlstringyes–
opened_countnumberyes–
participant_countnumberyes–
peoplearrayyes–
people_count_shownobject––
publicUrlstringyes–
rulesarrayyes–
warningsarrayyes–
wishlist_countnumberyes–

No examples provided.

redraw_secret_santa ~132

Use this when the organizer wants a new random draw for an existing Secret Santa, for example because they saw an assignment by mistake. Takes the organizer link. Works only while nobody has opened a private link; it replaces the old draw with the same rules, keeps the same private links and keeps wishlists. Does not add or remove people (make a new Secret Santa for that).

NameTypeReqDescription
manage_linkstringyesThe private organizer link from when the draw was made, e.g. https://secret-santa.zovo.one/m/AbC.../XyZ... (it contains /m/).
NameTypeReqDescription
budgetstring|nullyes–
can_redrawbooleanyes–
closedbooleanyes–
eventstringyes–
exchange_datestring|nullyes–
expires_onstringyes–
manageUrlstringyes–
opened_countnumberyes–
participant_countnumberyes–
peoplearrayyes–
people_count_shownobject––
publicUrlstringyes–
rulesarrayyes–
warningsarrayyes–
wishlist_countnumberyes–

No examples provided.

show_secret_santa_status ~136

Use this when the organizer asks who has opened their Secret Santa link, who added a wishlist, or wants the private links again. Takes the organizer link (it contains /m/). Returns each person's link, whether and when it was first opened, and whether they added a wishlist. Does not return who buys for whom. Does not change anything. Does not work with a person's private link.

NameTypeReqDescription
manage_linkstringyesThe private organizer link from when the draw was made, e.g. https://secret-santa.zovo.one/m/AbC.../XyZ... (it contains /m/).
NameTypeReqDescription
budgetstring|nullyes–
can_redrawbooleanyes–
closedbooleanyes–
eventstringyes–
exchange_datestring|nullyes–
expires_onstringyes–
manageUrlstringyes–
opened_countnumberyes–
participant_countnumberyes–
peoplearrayyes–
people_count_shownobject––
publicUrlstringyes–
rulesarrayyes–
warningsarrayyes–
wishlist_countnumberyes–

No examples provided.

Install

How do I install the Zovo Secret Santa MCP server?

Zovo Secret Santa is a hosted endpoint at https://secret-santa.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 · secret-santa.zovo.one

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

What is the Zovo Secret Santa MCP server?

Zovo Secret Santa is an MCP server listed in the public MCP registry as io.github.theluckystrike/secret-santa. Draw names for a holiday gift exchange, an office party or a family Secret Santa. This page covers its hosted endpoint (https://secret-santa.zovo.one/mcp).

Is the Zovo Secret Santa MCP server safe to use?

Zovo Secret Santa 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 Secret Santa MCP server expose?

Zovo Secret Santa exposes 3 tools: create_secret_santa, show_secret_santa_status, redraw_secret_santa. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.

Does the Zovo Secret Santa MCP server require authentication?

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

Is the Zovo Secret Santa MCP server still maintained?

Zovo Secret Santa 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 Secret Santa MCP server?

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