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.

Zovo Gift List

REMOTE · GIFT-LIST.ZOVO.ONE

Make a wishlist page that friends and family can claim gifts from.

+3 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

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 Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 899 tokens (~224/item across 4 items; 3 tools + 1 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 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
  • Structured output schemas are declared (100% 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 3 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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.

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

  • 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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 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.

  • 9 Nov 26 0
    • 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://gift-list.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.zovo.one
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 gift-list.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. 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
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gift-list.zovo.one/mcp Verified 200
http (plaintext) http://gift-list.zovo.one/mcp HTTPS enforced 301 https://gift-list.zovo.one/mcp
MCP tools · 3 exposed · ~787 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
create_gift_list ~336

Use this when the user wants a wishlist or gift registry page that friends and family can claim gifts from, for a birthday, Christmas or another holiday, a baby shower or a wedding. Takes a title, 1 to 80 items (name, optional note, price range text, store name and quantity up to 20) and whether the owner wants to see claims (hidden by default). Publishes a hosted page: friends see what is still available and claim it with their first name. Returns a shared link for friends and a private owner link. Does not accept links in items (name the store instead). Does not buy or track gifts.

NameTypeReqDescription
itemsarrayyesThe wishlist, e.g. [{"name":"Wool scarf","price":"$20-30"},{"name":"Hiking socks","quantity":2}].
notestring–Short note for friends, e.g. Sizes: shirt M, shoes 38. No links.
occasion_datestring–Date of the birthday or holiday as YYYY-MM-DD, e.g. 2026-12-25.
owner_namestring–First name of the person the gifts are for, e.g. Maya.
show_claims_to_ownerboolean–true = the owner page shows who claimed what. Default false (claims hidden to keep the surprise).
time_zonestring–IANA time zone for claim times, e.g. Europe/Berlin. Default America/New_York.
titlestringyesList title shown on the page, e.g. Maya's 8th birthday.
NameTypeReqDescription
changesarrayyes–
claim_countnumberyes–
claims_hiddenbooleanyes–
closedbooleanyes–
expires_atstringyes–
fully_claimednumber––
item_countnumberyes–
itemsarrayyes–
items_shownobject––
manageUrlstringyes–
occasion_datestring|nullyes–
publicUrlstringyes–
removed_claimsarray––
removed_claims_totalnumber––
titlestringyes–
warningsarrayyes–

No examples provided.

show_gift_list_status ~133

Use this when the list owner asks how their gift list is going, how many claims it has, or (when they chose to see claims) who is getting what. Takes the private owner link (it contains /m/). When claims are hidden, returns only the number of claims, not which items were claimed. Does not change anything. Does not work with the shared link.

NameTypeReqDescription
manage_linkstringyesThe private owner link from when the list was made, e.g. https://gift-list.zovo.one/m/AbC.../XyZ... (it contains /m/).
NameTypeReqDescription
changesarrayyes–
claim_countnumberyes–
claims_hiddenbooleanyes–
closedbooleanyes–
expires_atstringyes–
fully_claimednumber––
item_countnumberyes–
itemsarrayyes–
items_shownobject––
manageUrlstringyes–
occasion_datestring|nullyes–
publicUrlstringyes–
removed_claimsarray––
removed_claims_totalnumber––
titlestringyes–
warningsarrayyes–

No examples provided.

update_gift_list ~318

Use this when the list owner wants to change an existing gift list: add items, remove items, change a quantity, show or hide claims, rename it, or close or reopen it for claims. Takes the private owner link. Removing an item hides it from friends and from the list export; claims already made on it are kept and count in the claim total (the owner page and export list them only when the owner chose to see claims). Does not edit friends' claims and does not make a new list.

NameTypeReqDescription
add_itemsarray–Items to add, e.g. [{"name":"Puzzle 1000 pieces","price":"$15"}].
closedboolean–true = close the list to new claims; false = reopen it.
manage_linkstringyesThe private owner link from when the list was made, e.g. https://gift-list.zovo.one/m/AbC.../XyZ... (it contains /m/).
notestring–New note for friends; an empty string removes it.
remove_itemsarray–Exact names of items to remove, e.g. ["Wool scarf"].
set_quantitiesarray–New quantities, e.g. [{"name":"Hiking socks","quantity":3}].
show_claims_to_ownerboolean–true = show who claimed what on the owner page; false = hide claims.
titlestring–New title, e.g. Maya's 9th birthday.
NameTypeReqDescription
changesarrayyes–
claim_countnumberyes–
claims_hiddenbooleanyes–
closedbooleanyes–
expires_atstringyes–
fully_claimednumber––
item_countnumberyes–
itemsarrayyes–
items_shownobject––
manageUrlstringyes–
occasion_datestring|nullyes–
publicUrlstringyes–
removed_claimsarray––
removed_claims_totalnumber––
titlestringyes–
warningsarrayyes–

No examples provided.

Install

How do I install the Zovo Gift List MCP server?

Zovo Gift List is a hosted endpoint at https://gift-list.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.

remote · gift-list.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-gift-list 'https://gift-list.zovo.one/mcp'
Common questions

What is the Zovo Gift List MCP server?

Zovo Gift List is an MCP server listed in the public MCP registry as io.github.theluckystrike/gift-list. Make a wishlist page that friends and family can claim gifts from. This page covers its hosted endpoint (https://gift-list.zovo.one/mcp).

Is the Zovo Gift List MCP server safe to use?

Zovo Gift List 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 Gift List MCP server expose?

Zovo Gift List exposes 3 tools: create_gift_list, show_gift_list_status, update_gift_list. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.

Does the Zovo Gift List MCP server require authentication?

No. We connected to Zovo Gift List without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Zovo Gift List MCP server still maintained?

Zovo Gift List 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 Gift List MCP server?

VerifyMCP ran 14 checks on Zovo Gift List, 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.