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.

Santa's Calling

REMOTE · SANTASCALLING.CO.UK

Gift a child a live, personalised phone call from Santa (UK, £6.99). Buyer pays on Stripe.

+3 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

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 Security83
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 561 tokens (~140/item across 4 items; 4 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (25% 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 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 21 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.

  • 19 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.

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +4
    • DNSSEC: fail → pass ▲ security
    • HSTS header: fail → pass ▲ security
  • 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://santascalling.co.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=santascalling.co.uk CN=YE2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 593a81668b15e91d41907cb906a6e30cfdd
SANs: *.santascalling.co.uk, santascalling.co.uk
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of santascalling.co.uk. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
santascalling.co.uk. DS published 2371 13 Verified
santascalling.co.uk. Verified address RRset verified with the apex keys
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=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://santascalling.co.uk/mcp Verified 200
http (plaintext) http://santascalling.co.uk/mcp HTTPS enforced 301 https://santascalling.co.uk/mcp
MCP tools · 4 exposed · ~438 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
buy_gift_call ~298

Start buying a gift: a phone call from Santa for a child in the UK, £6.99. Returns `checkout_url`, a Stripe Checkout page where the buyer pays by card, Apple Pay or Google Pay (the link works for 30 minutes). Nothing is charged until they pay there. Once paid, we email the gift link to the buyer (and to recipient_email, if given). The parent opens it when the child is ready, adds the child's details, confirms their mobile by text, and Santa rings straight away. Usable until 24 December. Args: buyer_name: Who the gift is from, as the family will see it (e.g. "Grandma Jean"). buyer_email: The buyer's email, for the receipt and the gift link. recipient_name: Optional. Who it's for, e.g. "Sarah & Tom" (the parents) or the family name. recipient_email: Optional. We email the gift link straight to them once it's paid. message: Optional. A short message shown with the gift (up to 300 characters). promo_code: Optional. A promotion code, if the buyer has one.

NameTypeReqDescription
buyer_emailstringyes–
buyer_namestringyes–
messagestring––
promo_codestring––
recipient_emailstring––
recipient_namestring––

No output schema declared.

No examples provided.

check_gift_status ~51

Whether a gift started with buy_gift_call has been paid. Once paid, includes the gift link the family uses to book the call (it's also emailed).

NameTypeReqDescription
gift_idstringyes–

No output schema declared.

No examples provided.

get_faq ~33

Parents' frequently asked questions: what happens on the call, cost, safety, which phones, missed calls, refunds.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

get_info ~56

What Santa's Calling is: a live, personalised phone call from Santa for a child in the UK (£6.99, about 3 minutes, ages 2-16). Includes price, how a gift works, safety and links.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Santa's Calling MCP server?

Santa's Calling is a hosted endpoint at https://santascalling.co.uk/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 · santascalling.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-santascalling-santas-calling 'https://santascalling.co.uk/mcp'
Common questions

What is the Santa's Calling MCP server?

Santa's Calling is an MCP server listed in the public MCP registry as uk.co.santascalling/santas-calling. Gift a child a live, personalised phone call from Santa (UK, £6.99). Buyer pays on Stripe. This page covers its hosted endpoint (https://santascalling.co.uk/mcp).

Is the Santa's Calling MCP server safe to use?

Santa's Calling scores 77 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 Santa's Calling MCP server expose?

Santa's Calling exposes 4 tools: get_info, get_faq, buy_gift_call, check_gift_status. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.

Does the Santa's Calling MCP server require authentication?

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

Is the Santa's Calling MCP server still maintained?

Santa's Calling 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 Santa's Calling MCP server?

VerifyMCP ran 13 checks on Santa's Calling, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.