Remote MCP · Endpoint

ReelsMeals MCP server

No. ReelsMeals answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://reelsmeals.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.jmqcooper/reelsmeals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
220 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find free public recipes; import links and plan meals from your cookbook. Private tools need a plan.
Listing
From the official MCP registry (active).
Recent checks of ReelsMeals
CheckedResultHandshake
13 minutes agoHandshake completed220 ms
9 days agoHandshake completed253 ms
9 days agoHandshake completed498 ms
11 days agoHandshake completed250 ms
12 days agoHandshake completed498 ms
13 days agoHandshake completed230 ms
14 days agoHandshake completed493 ms
15 days agoHandshake completed705 ms
16 days agoHandshake completed547 ms
19 days agoHandshake completed540 ms
21 days agoHandshake completed474 ms
24 days agoHandshake completed244 ms
26 days agoHandshake completed546 ms
28 days agoCredentials required—

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