Remote MCP · Endpoint

Zelta BMI for Indians MCP server

No. Zelta BMI for Indians answered an MCP handshake 46 minutes ago.

UpLast checked 46 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
in.zelta/bmi-india
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
91 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
BMI check with Indian (Asian) cutoffs and a healthy weight range for any height.
Listing
From the official MCP registry (active).
Recent checks of Zelta BMI for Indians
CheckedResultHandshake
46 minutes agoHandshake completed91 ms
3 days agoHandshake completed55 ms
13 days agoHandshake completed91 ms
13 days agoHandshake completed88 ms
15 days agoHandshake completed98 ms
16 days agoHandshake completed85 ms
17 days agoHandshake completed108 ms
18 days agoHandshake completed74 ms
18 days agoHandshake completed62 ms
20 days agoHandshake completed111 ms
22 days agoHandshake completed73 ms
25 days agoHandshake completed230 ms
27 days agoHandshake completed54 ms
30 days agoHandshake completed50 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 BMI for Indians and makes no claim about it beyond what these checks measured.