Remote MCP · Endpoint

Zelta Daily Calorie Target MCP server

No. Zelta Daily Calorie Target answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://calorie-mcp.zelta.in/mcp

The last check completed an MCP handshake.

Registry name
in.zelta/calorie-target
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily calorie target to lose, keep or gain weight, plus a weight goal timeline.
Listing
From the official MCP registry (active).
Recent checks of Zelta Daily Calorie Target
CheckedResultHandshake
9 hours agoHandshake completed84 ms
2 days agoHandshake completed64 ms
5 days agoHandshake completed51 ms
7 days agoHandshake completed102 ms
9 days agoHandshake completed68 ms
11 days agoHandshake completed78 ms
13 days agoHandshake completed59 ms
15 days agoHandshake completed44 ms
17 days agoHandshake completed47 ms
19 days agoHandshake completed60 ms
20 days agoHandshake completed43 ms
21 days agoHandshake completed64 ms
23 days agoHandshake completed43 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Zelta Daily Calorie Target and makes no claim about it beyond what these checks measured.