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

cocktail-glass

https://cocktail.glass

Registry code: 4f1db957ba50db3b

api record

Tools for cocktail.glass — a catalogue of 500 cocktail recipes. Use search_cocktails to find drinks by name, list_cocktails to browse the whole catalogue (or one family), get_cocktail_recipe for a full recipe, find_cocktails_by_ingredient to search by a single ingredient, find_cocktails_in_movie to find drinks featured in a film or TV show, find_makeable_cocktails to find drinks you can make from a set of ingredients you have, and random_cocktail for a suggestion. The cocktails_from_my_bar prompt turns a photo of a home bar into a list of makeable cocktails.

endpoint
https://cocktail.glass/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 cocktail-glass live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is cocktail-glass free to use?
Yes — the hub reached it with no key and no payment.
What tools does cocktail-glass have?
7 tools: random_cocktail, find_makeable_cocktails, get_cocktail_recipe, search_cocktails, find_cocktails_in_movie, list_cocktails, find_cocktails_by_ingredient.
Is cocktail-glass 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.1%

90 days 98.8%· all time 98.8%

latency
126ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 591 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find a cocktail recipe
  • find cocktails by ingredient
  • find cocktails i can make
  • find cocktails in a movie
  • suggest a random cocktail
takes → gives
text → data
tools
7 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 7 tools
7 open 7 of 7 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.

  • random_cocktail reads open 6h ago

    Suggest one cocktail picked uniformly at random from the catalogue (or from one family if "family" is given) and return its full recipe — ingredients with measures, preparation steps, garnish, glassware, page URL, and any film or TV appearances. Each call returns an independent draw, so repeated calls give different drinks. The "family" filter matches the family name exactly (case- and diacritic-insensitive); if no cocktail matches that family the call silently falls back to the full catalogue rather than erroring. Use this only when the user wants a suggestion or inspiration with no specific drink in mind. For a named cocktail use get_cocktail_recipe; for "anything with gin" use find_cocktails_by_ingredient; for "what can I make from what I have" use find_makeable_cocktails.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "family": {
          "type": "string",
          "examples": [
            "Tiki",
            "Sour"
          ],
          "description": "Optional drink family — one of: Spirit-Forward, Sour, Highball, Fizz & Collins, Spritz, Champagne Cocktail, Tiki, Punch, Flip & Nog, Hot Drink, Shot. Other values fall back to the full catalogue. Omit for an unrestricted random pick."
        }
      }
    }
    arguments 13 lines
  • find_makeable_cocktails reads open 1h ago

    Given the ingredients you have on hand, find every cocktail you can make completely — one where you already have all of its ingredients. Garnishes are treated as optional and plain water is assumed available; soda and tonic water are not. Matching is word-based, not substring: "gin" matches "London dry gin" but not "ginger beer", and generic terms do not match product-class extras ("gin" will not cover "sloe gin" or "orange bitters"). Returns two lists: "makeable" (drinks you can make now, up to 60) and "almostMakeable" (drinks exactly one ingredient short, up to 25, each naming the missing ingredient). Drinks needing two or more extra ingredients are omitted entirely. Both lists are ordered simplest first — fewest distinct ingredients in the full recipe, then alphabetical by name. Use this for multi-ingredient "what can I make?" questions; for a single ingredient use find_cocktails_by_ingredient.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ingredients"
      ],
      "properties": {
        "ingredients": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 1
          },
          "examples": [
            [
              "gin",
              "sweet vermouth",
              "Campari",
              "lime"
            ]
          ],
          "minItems": 1,
          "description": "The ingredients you have available — spirits, liqueurs, juices, mixers, etc."
        }
      }
    }
    arguments 25 lines
  • get_cocktail_recipe reads open 1h ago

    Get the full recipe for one cocktail by name: ingredients with measures and units, preparation steps, garnish, glassware, family, page URL, and any film or TV appearances. Matching is case- and diacritic-insensitive: it tries an exact name match first, then falls back to the first substring match. Returns one cocktail object, or an { error } if nothing matches. Use this when you have a specific drink name; if the name is ambiguous or you want a list, call search_cocktails first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "examples": [
            "Negroni",
            "Margarita"
          ],
          "minLength": 1,
          "description": "The cocktail name. Exact is best; partial names work but resolve to the first substring match, so prefer search_cocktails when the name is uncertain."
        }
      }
    }
    arguments 17 lines
  • search_cocktails reads open 15h ago

    Search the cocktail catalogue by name (substring, case- and diacritic-insensitive, so "carre" matches "Carré"). Returns up to 25 summary results — name, page URL, family, glassware — ranked exact match first, then prefix, then suffix, then any substring. Use this when the user names a drink (even fuzzily) and you want to confirm it exists or disambiguate similar names; once you have a single name, call get_cocktail_recipe for the full recipe. For ingredient-based discovery use find_cocktails_by_ingredient instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "examples": [
            "Negroni",
            "margarita",
            "carre"
          ],
          "minLength": 1,
          "description": "Cocktail name or part of one — a single drink name, not an ingredient or category."
        }
      }
    }
    arguments 18 lines
  • find_cocktails_in_movie reads open 1h ago

    Find every cocktail that appears in a given film or TV show. Case- and diacritic-insensitive substring match against both the title and the scene description, so a character or actor works too — e.g. "Casablanca", "Bond", "Hemingway". Each result names the cocktail, the film/show title, the year, and the scene. Returns up to 60 appearances ordered oldest year first, then by cocktail name. A single cocktail can appear multiple times if it shows up in multiple scenes that match. Use this only for on-screen appearances; for a drink by name use search_cocktails, and to browse the whole catalogue use list_cocktails.

    mcp-tool

    {
      "type": "object",
      "required": [
        "movie"
      ],
      "properties": {
        "movie": {
          "type": "string",
          "examples": [
            "Casablanca",
            "Bond",
            "Hemingway"
          ],
          "minLength": 1,
          "description": "A film or TV show title, full or partial"
        }
      }
    }
    arguments 18 lines
  • list_cocktails reads open 6h ago

    List the whole catalogue: every cocktail as a summary (name, page URL, family, glassware), in catalogue order, optionally restricted to one drink family. Unlike search_cocktails and find_cocktails_by_ingredient — which cap their results and need a query — this takes no query and returns every matching cocktail, so use it to browse or enumerate the full set of 500 drinks (or a whole family) when there is nothing specific to search for. For one named drink use get_cocktail_recipe; to discover by ingredient use find_cocktails_by_ingredient.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "family": {
          "type": "string",
          "examples": [
            "Sour",
            "Tiki"
          ],
          "description": "Optional drink family — one of: Spirit-Forward, Sour, Highball, Fizz & Collins, Spritz, Champagne Cocktail, Tiki, Punch, Flip & Nog, Hot Drink, Shot. Matched exactly (case- and diacritic-insensitive); an unknown family returns an empty list. Omit to list the entire catalogue."
        }
      }
    }
    arguments 13 lines
  • find_cocktails_by_ingredient reads open 6h ago

    Find every cocktail in the catalogue that uses one specific ingredient. Matching is a case- and diacritic-insensitive substring match against each cocktail's ingredient names, so "gin" will also match "sloe gin" and "ginger beer" — use a more specific term if that matters. Returns up to 60 summary results (name, URL, family, glassware) in catalogue order. Takes one ingredient only; for "what can I make from X, Y, and Z?" use find_makeable_cocktails instead, which handles multiple ingredients and reports near-misses.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ingredient"
      ],
      "properties": {
        "ingredient": {
          "type": "string",
          "examples": [
            "gin",
            "lime juice",
            "Campari"
          ],
          "minLength": 1,
          "description": "A single ingredient term. One value only; passing a comma-separated list is treated as one literal string and will rarely match. Use find_makeable_cocktails for multi-ingredient queries."
        }
      }
    }
    arguments 18 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 4f1db957ba50db3b.

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