Cocktail Glass
glass.cocktail/cocktail-glass · 1.0.0
Search 500 cocktail recipes, get full recipes, find drinks by ingredient, suggest random picks.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 30 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://cocktail.glass/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 7 tools.
- Protocol
- 2025-06-18
- Calls itself
- cocktail-glass 1.1.0
- Handshake time
- 147 ms
- HTTP status
- 200
The tools it lists (7, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_cocktailsSearch 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.
list_cocktailsList 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.
get_cocktail_recipeGet 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.
find_cocktails_by_ingredientFind 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
glass.cocktail/cocktail-glass, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 142 days ago. The registry entry · cocktail.glass