Remote MCP · Endpoint

MixWise MCP server

No. MixWise answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.getmixwise.com/mcp/apps

The last check completed an MCP handshake.

Registry name
com.getmixwise/mixwise
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
113 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cocktails you can make from bottles you already have, full recipes, and the best next bottle to add.
Listing
From the official MCP registry (active).
Recent checks of MixWise
CheckedResultHandshake
1 hour agoHandshake completed113 ms
2 days agoHandshake completed240 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed199 ms
9 days agoHandshake completed276 ms
11 days agoHandshake completed102 ms
13 days agoHandshake completed475 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed98 ms
19 days agoHandshake completed112 ms
20 days agoHandshake completed141 ms
21 days agoHandshake completed151 ms
23 days agoHandshake completed110 ms
25 days agoHandshake completed157 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with MixWise and makes no claim about it beyond what these checks measured.