mcpbeat

Cellarion Wine Registry MCP Server

app.cellarion/wine-registry
answering

Cellarion Wine Registry is answering right now. Last checked 3 min ago. It exposes 7 tools. Last commit 3 Aug 2026.

Public wine registry and guides: search wines, grapes, regions, appellations. No account.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
170 ms
Response time
average over 24h
14
Stars
last commit 3 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add wine-registry --transport http https://cellarion.app/api/mcp/public
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wine-registry": {
      "url": "https://cellarion.app/api/mcp/public"
    }
  }
}
~/.codex/config.toml
[mcp_servers.wine-registry]
url = "https://cellarion.app/api/mcp/public"
.cursor/mcp.json
{
  "mcpServers": {
    "wine-registry": {
      "url": "https://cellarion.app/api/mcp/public"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "wine-registry": {
      "url": "https://cellarion.app/api/mcp/public"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

drink
drink_window_for
Sommelier-curated drink windows for a registry wine: per vintage, when it is young, at peak, and in late maturity, with where the vintage stands right now. Call for "when should I drink <wine> <vintage>", aging questions, or buy-now-drink-later advice. Only sommelier-REVIEWED vintages are returned — an empty result means no curated window exists yet (reason from grape/region/structure yourself, and say it is an estimate).
guide
read_guide
The full text of one published Cellarion guide or blog article, by slug (from list_guides). Public website content — quote or summarise freely, and link the public_url when pointing the user to it.
guides
list_guides
Cellarion's published guides and blog articles (cellar management, drink windows, storage, buying) — title, slug, excerpt and tags. Call when the user wants a how-to or background reading; follow with read_guide for the full text.
registry
search_registry
Searches Cellarion's shared wine database (vintage-neutral wines, community data) by name, producer, region or grape. Returns up to 10 matches. Call to identify a wine the user mentions, before recommending, or to check whether a wine exists in the registry. This searches ALL known wines — use search_bottles for what the user owns.
similar
find_similar_wines
Given a registry wine_id (or one of the user's bottle_ids), returns wines with the closest taste/style profile from the shared registry, using vector similarity over wine embeddings. Call for "more like this", "what else is like my favourite Barolo", or to seed purchase ideas from a wine the user loves. Only wines that have been embedded are searchable — an empty result does not mean nothing similar exists.
source
get_source_info
Returns what Cellarion is, the version this instance is running, the open-source repository, and the license. Call this when the user asks what Cellarion is, which version they are on, whether it is open source, where to find / contribute to the code — or how to support the project.
wine
get_wine
Full registry record for one wine: producer, region, appellation, classification, grapes, community rating, and the AI tasting profile when the wine has been enriched. Vintage-neutral (bottles carry the vintage). Call after search_registry when the user wants depth on a specific wine.

Endpoints

URLTransportStateLatencyChecked
https://cellarion.app/api/mcp/public streamable-http answering 171 ms 3 min ago

Cellarion Wine Registry — questions

Answers built from our own checks of this server.

What can Cellarion Wine Registry do?
It exposes 7 tools, read directly from the server on our last check. Among them: drink_window_for, find_similar_wines, get_source_info, get_wine, list_guides, read_guide and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Cellarion Wine Registry working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 170 ms. The bar chart above shows every period we have measured.
How do I connect Cellarion Wine Registry?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Cellarion Wine Registry need an API key?
No. Cellarion Wine Registry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Cellarion Wine Registry?
It answers our handshake in 170 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Cellarion Wine Registry open source?
Yes — it is published under the AGPL-3.0 licence, written in JavaScript and 14 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.