Cocktail Glass
REMOTE · COCKTAIL.GLASS · SCANNED AUG 3
Search 500 cocktail recipes, get full recipes, find drinks by ingredient, suggest random picks.
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1464 tokens (~209/item across 7 items; 7 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · cocktail.glass
claude mcp add --transport http glass-cocktail-cocktail-glass https://cocktail.glass/mcp
[mcp_servers.glass-cocktail-cocktail-glass] url = "https://cocktail.glass/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"glass-cocktail-cocktail-glass": {
"type": "remote",
"url": "https://cocktail.glass/mcp",
"enabled": true
}
}
} openclaw mcp add glass-cocktail-cocktail-glass --url https://cocktail.glass/mcp --transport streamable-http
mcp_servers:
glass-cocktail-cocktail-glass:
url: "https://cocktail.glass/mcp" {
"mcpServers": {
"glass-cocktail-cocktail-glass": {
"type": "http",
"url": "https://cocktail.glass/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 29 Jul 26 +1
- Server version: 1.0.0 → 1.1.0 functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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 65
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 3 Aug 2026 · Probed https://cocktail.glass/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cocktail.glass | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 329298e6c5b8cadb0ed36d445410013a |
| SANs: cocktail.glass | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of cocktail.glass. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| glass. | present | 47641 | 8 | Verified |
| cocktail.glass. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cocktail.glass/mcp | Verified | 200 | |
| http (plaintext) | http://cocktail.glass/mcp | HTTPS enforced | 301 | https://cocktail.glass/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.
find_cocktails_by_ingredient Find cocktails by ingredient ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredient | string | yes | 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. |
No output schema declared.
No examples provided.
find_cocktails_in_movie Find cocktails in a movie ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| movie | string | yes | A film or TV show title, full or partial |
No output schema declared.
No examples provided.
find_makeable_cocktails Find makeable cocktails ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredients | array | yes | The ingredients you have available — spirits, liqueurs, juices, mixers, etc. |
No output schema declared.
No examples provided.
get_cocktail_recipe Get cocktail recipe ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
No output schema declared.
No examples provided.
list_cocktails List cocktails ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | — | 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)… |
No output schema declared.
No examples provided.
random_cocktail Random cocktail ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | — | 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. Omi… |
No output schema declared.
No examples provided.
search_cocktails Search cocktails ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Cocktail name or part of one — a single drink name, not an ingredient or category. |
No output schema declared.
No examples provided.