Dreissigacker Wine Concierge
REMOTE · DREISSIGACKER-MCP.JOLLYSTONE-6DCD657D.WESTEUROPE.AZURECONTAINERAPPS.IO · SCANNED SEP 21
Wine recommendations, food pairings & B2B contact for Weingut Dreissigacker, Rheinhessen.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 431 tokens (~143/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Dreissigacker Wine Concierge MCP server?
Dreissigacker Wine Concierge is a hosted endpoint at https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/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 · dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io
claude mcp add --transport http paulwenner-dreissigacker-wine-concierge 'https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp'
{
"mcpServers": {
"paulwenner-dreissigacker-wine-concierge": {
"url": "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp"
}
}
} {
"servers": {
"paulwenner-dreissigacker-wine-concierge": {
"type": "http",
"url": "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp"
}
}
} [mcp_servers.paulwenner-dreissigacker-wine-concierge] url = "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paulwenner-dreissigacker-wine-concierge": {
"type": "remote",
"url": "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp",
"enabled": true
}
}
} openclaw mcp add paulwenner-dreissigacker-wine-concierge --url 'https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp' --transport streamable-http
mcp_servers:
paulwenner-dreissigacker-wine-concierge:
url: "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp" {
"McpServers": {
"paulwenner-dreissigacker-wine-concierge": {
"Transport": "http",
"Url": "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp"
}
}
} assistant mcp add paulwenner-dreissigacker-wine-concierge -t streamable-http -u 'https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp'
{
"mcpServers": {
"paulwenner-dreissigacker-wine-concierge": {
"type": "http",
"url": "https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 21 Sept 2026 · Probed https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jollystone-6dcd657d.westeurope.azurecontainerapps.io,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US | 27 Aug 2026 | 23 Feb 2027 | RSA 2048 | SHA384-RSA | 4300da4df8cfeaaef2c5f9f5b4000000da4df8 |
| SANs: *.jollystone-6dcd657d.westeurope.azurecontainerapps.io, *.scm.jollystone-6dcd657d.westeurope.azurecontainerapps.io, *.internal.jollystone-6dcd657d.westeurope.azurecontainerapps.io, *.ext.jollystone-6dcd657d.westeurope.azurecontainerapps.io, jollystone-6dcd657d.westeurope.azurecontainerapps.io | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000b13e5667d4a9b558000000000000b |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| azurecontainerapps.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp | Verified | 200 | |
| http (plaintext) | http://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp | HTTPS enforced | 301 | https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp |
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 →
dreissigacker_b2b_contact ~114
Get B2B contact information for Weingut Dreissigacker. Returns structured contact data, importer info, and next steps for trade inquiries. B2B-Kontaktdaten für Gastronomie, Handel und Importeure.
| Name | Type | Req | Description |
|---|---|---|---|
| interest | string | – | Specific interest, e.g. 'wine list curation', 'import partnership', 'event wines' |
| market | string | – | Target market or country, e.g. 'USA', 'UK', 'Japan', 'Deutschland' |
No output schema declared.
No examples provided.
dreissigacker_food_pairing ~115
Find the perfect Dreissigacker wine for a specific dish. Returns a wine recommendation with reasoning why it pairs well. Findet den perfekten Dreissigacker-Wein zu einem bestimmten Gericht.
| Name | Type | Req | Description |
|---|---|---|---|
| dish | string | yes | The dish to pair wine with, e.g. 'Vietnamese spring rolls', 'Trüffel-Risotto', 'grilled lobster' |
| language | string | – | Response language: 'de' for German, 'en' for English. Auto-detected if omitted. |
No output schema declared.
No examples provided.
dreissigacker_recommend_wine ~202
Recommend Dreissigacker wines based on style, food pairing, occasion, or budget. Returns matching wines from the portfolio across 4 tiers (Entry to Grand Cru). Empfiehlt Dreissigacker-Weine basierend auf Stil, Speise, Anlass oder Budget.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Budget per bottle, e.g. '30€', '50', 'under 25 EUR' |
| food | string | – | Food to pair with, e.g. 'grilled fish', 'Vietnamese spring rolls' |
| language | string | – | Response language: 'de' for German, 'en' for English. Auto-detected if omitted. |
| occasion | string | – | Occasion, e.g. 'fine dining', 'casual dinner', 'wine list for Michelin restaurant' |
| style | string | – | Wine style preference, e.g. 'fresh Riesling', 'full-bodied white', 'biodynamic' |
No output schema declared.
No examples provided.
What is the Dreissigacker Wine Concierge MCP server?
Dreissigacker Wine Concierge is an MCP server listed in the public MCP registry as io.github.paulwenner/dreissigacker-wine-concierge. Wine recommendations, food pairings & B2B contact for Weingut Dreissigacker, Rheinhessen. This page covers its hosted endpoint (https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp).
Is the Dreissigacker Wine Concierge MCP server safe to use?
Dreissigacker Wine Concierge scores 87 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 Dreissigacker Wine Concierge MCP server expose?
Dreissigacker Wine Concierge exposes 3 tools: dreissigacker_recommend_wine, dreissigacker_food_pairing, dreissigacker_b2b_contact. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Does the Dreissigacker Wine Concierge MCP server require authentication?
No. We connected to Dreissigacker Wine Concierge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dreissigacker Wine Concierge MCP server still maintained?
Dreissigacker Wine Concierge is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.