Remote MCP · Endpoint

Recipe library MCP server

No. Recipe library answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://recipes.gitshow.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ofershap/recipe-library
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
396 ms
Tools exposed
2 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Read-only Hebrew AI-agent recipe library with search and full-text retrieval.
Listing
From the official MCP registry (active).
Recent checks of Recipe library
CheckedResultHandshake
7 hours agoHandshake completed396 ms
13 hours agoHandshake completed550 ms
2 days agoHandshake completed437 ms
4 days agoHandshake completed378 ms
7 days agoHandshake completed442 ms
9 days agoHandshake completed493 ms
11 days agoHandshake completed365 ms
14 days agoHandshake completed371 ms
16 days agoHandshake completed384 ms
18 days agoHandshake completed413 ms
20 days agoHandshake completed375 ms
21 days agoHandshake completed362 ms
23 days agoFailed - the request timed out—

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

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