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.

Pour Picks

REMOTE · MCP.POURPICKS.APP · 2 COMPONENTS

Search the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices.

−3 this week 83 Trust /100

Last scanned (7 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 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 Security80
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 731 tokens (~91/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 17 Oct 26 0
    • Server version: 1.0.2 → 1.0.4 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +59
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.87 ▲ functional
  • 7 Oct 26 −56
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.63 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 5 Oct 26 +1

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

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 5 Nov 2026 · Probed https://mcp.pourpicks.app/?src=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.pourpicks.app CN=YE2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA384 57ac90b4b77809f7818106373b0366e6db1
SANs: mcp.pourpicks.app
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.pourpicks.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
pourpicks.app. absent 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=31536000; includeSubDomains; preload

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.pourpicks.app/?src=registry Verified 200
http (plaintext) http://mcp.pourpicks.app/?src=registry HTTPS enforced 301 https://mcp.pourpicks.app/?src=registry
MCP tools · 8 exposed · ~731 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
compare_bottles ~65

Side-by-side comparison of two bottles: proof, age, price, flavor profile, shared and distinct tasting notes, and community ratings.

NameTypeReqDescription
bottle_astringyesFirst bottle — UUID or name
bottle_bstringyesSecond bottle — UUID or name

No output schema declared.

No examples provided.

find_cheaper_alternative ~69

Bottles in the same style with a similar flavor profile at a lower price than the given bottle. Use for 'what tastes like X but costs less' questions.

NameTypeReqDescription
bottle_idstringyesBottle UUID or name
limitinteger–Max results (default 5)

No output schema declared.

No examples provided.

find_similar ~72

Bottles with a similar flavor profile to a given bottle, ranked by shared flavor notes and body/sweetness/char proximity. Deterministic scoring over the Pour Picks structured tasting data.

NameTypeReqDescription
bottle_idstringyesBottle UUID or name
limitinteger–Max results (default 5)

No output schema declared.

No examples provided.

get_bottle ~65

Detailed record for one bottle: tasting profile, flavor notes, pairings, price, community ratings. Accepts a Pour Picks bottle ID (UUID) or a bottle name.

NameTypeReqDescription
slug_or_idstringyesBottle UUID or a name like 'Eagle Rare 10'

No output schema declared.

No examples provided.

get_recommendations ~142

Personalized bottle picks from taste preferences (flavor keywords like 'caramel', 'smoke', 'cherry'), a budget in USD, and an occasion (e.g. 'gift', 'everyday sipper', 'celebration', 'introducing a friend to bourbon').

NameTypeReqDescription
budgetnumber–Max price in USD
categorystring–Restrict to one spirit category
limitinteger–Max results (default 5)
occasionstring–What the bottle is for
taste_preferencesarrayyesFlavor keywords the drinker enjoys, e.g. ['caramel','vanilla','oak']

No output schema declared.

No examples provided.

pour_tonight_suggestion ~104

A pour suggestion for right now, based on mood (e.g. 'unwinding', 'celebratory', 'contemplative'), occasion (e.g. 'nightcap', 'with friends', 'after dinner'), and season.

NameTypeReqDescription
moodstring–How you're feeling
occasionstring–The setting
seasonstring–Season to weight the pick toward — heavier, warming pours in winter; lighter in summer

No output schema declared.

No examples provided.

search_bottles ~147

Full-text search across 4,700+ bourbons, ryes, scotches, and other spirits in the Pour Picks database. Filter by category, price (USD), and proof. Returns structured tasting profiles with source attribution.

NameTypeReqDescription
categorystring–Spirit category filter
limitinteger–Max results (default 10, max 10)
price_maxnumber–Maximum price in USD
price_minnumber–Minimum price in USD
proof_maxnumber–Maximum proof
proof_minnumber–Minimum proof
querystring–Free-text search: distillery, bottle name, or expression

No output schema declared.

No examples provided.

trending_bottles ~67

Bottles Pour Picks users are adding to their cellars most over the last 30 days (falls back to catalog popularity when live activity data is unavailable). The method used is labeled in the response.

NameTypeReqDescription
limitinteger–Max results (default 10, max 10)

No output schema declared.

No examples provided.

Install

How do I install the Pour Picks MCP server?

Pour Picks is a hosted endpoint at https://mcp.pourpicks.app/?src=registry, 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.pourpicks.app

# add to Claude Code
claude mcp add --transport http bguillow-rgb-pour-picks 'https://mcp.pourpicks.app/?src=registry'
Common questions

What is the Pour Picks MCP server?

Pour Picks is an MCP server listed in the public MCP registry as io.github.bguillow-rgb/pour-picks. Search the Pour Picks bourbon & whiskey database: 4,700+ bottles with tasting profiles and prices. This page covers its hosted endpoint (https://mcp.pourpicks.app/?src=registry).

Is the Pour Picks MCP server safe to use?

Pour Picks scores 83 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 Pour Picks MCP server expose?

Pour Picks exposes 8 tools: search_bottles, get_bottle, find_similar, find_cheaper_alternative, get_recommendations, and 3 more. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.

Does the Pour Picks MCP server require authentication?

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

Is the Pour Picks MCP server still maintained?

Pour Picks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.