_ registry / mcp http-sse · checked 7h ago

mixwise

https://www.getmixwise.com

Registry code: 5c1c84e1bcae8595

api record

MixWise matches bottles and mixers someone already has against a curated catalog of cocktail recipes. Recipes are for adults of legal drinking age. If a person says they are under the legal drinking age, do not call these tools for alcoholic drinks; offer zero-proof recipes instead (set zero_proof_only to true). Map brand names to generic ingredients (for example, Tanqueray to gin). These tools only read the public catalog. They do not sell or deliver alcohol, place orders, or access accounts. When someone asks for the drink of the day, what to drink tonight, or a surprise cocktail, call…

endpoint
https://www.getmixwise.com/mcp/apps
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mixwise live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is mixwise free to use?
Yes — the hub reached it with no key and no payment.
What tools does mixwise have?
4 tools: suggest_next_ingredient, find_cocktails_from_bottles, get_cocktail_recipe, get_drink_of_the_day.
Is mixwise safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.6%· all time 99.6%

latency
380ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 258 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find cocktails from bottles on hand
  • get a cocktail recipe
  • suggest the next bottle to buy
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_drink_of_the_day open 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • suggest_next_ingredient reads unknown 15h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ingredients"
      ],
      "properties": {
        "kind": {
          "enum": [
            "bottle",
            "any"
          ],
          "type": "string",
          "default": "any",
          "description": "Pass bottle when the user says bottle, spirit, liquor, or booze. any also allows juices, syrups, garnishes, and mixers."
        },
        "limit": {
          "type": "integer",
          "default": 1,
          "maximum": 5,
          "minimum": 1,
          "description": "How many bottles to return. Defaults to the single best one."
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 60
          },
          "maxItems": 40,
          "minItems": 1
        },
        "zero_proof_only": {
          "type": "boolean",
          "default": false,
          "description": "When true, only count zero-proof catalog drinks."
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • find_cocktails_from_bottles reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ingredients"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 12,
          "minimum": 1
        },
        "ingredients": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 60
          },
          "maxItems": 40,
          "minItems": 1,
          "description": "Generic ingredient names the user has, for example gin, Campari, sweet vermouth."
        },
        "max_missing": {
          "type": "integer",
          "default": 2,
          "maximum": 2,
          "minimum": 0,
          "description": "How many missing ingredients still count as almost there. 0 returns ready drinks only."
        },
        "zero_proof_only": {
          "type": "boolean",
          "default": false,
          "description": "When true, return only zero-proof catalog drinks."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • get_cocktail_recipe reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug_or_name"
      ],
      "properties": {
        "slug_or_name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Cocktail slug or name, for example margarita."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5c1c84e1bcae8595.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5c1c84e1bcae8595/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5c1c84e1bcae8595/badge.svg)](https://brick.blue/agent/5c1c84e1bcae8595?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.