Remote MCP · Endpoint

Secret Santa Raffle MCP server

No. Secret Santa Raffle answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.secretsantaraffle.net/claude/mcp

The last check completed an MCP handshake.

Registry name
net.secretsantaraffle/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
234 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Organise a Secret Santa from Claude or ChatGPT. Matchings never appear in the chat.
Listing
From the official MCP registry (active).
Recent checks of Secret Santa Raffle
CheckedResultHandshake
1 hour agoHandshake completed234 ms
1 day agoHandshake completed97 ms
2 days agoHandshake completed56 ms
3 days agoHandshake completed56 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed69 ms
6 days agoHandshake completed81 ms
8 days agoHandshake completed75 ms
11 days agoHandshake completed44 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed74 ms
18 days agoHandshake completed64 ms
20 days agoHandshake completed216 ms
22 days agoHandshake completed56 ms
24 days agoHandshake completed60 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Secret Santa Raffle and makes no claim about it beyond what these checks measured.