Remote MCP · Endpoint

DietBox MCP server

No. DietBox answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_dietbox

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/dietbox-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
320 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Patient, prescription, anthropometry, scheduling, chat and food diary management for dietitians.
Listing
From the official MCP registry (active).
Recent checks of DietBox
CheckedResultHandshake
1 hour agoHandshake completed320 ms
2 days agoHandshake completed174 ms
4 days agoHandshake completed126 ms
5 days agoHandshake completed396 ms
7 days agoHandshake completed52 ms
8 days agoHandshake completed75 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed36 ms
14 days agoHandshake completed146 ms
15 days agoHandshake completed279 ms
17 days agoHandshake completed103 ms
18 days agoHandshake completed91 ms
19 days agoHandshake completed110 ms
20 days agoHandshake completed86 ms
20 days agoHandshake completed99 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed120 ms

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

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