mcpbeat Sign in

openwein.de — deutsche Weingüter und Weinfeste MCP Server

answering

openwein.de — deutsche Weingüter und Weinfeste is answering right now. Last checked 14 min ago. It exposes 12 tools.

German wineries, wine towns and wine festivals: 5.900 entries in 13 regions. Read-only, no key.

Uptime history 30 days of history
30 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
180 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 10

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

30 Aug 2 tool descriptions were rewritten get_winery, search_wineries
30 Aug a tool changed the parameters it asks for search_wineries
29 Aug 4 tools appeared get_glossary, get_lage, get_vintage and 1 more
29 Aug 2 tool descriptions were rewritten get_winery, search_lagen
27 Aug a tool description was rewritten list_events

Nothing serious here today

Today is the operative word: we check openwein.de — deutsche Weingüter und Weinfeste every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 14 min ago.

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

Available tools 12

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

events
list_events
Upcoming German wine events — Weinfeste, Hoffeste, Weinproben, Weinwanderungen — across all regions, or filtered by region, town or a radius around a point. Every event carries the source it was verified against and a link to its own page; the result also names the human-readable calendar page for the same selection, which is the thing to hand a person rather than retelling a list that changes daily.
glossary
get_glossary
German wine terms explained, with their regional variants. Useful because the same institution carries different names by region: the seasonal tavern a winery runs itself is a Straußwirtschaft on the Mosel and in the Palatinate, a Besenwirtschaft in Württemberg and a Hecken- or Häckerwirtschaft in Franconia — and none of them is the same as a Gutsausschank, which may open all year. Omit the term to list all entries.
lage
get_lage
One Einzellage in full: Bereich, Großlage, planted area, the official vineyard number, the municipalities it spans, and the wineries of its town. It is NOT known which wineries actually farm vines in a given Lage — no public register holds that — so the wineries listed are those located in the town, and the answer says so.
lagen
search_lagen
Search the 1.646 registered German Einzellagen (single vineyard sites) by name, town or region. The Einzellage is the smallest origin unit in German wine law and the name that appears on the label after the town ("Forster Ungeheuer", "Wehlener Sonnenuhr"). For the six regions of Rhineland-Palatinate the data is the official register of the Chamber of Agriculture and carries the vineyard number, Bereich, Großlage, planted area and the legal boundary; the Rheingau is currently sourced from Wikipedia and has no boundary. Note that a Lage name says where a wine grew, not how good it is. Where a winery names a Lage on its own website, get_lage returns that winery with the sentence it appeared in.
region
get_region
Full description of one wine region: its history, grape varieties and terroir, plus its wine towns and upcoming events.
regions
list_regions
Lists all 13 German wine regions (Anbaugebiete) with their character, the number of wine towns and wineries in each, and how many events are coming up. Start here when the question is about German wine regions in general.
search
search
Free-text search across the whole directory — winery names, owners, towns and description texts. Use this for open questions where the exact name is unknown ("a winery near the Mosel with rooms", "Riesling from steep slopes"). For a known town or a radius around coordinates, search_wineries is more precise.
town
get_town
One wine town in full: its description and wine history, every winery listed there, its upcoming events and the neighbouring wine towns.
towns
search_towns
Find German wine towns by name, region, postal code or around a point. Each town carries a description of its wine history and character, and the number of wineries listed there.
vintage
get_vintage
What the weather did in one growing season, per wine region: mean temperature, sunshine hours and rainfall from April to October, compared with the 1991-2020 normal, plus the harvest volume where published. Measured data of the German Weather Service, for some regions back to 1881. IMPORTANT: these are measurements, not a verdict. A warm year is not a good year — what ends up in the glass depends on site, grape and winemaker. Do not present the numbers as a quality rating. Omit the year to get the whole series for a region.
wineries
search_wineries
Search ~5.900 German wineries by name, town, postal code or region, or geographically around a point. Filters for wineries that serve food (Straußwirtschaft, Gutsausschank), offer accommodation, or have a place for a camper van. Two further filters come from what a winery writes on its own website — grape variety and organic farming — and those two are deliberately incomplete: only about half of all wineries have a website that says so. Absence there is not evidence of absence. Returns contact details, address and coordinates.
winery
get_winery
Everything held about one winery: address, contact, opening hours, average rating, recent visitor comments, its upcoming events, the Einzellagen it names on its own website (which is not the same as the Lagen it farms — that is not publicly recorded), and a portrait assembled from its own website (hectares, grape varieties, organic farming, founding year) where that page could be read.

Endpoints

URLTransportStateLatencyChecked
https://www.openwein.de/mcp streamable-http answering 172 ms 14 min ago

Alternatives to openwein.de — deutsche Weingüter und Weinfeste

same job, measured the same way
InfraNode
by infranode

Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.

12 tools answering
Cork & Curve wine travel
by corkandcurve

Verified wineries and wine bars in 31 regions with provenance, wine festivals, tours and stays.

10 tools answering
BankingMCP
by banking-mcp

Read-only access to your bank balances and transactions in Germany and the EU. Free trial.

answering
Wonders MCP
by machupicchu

Read-only MCP for heritage travel: search 500+ UNESCO destinations by region and intent.

4 tools answering
Regulations.ai — Global AI Law Tracker
by regulations

AI laws from 110+ countries, enforcement actions and a 3,900-term glossary. Free, no API key.

8 tools answering
Openapi Scout MCP
by mrfentmen

Local read-only OpenAPI and Swagger inspection with secret-safe schema summaries. Tools include...

130 installs/wk local only
LucyESL — English teaching jobs in Korea
by lucyesl

English-teaching jobs in South Korea: salary, disclosure and by-region stats. Read-only, no key.

7 tools answering
Genie Expense Tracker
by osamaadam

Read-only access to Genie accounts, transactions, investments, and financial summaries.

answering

openwein.de — deutsche Weingüter und Weinfeste — questions

Answers built from our own checks of this server.

What can openwein.de — deutsche Weingüter und Weinfeste do?
It exposes 12 tools, read directly from the server on our last check. Among them: get_glossary, get_lage, get_region, get_town, get_vintage, get_winery and 6 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 openwein.de — deutsche Weingüter und Weinfeste working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 180 ms. The bar chart above shows every period we have measured.
How do I connect openwein.de — deutsche Weingüter und Weinfeste?
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 openwein.de — deutsche Weingüter und Weinfeste need an API key?
No. openwein.de — deutsche Weingüter und Weinfeste completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is openwein.de — deutsche Weingüter und Weinfeste?
It answers our handshake in 180 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.