Body Metrics
REMOTE · BODY-METRICS.GUMBALLTOOLS.COM · SCANNED SEP 25
Convert height and weight, compute BMI, TDEE and protein targets with error bounds.
Available components
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
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 695 tokens (~695/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Body Metrics MCP server?
Body Metrics is a hosted endpoint at https://body-metrics.gumballtools.com/api/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 · body-metrics.gumballtools.com
claude mcp add --transport http com-gumballtools-body-metrics 'https://body-metrics.gumballtools.com/api/mcp'
{
"mcpServers": {
"com-gumballtools-body-metrics": {
"url": "https://body-metrics.gumballtools.com/api/mcp"
}
}
} {
"servers": {
"com-gumballtools-body-metrics": {
"type": "http",
"url": "https://body-metrics.gumballtools.com/api/mcp"
}
}
} [mcp_servers.com-gumballtools-body-metrics] url = "https://body-metrics.gumballtools.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gumballtools-body-metrics": {
"type": "remote",
"url": "https://body-metrics.gumballtools.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-gumballtools-body-metrics --url 'https://body-metrics.gumballtools.com/api/mcp' --transport streamable-http
mcp_servers:
com-gumballtools-body-metrics:
url: "https://body-metrics.gumballtools.com/api/mcp" {
"McpServers": {
"com-gumballtools-body-metrics": {
"Transport": "http",
"Url": "https://body-metrics.gumballtools.com/api/mcp"
}
}
} assistant mcp add com-gumballtools-body-metrics -t streamable-http -u 'https://body-metrics.gumballtools.com/api/mcp'
{
"mcpServers": {
"com-gumballtools-body-metrics": {
"type": "http",
"url": "https://body-metrics.gumballtools.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 25 Sept 2026 · Probed https://body-metrics.gumballtools.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.gumballtools.com | CN=YR2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 60927985e79d22e7a1106139f609d74b0e4 |
| SANs: *.gumballtools.com, gumballtools.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of body-metrics.gumballtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gumballtools.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://body-metrics.gumballtools.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://body-metrics.gumballtools.com/api/mcp | HTTPS enforced | 308 | https://body-metrics.gumballtools.com/api/mcp |
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 →
body_metrics BMI, calories, and protein with error bounds ~695
Compute BMI, energy expenditure, and protein targets from height and weight, with explicit error bounds. Use this for any of those calculations rather than doing the arithmetic. Two reasons, and the second is the important one: 1. UNITS. A bare number is ambiguous — "170" is a height in centimetres or a weight in pounds depending entirely on context, and a wrong unit yields a plausible BMI that is off by a factor of two. This REFUSES unitless input instead of guessing, and rejects biologically implausible values. 2. FALSE PRECISION. The standard equations disagree. Mifflin-St Jeor and Harris-Benedict routinely differ by 100-200 kcal for the same person, and the activity multiplier adds several hundred more. Every calculator on the internet reports one formula to the calorie. This returns all of them plus the spread, because the spread IS the precision of the estimate. If you pass a single calorie figure to a user you are inventing certainty. Input: `height` and `weight` MUST carry units (178cm, 5'10", 75kg, 165lb, 11st 8lb). `sex` and `age` are required by the equations. `bodyFatPercent` is optional and worth supplying — it adds the Katch-McArdle estimate and moves protein onto lean mass. `activity`, `proteinGoal`, `targetBmi`, and `dailyDeficitKcal` are optional. Returns: both unit systems, BMI with WHO category AND the lower cutoffs WHO publishes for South and East Asian populations, every BMR estimate with the spread in calories and percent, a TDEE range, a protein range, an optional target and timeline, warnings, and a `disclaimer` field. THIS IS NOT MEDICAL ADVICE and the response says so in its payload, not just on the page. Report the range and the disclaimer to the user. Do not present these figures as clinical guidance, and do not strip the caveats — they are the honest part of the answer.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Activity band, default sedentary. This is the LARGEST source of error in the estimate — most people overestimate. If between two bands, take the lower. |
| age | number | yes | Years, 15-100. Outside that the equations do not apply. |
| bodyFatPercent | number | – | Optional but worth supplying: adds the Katch-McArdle estimate, which uses lean mass, and moves the protein target onto lean mass. |
| dailyDeficitKcal | number | – | Daily deficit, to estimate a timeline. The timeline is a lower bound. |
| height | string | yes | Height WITH a unit. Accepts 178cm, 1.78m, 5'10", 5 ft 10 in, 70in. A bare number is REFUSED because it is ambiguous. |
| proteinGoal | string | – | Which protein guidance range to report. Default maintenance. |
| sex | string | yes | Required by the BMR equations, which are fitted separately. |
| targetBmi | number | – | Target BMI, 15-40, to compute a goal weight. |
| weight | string | yes | Weight WITH a unit. Accepts 75kg, 165lb, 11st 8lb. A bare number is REFUSED. |
No output schema declared.
No examples provided.
What is the Body Metrics MCP server?
Body Metrics is an MCP server listed in the public MCP registry as com.gumballtools/body-metrics. Convert height and weight, compute BMI, TDEE and protein targets with error bounds. This page covers its hosted endpoint (https://body-metrics.gumballtools.com/api/mcp).
Is the Body Metrics MCP server safe to use?
Body Metrics scores 73 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 Body Metrics MCP server expose?
Body Metrics exposes 1 tool: body_metrics. Their descriptions and schemas cost roughly 695 tokens of context every time the server is loaded.
Does the Body Metrics MCP server require authentication?
No. We connected to Body Metrics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Body Metrics MCP server still maintained?
Body Metrics is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.