mcpbeat Sign in

Beyond Wine MCP Server

not responding

Beyond Wine is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Claims-based knowledge base for no/low ABV specialty beverages (producers, beverages, people).

Uptime history 52 days of history · worst day 97%
52 days agonow
98.9%
Uptime 24h
90 of 91 checks
11
Tools
read from the server
505 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 September 2026. No other catalogue keeps this.

23 Sep 4 tool descriptions were rewritten get_beverage, get_claim, get_entity and 1 more
13 Sep 6 tool descriptions were rewritten8 times that day get_beverage, get_claim, get_entity and 3 more
13 Sep a tool changed the parameters it asks for search_claims
13 Sep a tool changed version
12 Sep 2 tool descriptions were rewritten get_beverage, get_producer
and 2 more, back to 12 September 2026

Beyond Wine does not always answer

Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

Available tools 11

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

beverage
get_beverage
Retrieve a published beverage profile and claim previews. Find the exact slug with search_beverages; never invent it. Check the returned producer against the question. To provide a sourced fact, call get_claim on a returned claim_uid, or search_claims with entity_type=beverage and this slug. Profile previews alone do not contain source lists. Cite an actual returned source or claim URL.
beverages
search_beverages
Find a beverage by name or alias. Start here for drink names, not search_producers. q matches a beverage name, alias OR producer name; a combined producer-plus-product phrase may not match. If empty, try a distinctive product word or search the producer separately and inspect its lineup. Use producer with an exact producer slug to list its drinks. Verify the returned beverage name and producer, copy its exact slug into get_beverage, then get_claim for source provenance. Do not infer nonexistence from an empty search or silently substitute another product.
claim
get_claim
Retrieve a published claim with provenance.sources and version history. Copy claim_uid from a profile or claim search. Use this to check a source behind a profile claim preview; cite an actual returned source or citation_url and preserve its source attribution. One claim does not establish that no other records or sources exist. Preserve the source's exact alcohol wording. 0% and 0.0% are different wording, but that difference does not by itself establish different measured trace-alcohol thresholds. 'Below 0.5%' is an upper-bound declaration; these declarations do not by themselves prove measurement or laboratory testing. Do not infer that alcohol is absent from ingredients or production methods.
claims
search_claims
Find published claims with their source provenance. To answer about a specific drink or producer, supply BOTH entity_type and its exact returned entity_slug. For a sourced statement, these two filters are normally sufficient: omit claim_type and reliability_class unless needed. claim_type is a record format (atomic_fact, structured_fact, editorial_claim), not a topic such as ingredients or collaboration. Inspect provenance.sources and describe producer statements, interviews, and independent reporting with their actual attribution. Follow meta.has_more pagination before making negative findings about the queried records and filters. Limit those findings to sources actually inspected; completing pagination does not establish that evidence is absent elsewhere. Preserve the source's exact alcohol wording. 0% and 0.0% are different wording, but that difference does not by itself establish different measured trace-alcohol thresholds. 'Below 0.5%' is an upper-bound declaration; these declarations do not by themselves prove measurement or laboratory testing. Do not infer that alcohol is absent from ingredients or production methods.
context
get_context
Retrieve a token-bounded context bundle for a Beyond Wine topic, including entity summary and optional claims or graph data.
entities
list_entities
List published entity profiles in the Beyond Wine knowledge base by type.
entity
get_entity
Retrieve a published entity profile with structured data and claim previews. For source provenance, follow a returned claim_uid with get_claim; cite actual returned source or claim URLs. Profiled entities (producers, beverages, people, restaurants) are independent businesses documented by Beyond Wine, not brands of it.
graph
get_graph
Retrieve direct relationship neighbors for an entity profiled in the Beyond Wine knowledge base.
ontology
get_ontology
Retrieve the Beyond Wine ontology, entity types, relationship types, and semantic scales.
producer
get_producer
Retrieve a specific producer documented by Beyond Wine, such as MURI or AMA Brewery. Includes the producer's published beverage lineup under data.beverages. Use search_producers first when the producer slug is unknown.
producers
search_producers
Find producers by name, country, city, ingredient or technique. This searches producers, not beverage names: use search_beverages for a drink. If empty, try a shorter producer name or remove extra filters. Copy the exact returned slug into get_producer, whose data.beverages contains the lineup.

Endpoints

URLTransportStateLatencyChecked
https://beyond.wine/mcp streamable-http answering 8071 ms 6 min ago

Alternatives to Beyond Wine

same job, measured the same way
mFlow
by m-flow

Shared task board and knowledge base for AI coding agents

answering
Factsets MCP Server
by joshua-auchincloss

An MCP server that provides a local, persistent, self-maintaining knowledge base for AI agents

40 installs/wk local only
I
Nol MCP
by yawlabs

nol MCP server -- search, cited Q&A, and pages over your team's knowledge base

local only
MCP Pickaxe
by aplaceforallmystuff

MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics

50 installs/wk local only
Swiss Truth MCP
by swisstruthorg

Verified knowledge base for AI agents — stop hallucinations with certified facts.

27 installs/wk local only
Simplepush
by simplepu

Send tasks and notifications to people's phones. Answers build a queryable knowledge base.

73 installs/wk answering
Prior
by cg3

Shared knowledge base for AI agents. Search and contribute solutions to technical problems.

32 installs/wk answering
Sprintra
by sprintra-io

The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP.

29 installs/wk answering

Beyond Wine — questions

Answers built from our own checks of this server.

What can Beyond Wine do?
It exposes 11 tools, read directly from the server on our last check. Among them: get_beverage, get_claim, get_context, get_entity, get_graph, get_ontology and 5 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 Beyond Wine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 505 ms. The bar chart above shows every period we have measured.
The registry lists Beyond Wine as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Beyond Wine?
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 Beyond Wine need an API key?
No. Beyond Wine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Beyond Wine?
It answers our handshake in 505 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.