# Pick My Secret Santa (remote · mcp.pickmysecretsanta.com)

Runs a Secret Santa name draw in chat and gives each person a private reveal link.

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

## Components

- remote · `mcp.pickmysecretsanta.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp.md), [page](https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp)

## Channel facts

- Endpoint: `https://mcp.pickmysecretsanta.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## 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.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1489 tokens (~496/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
- **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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Pick My Secret Santa MCP server?

Pick My Secret Santa is a hosted endpoint at https://mcp.pickmysecretsanta.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.

### Claude

```bash
claude mcp add --transport http com-pickmysecretsanta-pick-my-secret-santa 'https://mcp.pickmysecretsanta.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-pickmysecretsanta-pick-my-secret-santa": {
      "url": "https://mcp.pickmysecretsanta.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-pickmysecretsanta-pick-my-secret-santa": {
      "type": "http",
      "url": "https://mcp.pickmysecretsanta.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-pickmysecretsanta-pick-my-secret-santa]
url = "https://mcp.pickmysecretsanta.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pickmysecretsanta-pick-my-secret-santa": {
      "type": "remote",
      "url": "https://mcp.pickmysecretsanta.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pickmysecretsanta-pick-my-secret-santa --url 'https://mcp.pickmysecretsanta.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pickmysecretsanta-pick-my-secret-santa:
    url: "https://mcp.pickmysecretsanta.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-pickmysecretsanta-pick-my-secret-santa": {
      "Transport": "http",
      "Url": "https://mcp.pickmysecretsanta.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-pickmysecretsanta-pick-my-secret-santa -t streamable-http -u 'https://mcp.pickmysecretsanta.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-pickmysecretsanta-pick-my-secret-santa": {
      "type": "http",
      "url": "https://mcp.pickmysecretsanta.com/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-21 (score 70, +1)

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

### 2026-11-20 (score 69, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “explain_secret_santa_rules” rewrote its description, which is the text the model reads
- [security] Tool “plan_secret_santa_setup” rewrote its description, which is the text the model reads

### 2026-11-18 (score 69, +1)

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

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

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

### 2026-11-14 (score 67, +1)

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

### 2026-11-12 (score 66, +1)

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

### 2026-11-10 (score 65, +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-07 (score 64, +1)

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

## MCP tools (3)

### `pick_secret_santa_gift` (~373 tokens)

Pick a Secret Santa gift

Filters Santa's vetted 212 hand-checked gift ideas - the Secret Santa subset of the shared 255-idea bank it shares with its sister site The Present Picker, sorted here for Secret Santa by the budget band your group agreed for its draw - with strict parameters, and returns up to three picks. Parameters: budget_band (required: under_25, 25_to_50, 50_to_100, over_100); recipient_type (anyone, kid - only ideas from the bank's Kid shelf, or adult - everything except the Kid shelf); one interest hint (books, cooking, cozy, fitness, games, gardening, music, outdoors, science, tech, travel, or surprise) which ranks matches first; and avoid, a list of words - any idea whose name, blurb, or why mentions an avoid word is excluded, and the answer says how many ideas the filters set aside. Each pick names the kind of gift, why it fits, and what to look for and avoid. No brands, no stores, no exact prices: budget bands are guides, not exact prices. This tool never asks who the gift is for by name and knows nothing about any draw.

Input parameters:

- `avoid` (array): Words to exclude: any idea whose name, blurb, or why mentions one of these words is filtered out (for example "coffee" or "scented").
- `budget` (string): Legacy alias for budget_band.
- `budget_band` (string): The group's budget band.
- `interest` (string): One interest hint for the person, or surprise for any.
- `recipient_type` (string): Who the gift is for: kid returns only the bank's Kid-shelf ideas; adult excludes them; anyone (default) applies no recipient filter.

### `explain_secret_santa_rules` (~117 tokens)

Explain Secret Santa rules

The rules and fairness answers pickmysecretsanta.com itself publishes, worded the site's way. Topics: basics (the classic rules), fairness_and_secrecy (how the sealed draw works and its honest limits), organizer_view (the organizer's screen shows names and links, never matches by default), keep_apart_pairs, late_joiner (the two honest ways to add someone after the draw), budget (the four bands), white_elephant (how it differs).

Input parameters:

- `topic` (string, required): Which rule to explain.

### `plan_secret_santa_setup` (~494 tokens)

Plan a Secret Santa setup

Configures a Secret Santa group of 3 to 30 right here in chat and hands the organizer one pre-filled link to pickmysecretsanta.com, where the draw is picked in their browser. To make the private links work, the names and matches are stored on the site's server in a form the site can read, and each person gets a private link showing only their own match. Give it the group's names and, optionally, a group name, a budget band, and keep_apart pairs (two-name lists, like [["Ana", "Ben"]], for people who must not draw each other): it validates the setup (3 to 30 people, no shared names - the site's draw cannot tell two same-named people apart) and checks that a valid draw exists under the keep-apart pairs before it returns the link with the group, names, budget, and pairs already in the form, plus the site's honest warnings; if the pairs leave no fair draw, it names the conflict plainly and returns no link. The link carries setup only - nobody has been assigned anyone. Names are used once to build the link and are never stored. With only a headcount (group_size) and no names, it instead returns the setup checklist the site prescribes: what to agree out loud first (buy-by date, what counts as a gift, the late-joiner rule, the reveal), the budget step, and how the browser draw works.

Input parameters:

- `budget` (string): Legacy alias for budget_band.
- `budget_band` (string): The group's budget band, if already picked.
- `group_name` (string): Optional group name, up to 40 characters (for example "The Office Crew").
- `group_size` (integer): How many people, 3 to 30 - for the checklist when no names are given.
- `has_keep_apart_pairs` (boolean): Checklist mode only: true if some pairs must not draw each other.
- `keep_apart` (array): Pairs who must not draw each other, as two-name lists using names from the names list, e.g. [["Ana", "Ben"]].
- `names` (array): Every player's name, one per person (3 to 30). Names must be distinct - add a last initial where two people share a name. When names are given, the tool returns the pre-filled setup link.

## Diagnostics

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

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 64
- 2026-11-08: 64
- 2026-11-07: 64
- 2026-11-06: 63
- 2026-11-05: 63

## Common questions

### What is the Pick My Secret Santa MCP server?

Pick My Secret Santa is an MCP server listed in the public MCP registry as com.pickmysecretsanta/pick-my-secret-santa. Runs a Secret Santa name draw in chat and gives each person a private reveal link. This page covers its hosted endpoint (https://mcp.pickmysecretsanta.com/mcp).

### Is the Pick My Secret Santa MCP server safe to use?

Pick My Secret Santa scores 70 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 Pick My Secret Santa MCP server expose?

Pick My Secret Santa exposes 3 tools: pick_secret_santa_gift, explain_secret_santa_rules, plan_secret_santa_setup. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

### Does the Pick My Secret Santa MCP server require authentication?

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

### Is the Pick My Secret Santa MCP server still maintained?

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

VerifyMCP ran 12 checks on Pick My Secret Santa, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Pick My Secret Santa: HTTPS. 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://mcp.pickmysecretsanta.com/mcp
- Repository: https://github.com/wdlcmu/pick-my-secret-santa
- Website: https://pickmysecretsanta.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-pickmysecretsanta-pick-my-secret-santa/mcp
