# Body Metrics (remote · body-metrics.gumballtools.com)

Convert height and weight, compute BMI, TDEE and protein targets with error bounds.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `body-metrics.gumballtools.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp.md), [page](https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp)

## Channel facts

- Endpoint: `https://body-metrics.gumballtools.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-gumballtools-body-metrics 'https://body-metrics.gumballtools.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gumballtools-body-metrics": {
      "url": "https://body-metrics.gumballtools.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gumballtools-body-metrics": {
      "type": "http",
      "url": "https://body-metrics.gumballtools.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gumballtools-body-metrics]
url = "https://body-metrics.gumballtools.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gumballtools-body-metrics": {
      "type": "remote",
      "url": "https://body-metrics.gumballtools.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gumballtools-body-metrics --url 'https://body-metrics.gumballtools.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gumballtools-body-metrics:
    url: "https://body-metrics.gumballtools.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gumballtools-body-metrics": {
      "Transport": "http",
      "Url": "https://body-metrics.gumballtools.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gumballtools-body-metrics -t streamable-http -u 'https://body-metrics.gumballtools.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, +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.

### 2026-09-22 (score 72, +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.

### 2026-09-19 (score 71, +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.

### 2026-09-17 (score 70, +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.

### 2026-09-15 (score 69, +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.

### 2026-09-13 (score 68, +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.

### 2026-09-11 (score 67, +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.

## MCP tools (1)

### `body_metrics` (~695 tokens)

BMI, calories, and protein with error bounds

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.

Input parameters:

- `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, required): 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, required): 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, required): Required by the BMR equations, which are fitted separately.
- `targetBmi` (number): Target BMI, 15-40, to compute a goal weight.
- `weight` (string, required): Weight WITH a unit. Accepts 75kg, 165lb, 11st 8lb. A bare number is REFUSED.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 64
- 2026-09-05: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://body-metrics.gumballtools.com/api/mcp
- Repository: https://github.com/bwalvoord/gumball
- Website: https://body-metrics.gumballtools.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-gumballtools-body-metrics/api-mcp