Remote MCP · Endpoint

Dieta.ai MCP server

No. Dieta.ai answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_dieta

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/dieta-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
45 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Nutrition tracking by Dieta.ai. Read your food log with macros (calories, protein, carbs, fat, fiber
Listing
From the official MCP registry (active).
Recent checks of Dieta.ai
CheckedResultHandshake
1 day agoHandshake completed45 ms
3 days agoHandshake completed58 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed1.45 s
9 days agoHandshake completed45 ms
12 days agoHandshake completed90 ms
13 days agoHandshake completed75 ms
15 days agoHandshake completed268 ms
16 days agoHandshake completed641 ms
18 days agoHandshake completed103 ms
19 days agoHandshake completed87 ms
20 days agoHandshake completed108 ms
20 days agoHandshake completed101 ms
21 days agoHandshake completed78 ms
22 days agoHandshake completed67 ms

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

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