Pick My Secret Santa
REMOTE · MCP.PICKMYSECRETSANTA.COM
Runs a Secret Santa name draw in chat and gives each person a private reveal link.
Available components
Last scanned (14 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 21 Nov 26 +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.
- 20 Nov 26 0
- 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 security
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 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.
- 7 Nov 26 +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.
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://mcp.pickmysecretsanta.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pickmysecretsanta.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8bb83e86464daaf0e02952aa03058ba |
| SANs: pickmysecretsanta.com, mcp.pickmysecretsanta.com, *.mcp.pickmysecretsanta.com | ||||||
| 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 mcp.pickmysecretsanta.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| pickmysecretsanta.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pickmysecretsanta.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pickmysecretsanta.com/mcp | Inconclusive | 405 |
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 →
explain_secret_santa_rules Explain Secret Santa rules ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Which rule to explain. |
No output schema declared.
No examples provided.
pick_secret_santa_gift Pick a Secret Santa gift ~373
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
plan_secret_santa_setup Plan a Secret Santa setup ~494
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.pickmysecretsanta.com
claude mcp add --transport http com-pickmysecretsanta-pick-my-secret-santa 'https://mcp.pickmysecretsanta.com/mcp'
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.