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.

openwein.de — deutsche Weingüter und Weinfeste

REMOTE · WWW.OPENWEIN.DE · SCANNED SEP 22

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

Available components

+4 this week 80 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1989 tokens (~165/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the openwein.de — deutsche Weingüter und Weinfeste MCP server?

openwein.de — deutsche Weingüter und Weinfeste is a hosted endpoint at https://www.openwein.de/mcp, 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 · www.openwein.de

# add to Claude Code
claude mcp add --transport http de-openwein-mcp 'https://www.openwein.de/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "de-openwein-mcp": {
      "url": "https://www.openwein.de/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "de-openwein-mcp": {
      "type": "http",
      "url": "https://www.openwein.de/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.de-openwein-mcp]
url = "https://www.openwein.de/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-openwein-mcp": {
      "type": "remote",
      "url": "https://www.openwein.de/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add de-openwein-mcp --url 'https://www.openwein.de/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  de-openwein-mcp:
    url: "https://www.openwein.de/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "de-openwein-mcp": {
      "Transport": "http",
      "Url": "https://www.openwein.de/mcp"
    }
  }
}
# add to Vellum
assistant mcp add de-openwein-mcp -t streamable-http -u 'https://www.openwein.de/mcp'
// mcp.json
{
  "mcpServers": {
    "de-openwein-mcp": {
      "type": "http",
      "url": "https://www.openwein.de/mcp"
    }
  }
}

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

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.

  • 22 Sept 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.

  • 20 Sept 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.

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +3
    • HSTS header: fail → pass security
  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 22 Sept 2026 · Probed https://www.openwein.de/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=openwein.de CN=YE2,O=Let's Encrypt,C=US 29 Aug 2026 27 Nov 2026 ECDSA 256 ECDSA-SHA384 5779ffbb71994ff6fba7d2d6168f98097f6
SANs: openwein.de, www.openwein.de
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 bogus

Validation of www.openwein.de. Bogus

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
de. present 26755 8 Verified
openwein.de. present 4663 13 Verified
www.openwein.de. Bogus address RRset signature failed verification
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
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.openwein.de/mcp Verified 200
http (plaintext) http://www.openwein.de/mcp HTTPS enforced 301 https://www.openwein.de/mcp
MCP tools · 12 exposed · ~1,897 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
get_glossary ~140

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.

NameTypeReqDescription
categorystringRestrict the listing to one category.
termstringTerm, alias or a synonym, e.g. "Besen".

No output schema declared.

No examples provided.

get_lage ~115

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.

NameTypeReqDescription
lagestringLage alias from search_lagen.
regionstringRegion alias.
urlstringAlternatively its openwein.de URL or path.

No output schema declared.

No examples provided.

get_region ~69

Full description of one wine region: its history, grape varieties and terroir, plus its wine towns and upcoming events.

NameTypeReqDescription
regionstringyesRegion alias, e.g. "rheinhessen", "mosel-saar-ruwer", "ahr". Use list_regions to see all.

No output schema declared.

No examples provided.

get_town ~74

One wine town in full: its description and wine history, every winery listed there, its upcoming events and the neighbouring wine towns.

NameTypeReqDescription
idintegerAlternatively the town id.
regionstringRegion alias.
townstringTown alias, e.g. "mainz-ebersheim".

No output schema declared.

No examples provided.

get_vintage ~166

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.

NameTypeReqDescription
fromintegerEarliest year when returning a series.
regionstringRegion alias.
yearintegerVintage year. Omitted: the whole series.

No output schema declared.

No examples provided.

get_winery ~141

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.

NameTypeReqDescription
idintegerWinery id from search_wineries.
urlstringAlternatively its openwein.de URL or path, e.g. "/rheinhessen/mainz-ebersheim/weingut-eva-vollmer".

No output schema declared.

No examples provided.

list_events ~219

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.

NameTypeReqDescription
fromstringEarliest date, YYYY-MM-DD. Defaults to today.
latnumberLatitude for a radius search.
limitintegerMax results, 1-100. Default 40.
lngnumberLongitude for a radius search.
radius_kmnumberRadius in km around lat/lng. Default 25.
regionstringRegion alias to restrict to.
tostringLatest date, YYYY-MM-DD. Defaults to one year out.
townstringTown name or alias to restrict to.

No output schema declared.

No examples provided.

list_regions ~56

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~160

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.

NameTypeReqDescription
has_caravanbooleanOnly wineries with a camper van pitch.
has_lodgingbooleanOnly wineries offering accommodation.
limitintegerMax results, 1-50. Default 20.
querystringyesWhat to look for, in German or English.
regionstringRegion alias to restrict to.
serves_foodbooleanOnly wineries that serve food.

No output schema declared.

No examples provided.

search_lagen ~243

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.

NameTypeReqDescription
grosslagestringRestrict to one Großlage.
limitintegerMax results, 1-100. Default 25.
querystringFree text matched against the Lage name.
regionstringRegion alias to restrict to.
townstringTown name or alias, e.g. "Kallstadt".

No output schema declared.

No examples provided.

search_towns ~133

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.

NameTypeReqDescription
latnumber
limitintegerMax results, 1-50. Default 20.
lngnumber
plzstringGerman postal code.
querystringTown name, full or partial.
radius_kmnumberRadius in km around lat/lng. Default 20.
regionstringRegion alias to restrict to.

No output schema declared.

No examples provided.

search_wineries ~381

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.

NameTypeReqDescription
grape_varietystringOnly wineries that NAME this grape variety on their own website, e.g. "Riesling". This is not a complete list of who grows it: a winery without a website, or one that does not list its varieties, is…
has_caravanbooleanOnly wineries with a camper van pitch.
has_lodgingbooleanOnly wineries offering accommodation.
latnumberLatitude for a radius search.
limitintegerMax results, 1-50. Default 20.
lngnumberLongitude for a radius search.
organicbooleanOnly wineries that STATE organic farming on their own website. Not a certification check — same caveat as grape_variety.
plzstringGerman postal code.
querystringFree text matched against winery name, owner and second name.
radius_kmnumberRadius in km around lat/lng. Default 10.
regionstringRegion alias to restrict to.
serves_foodbooleanOnly wineries with a Straußwirtschaft, Gutsausschank or restaurant.
townstringTown name or alias, e.g. "Nierstein".

No output schema declared.

No examples provided.

Common questions

What is the openwein.de — deutsche Weingüter und Weinfeste MCP server?

openwein.de — deutsche Weingüter und Weinfeste is an MCP server listed in the public MCP registry as de.openwein/mcp. German wineries, wine towns and wine festivals: 5.900 entries in 13 regions. Read-only, no key. This page covers its hosted endpoint (https://www.openwein.de/mcp).

Is the openwein.de — deutsche Weingüter und Weinfeste MCP server safe to use?

openwein.de — deutsche Weingüter und Weinfeste scores 80 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 openwein.de — deutsche Weingüter und Weinfeste MCP server expose?

openwein.de — deutsche Weingüter und Weinfeste exposes 12 tools: list_regions, get_region, search_wineries, get_winery, list_events, and 7 more. Their descriptions and schemas cost roughly 1,897 tokens of context every time the server is loaded.

Does the openwein.de — deutsche Weingüter und Weinfeste MCP server require authentication?

No. We connected to openwein.de — deutsche Weingüter und Weinfeste without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the openwein.de — deutsche Weingüter und Weinfeste MCP server still maintained?

openwein.de — deutsche Weingüter und Weinfeste is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.