# Zovo Secret Santa (remote · secret-santa.zovo.one)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `secret-santa.zovo.one`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa.md), [page](https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa)

## Channel facts

- Endpoint: `https://secret-santa.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (redraw_secret_santa).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-secret-santa 'https://secret-santa.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-secret-santa": {
      "url": "https://secret-santa.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-secret-santa": {
      "type": "http",
      "url": "https://secret-santa.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-secret-santa]
url = "https://secret-santa.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-secret-santa": {
      "type": "remote",
      "url": "https://secret-santa.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-secret-santa --url 'https://secret-santa.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-secret-santa:
    url: "https://secret-santa.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-secret-santa": {
      "Transport": "http",
      "Url": "https://secret-santa.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-secret-santa -t streamable-http -u 'https://secret-santa.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-secret-santa": {
      "type": "http",
      "url": "https://secret-santa.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 73, +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.

### 2026-11-18 (score 72, +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.

### 2026-11-16 (score 71, +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.

### 2026-11-13 (score 70, +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.

### 2026-11-11 (score 69, +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.

### 2026-11-09 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 67)

First indexed and scored.

## MCP tools (3)

### `create_secret_santa` (~424 tokens)

Create Secret Santa

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.

Input parameters:

- `budget` (string): Spending limit as text, e.g. $25 or 20-30 EUR.
- `couples` (array): Groups whose members must not draw each other (couples, households), e.g. [["Ana","Bo"]].
- `event_name` (string): Name shown on every page, e.g. Office Secret Santa 2026.
- `exchange_date` (string): Day of the gift exchange as YYYY-MM-DD, e.g. 2026-12-18.
- `exclusions` (array): One-way rules, e.g. [{"giver":"Cy","cannot_draw":"Dee"}] for last year's match.
- `no_two_person_loops` (boolean): true = no two people draw each other (A gives to B and B gives to A). Default false.
- `note` (string): Short note from the organizer shown on every private page, e.g. Wrap it and bring it to the party. No links.
- `participants` (array, required): Everyone taking part, 3 to 60 first names or nicknames, each unique, e.g. ["Ana","Bo","Cy","Dee"].
- `time_zone` (string): IANA time zone for showing when links were opened, e.g. America/Chicago. Default America/New_York.

Output parameters:

- `budget` (string|null)
- `can_redraw` (boolean)
- `closed` (boolean)
- `event` (string)
- `exchange_date` (string|null)
- `expires_on` (string)
- `manageUrl` (string)
- `opened_count` (number)
- `participant_count` (number)
- `people` (array)
- `people_count_shown` (object)
- `publicUrl` (string)
- `rules` (array)
- `warnings` (array)
- `wishlist_count` (number)

### `show_secret_santa_status` (~136 tokens)

Show Secret Santa status

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.

Input parameters:

- `manage_link` (string, required): The private organizer link from when the draw was made, e.g. https://secret-santa.zovo.one/m/AbC.../XyZ... (it contains /m/).

Output parameters:

- `budget` (string|null)
- `can_redraw` (boolean)
- `closed` (boolean)
- `event` (string)
- `exchange_date` (string|null)
- `expires_on` (string)
- `manageUrl` (string)
- `opened_count` (number)
- `participant_count` (number)
- `people` (array)
- `people_count_shown` (object)
- `publicUrl` (string)
- `rules` (array)
- `warnings` (array)
- `wishlist_count` (number)

### `redraw_secret_santa` (~132 tokens)

Redraw Secret Santa

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).

Input parameters:

- `manage_link` (string, required): The private organizer link from when the draw was made, e.g. https://secret-santa.zovo.one/m/AbC.../XyZ... (it contains /m/).

Output parameters:

- `budget` (string|null)
- `can_redraw` (boolean)
- `closed` (boolean)
- `event` (string)
- `exchange_date` (string|null)
- `expires_on` (string)
- `manageUrl` (string)
- `opened_count` (number)
- `participant_count` (number)
- `people` (array)
- `people_count_shown` (object)
- `publicUrl` (string)
- `rules` (array)
- `warnings` (array)
- `wishlist_count` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 68
- 2026-11-09: 68
- 2026-11-08: 67

## 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.

## Links

- Remote endpoint: https://secret-santa.zovo.one/mcp
- Website: https://secret-santa.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-secret-santa/secret-santa
