Convert height and weight, compute BMI, TDEE and protein targets with error bounds.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Years, 15-100. Outside that the equations do not apply.
Required by the BMR equations, which are fitted separately.
Height WITH a unit. Accepts 178cm, 1.78m, 5'10", 5 ft 10 in, 70in. A bare number is REFUSED because it is ambiguous.
Weight WITH a unit. Accepts 75kg, 165lb, 11st 8lb. A bare number is REFUSED.
Activity band, default sedentary. This is the LARGEST source of error in the estimate — most people overestimate. If between two bands, take the lower.
Target BMI, 15-40, to compute a goal weight.
Which protein guidance range to report. Default maintenance.
Optional but worth supplying: adds the Katch-McArdle estimate, which uses lean mass, and moves the protein target onto lean mass.
Daily deficit, to estimate a timeline. The timeline is a lower bound.
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.
| Argument | Type | Description |
|---|---|---|
| age* | number | Years, 15-100. Outside that the equations do not apply. |
| sex* | string | Required by the BMR equations, which are fitted separately. |
| height* | string | Height WITH a unit. Accepts 178cm, 1.78m, 5'10", 5 ft 10 in, 70in. A bare number is REFUSED because it is ambiguous. |
| weight* | string | Weight WITH a unit. Accepts 75kg, 165lb, 11st 8lb. A bare number is REFUSED. |
| 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. |
| targetBmi | number | Target BMI, 15-40, to compute a goal weight. |
| proteinGoal | string | Which protein guidance range to report. Default maintenance. |
| 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. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"height",
"weight",
"sex",
"age"
],
"properties": {
"age": {
"type": "number",
"description": "Years, 15-100. Outside that the equations do not apply."
},
"sex": {
"enum": [
"male",
"female"
],
"type": "string",
"description": "Required by the BMR equations, which are fitted separately."
},
"height": {
"type": "string",
"description": "Height WITH a unit. Accepts 178cm, 1.78m, 5'10\", 5 ft 10 in, 70in. A bare number is REFUSED because it is ambiguous."
},
"weight": {
"type": "string",
"description": "Weight WITH a unit. Accepts 75kg, 165lb, 11st 8lb. A bare number is REFUSED."
},
"activity": {
"enum": [
"sedentary",
"light",
"moderate",
"active",
"extreme"
],
"type": "string",
"description": "Activity band, default sedentary. This is the LARGEST source of error in the estimate — most people overestimate. If between two bands, take the lower."
},
"targetBmi": {
"type": "number",
"description": "Target BMI, 15-40, to compute a goal weight."
},
"proteinGoal": {
"enum": [
"maintenance",
"active",
"strength",
"deficit"
],
"type": "string",
"description": "Which protein guidance range to report. Default maintenance."
},
"bodyFatPercent": {
"type": "number",
"description": "Optional but worth supplying: adds the Katch-McArdle estimate, which uses lean mass, and moves the protein target onto lean mass."
},
"dailyDeficitKcal": {
"type": "number",
"description": "Daily deficit, to estimate a timeline. The timeline is a lower bound."
}
}
}