Remote MCP · Endpoint

Ask Garçon MCP server

No. Ask Garçon answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://mcp.fixmeadrinkapp.com/mcp

The last check completed an MCP handshake.

Registry name
com.fixmeadrinkapp/ask-garcon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
276 ms
Tools exposed
4 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Cocktails from the bottles you own: recipes, bar terms, similar drinks, low and zero-proof picks.
Listing
From the official MCP registry (active).
Recent checks of Ask Garçon
CheckedResultHandshake
53 minutes agoHandshake completed276 ms
3 days agoHandshake completed136 ms
12 days agoHandshake completed258 ms
13 days agoHandshake completed154 ms

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

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 Ask Garçon and makes no claim about it beyond what these checks measured.