Remote MCP · Endpoint

Plate Pal MCP server

No. Plate Pal answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://goodturn-mcp.pages.dev/platepal/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/platepal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
36 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Calories and nutrition for any food, chain meal or barcode, and meal ideas for a goal and diet.
Listing
From the official MCP registry (active).
Recent checks of Plate Pal
CheckedResultHandshake
33 minutes agoHandshake completed36 ms
9 days agoHandshake completed66 ms
10 days agoHandshake completed300 ms
11 days agoHandshake completed31 ms
12 days agoHandshake completed28 ms
14 days agoHandshake completed25 ms
14 days agoHandshake completed30 ms
15 days agoHandshake completed45 ms
17 days agoHandshake completed26 ms
19 days agoHandshake completed29 ms
22 days agoHandshake completed16 ms
24 days agoHandshake completed21 ms
26 days agoHandshake completed41 ms
28 days agoHandshake completed54 ms

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

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