Remote MCP · Endpoint

Mise Recipes MCP server

No. Mise Recipes answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mise.how/mcp

The last check completed an MCP handshake.

Registry name
how.mise/mise
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
212 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Ad-free recipes with amounts in every step: search, scale, plan meals, build shopping lists.
Listing
From the official MCP registry (deprecated).
Recent checks of Mise Recipes
CheckedResultHandshake
1 hour agoHandshake completed212 ms
1 day agoHandshake completed409 ms
2 days agoHandshake completed1.28 s
3 days agoHandshake completed477 ms
4 days agoHandshake completed455 ms
5 days agoHandshake completed313 ms
6 days agoHandshake completed273 ms
9 days agoHandshake completed230 ms
11 days agoHandshake completed477 ms
14 days agoHandshake completed299 ms
16 days agoHandshake completed1.18 s
18 days agoHandshake completed196 ms
20 days agoHandshake completed348 ms
22 days agoCredentials required—
24 days agoCredentials required—

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

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 Mise Recipes and makes no claim about it beyond what these checks measured.