Zelta BMI for Indians
REMOTE · BMI-MCP.ZELTA.IN
BMI check with Indian (Asian) cutoffs and a healthy weight range for any height.
Available components
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 295 tokens (~98/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +1
- Server version: 1.0.0 → 1.0.1 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bmi-mcp.zelta.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zelta.in | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e44e0d3a2832515c1328474436dd36f8 |
| SANs: zelta.in, bmi-mcp.zelta.in, *.bmi-mcp.zelta.in | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bmi-mcp.zelta.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| zelta.in. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bmi-mcp.zelta.in/mcp | Verified | 200 | |
| http (plaintext) | http://bmi-mcp.zelta.in/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bmi_check BMI check (Indian cutoffs) ~152
Use this when an adult asks for their BMI or whether their weight is normal, overweight or obese, such as "BMI for 72 kg 165 cm", "am I overweight at 5 ft 6 and 70 kg", or "BMI Asian cutoff". Shows the Asian-Indian category next to the WHO one. Do not use for children or teens under 18, pregnancy, diagnosis, or treatment and medication questions.
| Name | Type | Req | Description |
|---|---|---|---|
| height_cm | number | – | Height in centimetres |
| height_ft | number | – | Height feet part, if not using centimetres |
| height_in | number | – | Height inches part, used with height_ft |
| weight_kg | number | yes | Body weight in kilograms |
No output schema declared.
No examples provided.
healthy_weight_range Healthy weight range for a height ~134
Use this when an adult asks what weight is normal or ideal for a height, such as "ideal weight for 5 ft 4", "normal weight for 170 cm Indian male", or "how much should I weigh at 158 cm". Gives the BMI-based range under Asian-Indian and WHO cutoffs. Do not use for children, pregnancy, athletes judged on muscle, or diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| height_cm | number | – | Height in centimetres |
| height_ft | number | – | Height feet part, if not using centimetres |
| height_in | number | – | Height inches part, used with height_ft |
No output schema declared.
No examples provided.
How do I install the Zelta BMI for Indians MCP server?
Zelta BMI for Indians is a hosted endpoint at https://bmi-mcp.zelta.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bmi-mcp.zelta.in
claude mcp add --transport http in-zelta-bmi-india 'https://bmi-mcp.zelta.in/mcp'
What is the Zelta BMI for Indians MCP server?
Zelta BMI for Indians is an MCP server listed in the public MCP registry as in.zelta/bmi-india. BMI check with Indian (Asian) cutoffs and a healthy weight range for any height. This page covers its hosted endpoint (https://bmi-mcp.zelta.in/mcp).
Is the Zelta BMI for Indians MCP server safe to use?
Zelta BMI for Indians scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zelta BMI for Indians MCP server expose?
Zelta BMI for Indians exposes 2 tools: bmi_check, healthy_weight_range. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Does the Zelta BMI for Indians MCP server require authentication?
No. We connected to Zelta BMI for Indians without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zelta BMI for Indians MCP server still maintained?
Zelta BMI for Indians is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.