Body Metrics
BMI, calories, and protein — with the uncertainty shown.
Why delegate this
Two failure modes at once. A bare number is ambiguous — "170" is a height in centimetres or a weight in pounds — and a wrong unit yields a plausible BMI that is off by a factor of two. And the standard energy formulas disagree by hundreds of calories, so any single figure is false precision.
Tools
body_metrics
BMI, calories, and protein with error bounds
Compute BMI, energy expenditure, and protein targets from height and weight. Height and weight MUST carry units — a bare number is REFUSED rather than guessed, because a unit mix-up produces a plausible-looking answer that is badly wrong. Returns every standard BMR formula plus the spread between them, because the spread IS the precision of the estimate. Do not relay a single calorie figure as though it were exact. Not medical advice, and the response says so in its payload.
Direct endpoint:
https://body-metrics-tau.vercel.app/api/v1/metrics
Two ways to call it
Through the aggregator, which gives you every other tool at the same time:
claude mcp add --transport http gumball https://gumballtools.com/api/mcpOr directly, if this is the only capability you want:
claude mcp add --transport http body-metrics https://body-metrics-tau.vercel.app/api/mcp