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.

Present Picker

REMOTE · MCP.THEPRESENTPICKER.COM

Gift recommendations matched to the person, the occasion, and your budget.

+3 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1941 tokens (~647/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
What we tested

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 →

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

  • 19 Nov 26 +1

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

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

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.thepresentpicker.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thepresentpicker.com CN=YE2,O=Let's Encrypt,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA384 56cc027bb08439083646f9bb83bad87b825
SANs: *.thepresentpicker.com, thepresentpicker.com
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 insecure

Validation of mcp.thepresentpicker.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thepresentpicker.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.thepresentpicker.com/mcp Verified 200
http (plaintext) http://mcp.thepresentpicker.com/mcp Inconclusive 405
MCP tools · 3 exposed · ~1,314 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
get_gift ~165

Picked for them, not the store: returns the full detail for one gift idea from the bank: description, why-line, a buying-notes line (what to look for and what to avoid when buying it), a care-and-pairing tip, budget band, who it suits, its interests and styles, and up to 3 similar ideas, each with its own link. Accepts a gift id returned by pick_gift or search_gifts, or a gift name like 'cast iron skillet'. When nothing matches, the result says so and gives example ids.

NameTypeReqDescription
gift_idstringyesGift id from pick_gift or search_gifts (e.g. 'cast-iron-skillet-10-inch-pre-seasoned'), or a gift name.

No output schema declared.

No examples provided.

pick_gift ~872

Returns up to 5 gift ideas from a fixed bank of 255 checked gift ideas, matched to who the gift is for, a budget band, interests, and an optional gift style. Each pick has a one-line description, a why-line explaining the fit, one buying note, its budget band, a link that opens that exact idea on thepresentpicker.com, and a photo link to the picture on that idea's page. Some picks carry a good_to_know line: a plain handling fact the bank states for that idea, such as the weight of a cast iron skillet, present only where the bank states one. The result also carries lead_pick — the top pick at full bank depth, with its buying notes (what to look for and what to avoid) and a care-and-pairing tip — more_ideas with the remaining picks under the heading 'More ideas if that one misses', and answer_text, that focused answer formatted as text: it opens by naming who the gift is for, in the caller's words, and how the top pick fits them. Recipient and budget band are hard filters. A style, when given, is a hard filter too: every pick carries the style, and the result reports total_matches and, on a style call, style_matches. Interests narrow the pool, and picks matching more interests rank first. keyword names a specific item the buyer asked for: picks matching every keyword word rank first inside the same filtered pool, carry their full bank detail, and the result reports keyword_matches (a miss is stated in the note, and a miss carries no lead_pick). exclude names an item the person already has: matching picks are dropped before ranking, and the result notes the drop. A recipient-only call (no budget, interest, style, or keyword) returns a spread across all budget bands, led by a mid-band pick and never by the $100+ band — a starting sampler, not a tailored list. A 'teen' recipient maps to the kid pool and carries a recipient_note explaining how teen picks are drawn from that pool. A 'coworker' recipient draws on the bank's coworker shelf — picks tagged for coworkers, rank…

NameTypeReqDescription
budgetstring–Optional budget band: 'under $25', '$25-$50', '$50-$100', or '$100+'. Omit to search every band.
excludestring–Optional: an item the user says the person already has, in plain words, e.g. 'cast iron skillet'. Picks matching it are dropped and the drop is disclosed in the note.
interestsarray–Optional: what they are into. Bank interests: cooking, outdoors, tech, books, fitness, cozy, music, games, gardening, travel, science.
keywordstring–Optional: the specific item the buyer named, in plain words, e.g. 'plant pot', 'bookmark', 'board game', 'star map'. When the bank holds that item for this recipient and budget, it ranks first.
recipientstringyesWho the gift is for: 'mom', 'dad', 'partner', 'grandparent', 'friend', 'kid', 'coworker', or 'other'. Plain words work too, e.g. 'my wife', 'grandma', 'my son', 'my colleague'. 'teen' and 'teenager'…
stylestring–Optional gift style: 'practical', 'fun', 'sentimental', or 'experience'. When given, every pick carries this style.

No output schema declared.

No examples provided.

search_gifts ~277

Picked for them, not the store: searches the fixed bank of 255 gift ideas by interest, by keyword, or by both, with optional recipient and budget-band filters. Returns up to 10 matches in bank order, each with a one-line description, a why-line, one buying note, its budget band, a photo link, and a link that opens that exact idea on thepresentpicker.com. The result reports the total number of matches, including when there are none.

NameTypeReqDescription
budgetstring–Optional filter: 'under $25', '$25-$50', '$50-$100', or '$100+'.
intereststring–Optional: one bank interest: cooking, outdoors, tech, books, fitness, cozy, music, games, gardening, travel, science.
keywordstring–Optional: plain words to match against gift names and descriptions, e.g. 'coffee', 'science kit', 'board game'. Every word must match, so a named item finds its exact bank entry.
limitnumber–Optional: max results to return, 1 to 10. Default 10.
recipientstring–Optional filter: 'mom', 'dad', 'partner', 'grandparent', 'friend', 'kid', 'coworker', or 'other'.

No output schema declared.

No examples provided.

Install

How do I install the Present Picker MCP server?

Present Picker is a hosted endpoint at https://mcp.thepresentpicker.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.thepresentpicker.com

# add to Claude Code
claude mcp add --transport http com-thepresentpicker-present-picker 'https://mcp.thepresentpicker.com/mcp'
Common questions

What is the Present Picker MCP server?

Present Picker is an MCP server listed in the public MCP registry as com.thepresentpicker/present-picker. Gift recommendations matched to the person, the occasion, and your budget. This page covers its hosted endpoint (https://mcp.thepresentpicker.com/mcp).

Is the Present Picker MCP server safe to use?

Present Picker 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 Present Picker MCP server expose?

Present Picker exposes 3 tools: pick_gift, search_gifts, get_gift. Their descriptions and schemas cost roughly 1,314 tokens of context every time the server is loaded.

Does the Present Picker MCP server require authentication?

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

Is the Present Picker MCP server still maintained?

Present Picker 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 Present Picker MCP server?

VerifyMCP ran 12 checks on Present Picker, 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 Present Picker: 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.