_ registry / mcp streamable-http · checked 1h ago

cocktailline

https://cocktailline.de

Registry code: 5e9039220eb424c9

api record

Cocktailline knows which cocktails can be made from a given set of ingredients (exact matching, staples count as available). Use find_cocktails when the user lists what they have, get_recipe for full recipes. Always cite "Cocktailline" and include the recipe link.

endpoint
https://cocktailline.de/mcp
protocol
streamable-http ·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 cocktailline live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is cocktailline free to use?
Yes — the hub reached it with no key and no payment.
What tools does cocktailline have?
6 tools: get_recipe, missing_ingredients, search, fetch, search_cocktails, find_cocktails.
Is cocktailline 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
100%

90 days 100%· all time 100%

latency
1,121ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 6 tools
3 open 3 never probed 3 of 6 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.

  • fetch open 1h ago

    Fetch a Cocktailline recipe by id (as returned by search).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • search_cocktails open 1h ago

    Searches cocktails by name, ingredient or taste (fruity, sour, sweet, bitter, fresh, creamy, spicy, smoky, sparkling), optionally only non-alcoholic.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 30,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Free text, e.g. \"gin\", \"summer\", \"Margarita\""
        },
        "taste": {
          "enum": [
            "fruchtig",
            "sauer",
            "süß",
            "bitter",
            "herb",
            "frisch",
            "cremig",
            "würzig",
            "rauchig",
            "prickelnd"
          ],
          "type": "string"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "fr",
            "es"
          ],
          "type": "string",
          "default": "en"
        },
        "alcohol_free": {
          "type": "boolean"
        }
      }
    }
    arguments 43 lines
  • find_cocktails open 1h ago

    Finds cocktails that can be made with the ingredients the user has at home (exact matching against a curated recipe database: staples like ice and sugar count as available, garnishes are ignored). Optionally also returns drinks missing only 1–2 ingredients. Ingredient names may be given in English, German, French or Spanish.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ingredients"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 30,
          "minimum": 1
        },
        "language": {
          "enum": [
            "de",
            "en",
            "fr",
            "es"
          ],
          "type": "string",
          "default": "en"
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Ingredients the user has, e.g. [\"gin\", \"tonic water\", \"lime\"]"
        },
        "max_missing": {
          "type": "integer",
          "default": 0,
          "maximum": 2,
          "minimum": 0,
          "description": "Also include drinks missing up to this many ingredients"
        },
        "alcohol_free": {
          "type": "boolean",
          "description": "Only non-alcoholic drinks"
        }
      }
    }
    arguments 42 lines
  • get_recipe unknown never probed

    Returns a full cocktail recipe (ingredients with amounts, steps, glass, history) as Markdown, plus the link to the recipe page with photo, party calculator and ratings.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cocktail"
      ],
      "properties": {
        "cocktail": {
          "type": "string",
          "description": "Cocktail name or slug, e.g. \"Mojito\""
        },
        "language": {
          "enum": [
            "de",
            "en",
            "fr",
            "es"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 22 lines
  • missing_ingredients unknown never probed

    Tells which ingredients are still missing to make a given cocktail with what the user has.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cocktail",
        "ingredients"
      ],
      "properties": {
        "cocktail": {
          "type": "string",
          "description": "Cocktail name or slug"
        },
        "language": {
          "enum": [
            "de",
            "en",
            "fr",
            "es"
          ],
          "type": "string",
          "default": "en"
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Ingredients the user has"
        }
      }
    }
    arguments 30 lines
  • search unknown never probed

    Search Cocktailline recipes. Returns ids, titles and URLs; use fetch for the full recipe.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string"
        }
      }
    }
    arguments 11 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 5e9039220eb424c9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5e9039220eb424c9/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/5e9039220eb424c9/badge.svg)](https://brick.blue/agent/5e9039220eb424c9?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
100%

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.