MCP QUEEN
glass.cocktail/cocktail-glass A
Search 500 cocktail recipes, get full recipes, find drinks by ingredient, suggest random picks.
Web & Searchv1.0.0streamable-httpcocktail.glass
Grade evidence — probed 2026-07-13 11:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 169ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo cocktail-glass@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 7 tools e.g. "search_cocktails"; 7/7 described, 7/7 fully-typed schemas, median description 543 chars |
| latency | 10 / 10 | initialize round-trip 169ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace glass.cocktail matches endpoint/repo |
Score 97/100 · latency 169ms · 7 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http cocktail-glass https://cocktail.glass/mcp
Generic MCP client config:
{ "mcpServers": { "cocktail-glass": { "type": "http", "url": "https://cocktail.glass/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/glass.cocktail/cocktail-glass · referral link https://mcpqueen.com/go/glass.cocktail/cocktail-glass (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/glass.cocktail/cocktail-glass)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 11:45 | A | 97 | 169ms |