_ registry / mcp http-sse · checked 18m ago

dreissigacker-wines

https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io

Registry code: dcace9e9a8cf7eef

api record

Wine recommendations, food pairings & B2B contact for Weingut Dreissigacker, Rheinhessen.

from a public catalogue that lists it, not from the operator

endpoint
https://dreissigacker-mcp.jollystone-6dcd657d.westeurope.azurecontainerapps.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dreissigacker-wines live?
Yes — it answered the hub's last check (checked 18m ago). It answered 100% of checks over the last 30 days.
Is dreissigacker-wines free to use?
Yes — the hub reached it with no key and no payment.
What tools does dreissigacker-wines have?
3 tools: dreissigacker_food_pairing, dreissigacker_b2b_contact, dreissigacker_recommend_wine.
Is dreissigacker-wines safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.7%· all time 99.7%

latency
73ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 388 checks · signed record
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
  • unknown → live
_ what it is for
topic
lifestyle & home food & drink
used for
  • recommend wine for a dish
  • recommend wines by style and budget
  • get winery b2b contact details
takes → gives
text → text, data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • dreissigacker_b2b_contact reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "market": {
      "type": "string",
      "description": "Target market or country, e.g. 'USA', 'UK', 'Japan', 'Deutschland'"
    },
    "interest": {
      "type": "string",
      "description": "Specific interest, e.g. 'wine list curation', 'import partnership', 'event wines'"
    }
  }
}
    arguments 14 lines
  • dreissigacker_recommend_wine reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "food": {
      "type": "string",
      "description": "Food to pair with, e.g. 'grilled fish', 'Vietnamese spring rolls'"
    },
    "style": {
      "type": "string",
      "description": "Wine style preference, e.g. 'fresh Riesling', 'full-bodied white', 'biodynamic'"
    },
    "budget": {
      "type": "string",
      "description": "Budget per bottle, e.g. '30€', '50', 'under 25 EUR'"
    },
    "language": {
      "enum": [
        "de",
        "en"
      ],
      "type": "string",
      "description": "Response language: 'de' for German, 'en' for English. Auto-detected if omitted."
    },
    "occasion": {
      "type": "string",
      "description": "Occasion, e.g. 'fine dining', 'casual dinner', 'wine list for Michelin restaurant'"
    }
  }
}
    arguments 30 lines
  • dreissigacker_food_pairing reads unknown 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "dish"
  ],
  "properties": {
    "dish": {
      "type": "string",
      "description": "The dish to pair wine with, e.g. 'Vietnamese spring rolls', 'Trüffel-Risotto', 'grilled lobster'"
    },
    "language": {
      "enum": [
        "de",
        "en"
      ],
      "type": "string",
      "description": "Response language: 'de' for German, 'en' for English. Auto-detected if omitted."
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id dcace9e9a8cf7eef.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dcace9e9a8cf7eef/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/dcace9e9a8cf7eef/badge.svg)](https://brick.blue/agent/dcace9e9a8cf7eef?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on azurecontainerapps.io 5 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.