Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MixWise

REMOTE · WWW.GETMIXWISE.COM

Cocktails you can make from bottles you already have, full recipes, and the best next bottle to add.

+2 this week 89 Trust /100

Last scanned (2 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 6 Nov 2026.

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 621 tokens (~124/item across 5 items; 4 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 6 Nov 2026 · Probed https://www.getmixwise.com/mcp/apps

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.getmixwise.com CN=YR2,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 RSA 2048 SHA256-RSA 62c08006c14334f7ceeefc94c372cb3cef3
SANs: www.getmixwise.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.getmixwise.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
getmixwise.com. No DS 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.getmixwise.com/mcp/apps Verified 200
http (plaintext) http://www.getmixwise.com/mcp/apps HTTPS enforced 308 https://www.getmixwise.com/mcp/apps
MCP tools · 4 exposed · ~460 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_cocktails_from_bottles ~137

Use this when the user lists bottles or ingredients they have and wants catalog cocktails they can make now, or that are one or two ingredients away. Returns only MixWise catalog recipes. Set zero_proof_only when the user wants drinks without alcohol.

NameTypeReqDescription
ingredientsarrayyesGeneric ingredient names the user has, for example gin, Campari, sweet vermouth.
limitinteger––
max_missinginteger–How many missing ingredients still count as almost there. 0 returns ready drinks only.
zero_proof_onlyboolean–When true, return only zero-proof catalog drinks.
NameTypeReqDescription
almost_therearrayyes–
countsobjectyes–
linksobjectyes–
readyarrayyes–
recognizedarrayyes–
unrecognizedarrayyes–

No examples provided.

get_cocktail_recipe ~63

Use this when the user asks how to make a specific cocktail by name, or picks one from MixWise results. Returns the full catalog recipe, including measures and steps.

NameTypeReqDescription
slug_or_namestringyesCocktail slug or name, for example margarita.
NameTypeReqDescription
difficulty–––
foundbooleanyes–
garnish–––
glassware–––
image_url–––
ingredientsarray––
instructions_stepsarray––
is_zero_proofboolean––
linksobjectyes–
namestring––
responsible_notestring––
short_description–––
slugstring––
suggestionsarray––
technique–––

No examples provided.

get_drink_of_the_day ~57

Use this when the user asks for the drink of the day, what to drink tonight, or a surprise cocktail. Returns the same MixWise drink the website shows for the current Pacific calendar day, with a one-line description.

Input schema present but exposes no named parameters.

NameTypeReqDescription
can_makeboolean––
date_keystringyes–
displaystringyes–
foundbooleanyes–
image_url–––
ingredientsarray––
linksobjectyes–
missingarray––
namestring––
short_description–––
slugstring––
whystring––

No examples provided.

suggest_next_ingredient ~203

Use this when the user asks which single ingredient or bottle to add to unlock the most new cocktails from what they already have. Returns the one catalog bottle that unlocks the most drinks. Set zero_proof_only when the user wants drinks without alcohol. It does not sell anything or link to a store. Pass kind bottle when the user says bottle, spirit, liquor, or booze; otherwise leave kind as any. A bottle is a spirit, liqueur, vermouth, amaro, wine, or bitters, not a juice, syrup, or garnish.

NameTypeReqDescription
ingredientsarrayyes–
kindstring–Pass bottle when the user says bottle, spirit, liquor, or booze. any also allows juices, syrups, garnishes, and mixers.
limitinteger–How many bottles to return. Defaults to the single best one.
zero_proof_onlyboolean–When true, only count zero-proof catalog drinks.
NameTypeReqDescription
displaystringyes–
kindstringyes–
linksobjectyes–
recognizedarrayyes–
suggestionsarrayyes–
unrecognizedarrayyes–

No examples provided.

Install

How do I install the MixWise MCP server?

MixWise is a hosted endpoint at https://www.getmixwise.com/mcp/apps, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.getmixwise.com

# add to Claude Code
claude mcp add --transport http com-getmixwise-mixwise 'https://www.getmixwise.com/mcp/apps'
Common questions

What is the MixWise MCP server?

MixWise is an MCP server listed in the public MCP registry as com.getmixwise/mixwise. Cocktails you can make from bottles you already have, full recipes, and the best next bottle to add. This page covers its hosted endpoint (https://www.getmixwise.com/mcp/apps).

Is the MixWise MCP server safe to use?

MixWise scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MixWise MCP server expose?

MixWise exposes 4 tools: find_cocktails_from_bottles, get_cocktail_recipe, suggest_next_ingredient, get_drink_of_the_day. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

Does the MixWise MCP server require authentication?

No. We connected to MixWise without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MixWise MCP server still maintained?

MixWise is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MixWise MCP server?

VerifyMCP ran 14 checks on MixWise, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.