A-

cocktail.glass

Item: cocktail.glass
Rating: 91
Author: wmcp.sh

https://cocktail.glass/mcp

91/100 · MCP Trust Grade · checked 4h ago · MCP 2025-06-18

⚠ Rug-pull watch: this server's tool surface has changed 1× since baseline — last 5h ago. Continuously watched by wmcp.sh for drift & rug-pulls.

What it offers — 6 tools · Developer Tools

search_cocktails

Search the cocktail catalogue by name (substring, case- and diacritic-insensitive, so "carre" matches "Carré"). Returns up to 25 summary results — nam

get_cocktail_recipe

Get the full recipe for one cocktail by name: ingredients with measures and units, preparation steps, garnish, glassware, family, page URL, and any fi

find_cocktails_by_ingredient

Find every cocktail in the catalogue that uses one specific ingredient. Matching is a case- and diacritic-insensitive substring match against each coc

find_cocktails_in_movie

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 desc

find_makeable_cocktails

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

random_cocktail

Suggest one cocktail picked uniformly at random from the catalogue (or from one family if "family" is given) and return its full recipe — ingredients

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 6 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

6 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%92

single-probe latency 128ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%80

100% of tools have typed inputSchema
0/6 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade cocktail.glass on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — cocktail.glass grade A-

Share on X Open card image

https://wmcp.sh/mcp/grade/cocktail.glass

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade A-](https://wmcp.sh/mcp/grade/cocktail.glass/badge.svg)](https://wmcp.sh/mcp/grade/cocktail.glass)

HTML

<a href="https://wmcp.sh/mcp/grade/cocktail.glass"><img src="https://wmcp.sh/mcp/grade/cocktail.glass/badge.svg" alt="MCP Trust Grade A- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.