Remote MCP · Endpoint

Zelta Protein Per Day MCP server

No. Zelta Protein Per Day answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
in.zelta/protein-target
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Daily protein need by weight and goal, with a sample Indian food plan to hit it.
Listing
From the official MCP registry (active).
Recent checks of Zelta Protein Per Day
CheckedResultHandshake
46 minutes agoHandshake completed52 ms
3 days agoHandshake completed60 ms
13 days agoHandshake completed249 ms
13 days agoHandshake completed72 ms
15 days agoHandshake completed70 ms
16 days agoHandshake completed58 ms
17 days agoHandshake completed60 ms
18 days agoHandshake completed70 ms
18 days agoHandshake completed62 ms
20 days agoHandshake completed102 ms
22 days agoHandshake completed113 ms
25 days agoHandshake completed124 ms
27 days agoHandshake completed55 ms
30 days agoHandshake completed61 ms

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

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