# Pour Picks (remote · mcp.pourpicks.app)

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

- Trust score: 83/100 (high trust)
- Change this week: −3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.pourpicks.app`: 83/100 (this document), [markdown](https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp.md), [page](https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp)
- npm · `pour-picks-mcp`: 76/100, [markdown](https://verifymcp.io/servers/bguillow-rgb-pour-picks/pour-picks-mcp.md), [page](https://verifymcp.io/servers/bguillow-rgb-pour-picks/pour-picks-mcp)

## Channel facts

- Endpoint: `https://mcp.pourpicks.app/?src=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 731 tokens (~91/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http bguillow-rgb-pour-picks 'https://mcp.pourpicks.app/?src=registry'
```

### Cursor

```json
{
  "mcpServers": {
    "bguillow-rgb-pour-picks": {
      "url": "https://mcp.pourpicks.app/?src=registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bguillow-rgb-pour-picks": {
      "type": "http",
      "url": "https://mcp.pourpicks.app/?src=registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bguillow-rgb-pour-picks]
url = "https://mcp.pourpicks.app/?src=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bguillow-rgb-pour-picks": {
      "type": "remote",
      "url": "https://mcp.pourpicks.app/?src=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bguillow-rgb-pour-picks --url 'https://mcp.pourpicks.app/?src=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bguillow-rgb-pour-picks:
    url: "https://mcp.pourpicks.app/?src=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "bguillow-rgb-pour-picks": {
      "Transport": "http",
      "Url": "https://mcp.pourpicks.app/?src=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bguillow-rgb-pour-picks -t streamable-http -u 'https://mcp.pourpicks.app/?src=registry'
```

### Other

```json
{
  "mcpServers": {
    "bguillow-rgb-pour-picks": {
      "type": "http",
      "url": "https://mcp.pourpicks.app/?src=registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, −3)

- [functional] Stability: pass → 0.80

### 2026-10-17 (score 86, 0)

- [functional] Server version: 1.0.2 → 1.0.4

### 2026-10-16 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-10-15 (score 86, +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.

### 2026-10-13 (score 85, +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.

### 2026-10-12 (score 84, +59)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.87

### 2026-10-07 (score 25, −56)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.63 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-05 (score 81, +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.

## MCP tools (8)

### `search_bottles` (~147 tokens)

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.

Input parameters:

- `category` (string): Spirit category filter
- `limit` (integer): Max results (default 10, max 10)
- `price_max` (number): Maximum price in USD
- `price_min` (number): Minimum price in USD
- `proof_max` (number): Maximum proof
- `proof_min` (number): Minimum proof
- `query` (string): Free-text search: distillery, bottle name, or expression

### `get_bottle` (~65 tokens)

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

Input parameters:

- `slug_or_id` (string, required): Bottle UUID or a name like 'Eagle Rare 10'

### `find_similar` (~72 tokens)

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.

Input parameters:

- `bottle_id` (string, required): Bottle UUID or name
- `limit` (integer): Max results (default 5)

### `find_cheaper_alternative` (~69 tokens)

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.

Input parameters:

- `bottle_id` (string, required): Bottle UUID or name
- `limit` (integer): Max results (default 5)

### `get_recommendations` (~142 tokens)

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

Input parameters:

- `budget` (number): Max price in USD
- `category` (string): Restrict to one spirit category
- `limit` (integer): Max results (default 5)
- `occasion` (string): What the bottle is for
- `taste_preferences` (array, required): Flavor keywords the drinker enjoys, e.g. ['caramel','vanilla','oak']

### `compare_bottles` (~65 tokens)

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

Input parameters:

- `bottle_a` (string, required): First bottle — UUID or name
- `bottle_b` (string, required): Second bottle — UUID or name

### `trending_bottles` (~67 tokens)

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.

Input parameters:

- `limit` (integer): Max results (default 10, max 10)

### `pour_tonight_suggestion` (~104 tokens)

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

Input parameters:

- `mood` (string): How you're feeling
- `occasion` (string): The setting
- `season` (string): Season to weight the pick toward — heavier, warming pours in winter; lighter in summer

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 86
- 2026-10-29: 86
- 2026-10-28: 86
- 2026-10-27: 86
- 2026-10-26: 86
- 2026-10-25: 86
- 2026-10-24: 86
- 2026-10-23: 86
- 2026-10-22: 86
- 2026-10-21: 86
- 2026-10-20: 86
- 2026-10-19: 86
- 2026-10-18: 86
- 2026-10-17: 86
- 2026-10-16: 86
- 2026-10-15: 86
- 2026-10-14: 85
- 2026-10-13: 85
- 2026-10-12: 84
- 2026-10-10: 25
- 2026-10-07: 25
- 2026-10-05: 81
- 2026-10-04: 80
- 2026-10-03: 80

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

### What did VerifyMCP test on the Pour Picks MCP server?

VerifyMCP ran 13 checks on Pour Picks, 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.

## Links

- Remote endpoint: https://mcp.pourpicks.app/?src=registry
- Repository: https://github.com/bguillow-rgb/pour-picks-mcp
- Website: https://pourpicks.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp.json
- HTML version of this page: https://verifymcp.io/servers/bguillow-rgb-pour-picks/mcp