# bodylog (pypi · bodylog)

Agent-first workout and food log: sets and meals from chat, USDA and Open Food Facts macros, cards.

- Trust score: 90/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- pypi · `bodylog`: 90/100 (this document), [markdown](https://verifymcp.io/servers/abhaymettu-bodylog/bodylog.md), [page](https://verifymcp.io/servers/abhaymettu-bodylog/bodylog)

## Channel facts

- Registry: `pypi`
- Package: `bodylog`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-10-16.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to abhaymettu/bodylog).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1499 tokens (~99/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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 bodylog MCP server?

bodylog runs locally as a PyPI package, launched with uvx bodylog. 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 abhaymettu-bodylog -- uvx bodylog
```

### Cursor

```json
{
  "mcpServers": {
    "abhaymettu-bodylog": {
      "command": "uvx",
      "args": [
        "bodylog"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "abhaymettu-bodylog": {
      "command": "uvx",
      "args": [
        "bodylog"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add abhaymettu-bodylog -- uvx bodylog
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "abhaymettu-bodylog": {
      "type": "local",
      "command": [
        "uvx",
        "bodylog"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add abhaymettu-bodylog --command uvx --arg bodylog
```

### Hermes

```yaml
mcp_servers:
  abhaymettu-bodylog:
    command: "uvx"
    args: ["bodylog"]
```

### Netclaw

```json
{
  "McpServers": {
    "abhaymettu-bodylog": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "bodylog"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add abhaymettu-bodylog -t stdio -c uvx -a bodylog
```

### Other

```json
{
  "mcpServers": {
    "abhaymettu-bodylog": {
      "command": "uvx",
      "args": [
        "bodylog"
      ]
    }
  }
}
```

## 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-10-16 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 88, +4)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 63. That category is still filling its 30-day observation window: 11 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-10-04 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 83, +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-30 (score 82, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-29 (score 79, +11)

- [security improvement] Provenance: unverified → pass
- [security] The attested source repository moved: abhaymettu/bodylog

### 2026-09-28 (score 68, 0)

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

## MCP tools (15)

### `log_set` (~203 tokens)

Log a set to the current workout, starting one if none is open.

exercise: name as the user says it ("incline db curl"); omit to reuse the last set's exercise.
weight/unit: 0 or omitted for bodyweight; unit is kg or lb (defaults to the last unit used).
kind: normal, warmup, drop or failure. count: identical sets at once ("3x10").
text: alternatively, the user's raw message ("62.5kg x 6", "same", "this is tricep pushdowns btw").
Returns the logged sets and any PRs they set. A text that ends the workout ("done, 1h 5m") returns the card.

Input parameters:

- `count` (integer)
- `exercise`
- `kind` (string)
- `notes`
- `reps`
- `rpe`
- `text`
- `unit`
- `weight`

### `edit_last_set` (~79 tokens)

Fix the most recent set in the open workout ("that was 10 reps", "that was cable pushdowns"), or delete it.

Input parameters:

- `delete` (boolean)
- `exercise`
- `kind`
- `notes`
- `reps`
- `rpe`
- `unit`
- `weight`

### `end_session` (~101 tokens)

End the open workout. duration is what the user says ("1h 5m", "65 min", "1:05"); title is optional
("Push Day"). unit (kg or lb) sets the totals' unit. Returns the summary card as text and PNG images
(one per page; long workouts span several) to show the user.

Input parameters:

- `duration`
- `theme` (string)
- `title`
- `unit`

### `session_card` (~116 tokens)

Summary card (text + PNG pages) for a workout: the open one, else the latest. theme: dark, light, or
clear (transparent background, a sticker for a photo); unit: kg or lb for totals (each set keeps the unit
it was logged in); style: full (every set, may span pages) or story (one phone-screen image, one line
per exercise).

Input parameters:

- `session_id`
- `style` (string)
- `theme` (string)
- `unit`

### `exercise_history` (~47 tokens)

Per-session history for one exercise, newest first: sets, best set, top weight, estimated 1RM, volume.

Input parameters:

- `exercise` (string, required)
- `limit` (integer)

### `prs` (~37 tokens)

All-time records (heaviest weight, best estimated 1RM, most reps) for one exercise or all of them.

Input parameters:

- `exercise`

### `weekly_volume` (~30 tokens)

Training volume, workouts and sets per week (Monday start), oldest first.

Input parameters:

- `weeks` (integer)

### `import_chat` (~67 tokens)

Backfill workouts from a pasted chat log (lines like "[2026-09-08 18:07] me: 60kg x 8").
Safe to repeat: time spans that already hold sets are skipped. Lists lines it could not read.

Input parameters:

- `text` (string, required)

### `log_food` (~237 tokens)

Log food. Usually pass the user's words as text ("2 eggs, toast and a protein shake", "lunch: 200g chicken,
1 cup rice"); it is split into items and each is matched to USDA FoodData Central or Open Food Facts.
For one item: name (or barcode, or a food_id from lookup_food) with grams, or amount + unit (cup, slice, tbsp,
oz, ml...). Pass kcal/protein/carbs/fat when the user reads them off a label. meal: breakfast, lunch, dinner
or snack (default from the words, else the time of day).
Each item has a status: ok / manual count; unknown (no match; see candidates) and needs_amount do not count
until fixed with edit_food. Returns the items and the day's totals so far.

Input parameters:

- `amount`
- `barcode`
- `carbs`
- `fat`
- `food_id`
- `grams`
- `kcal`
- `meal`
- `name`
- `protein`
- `text`
- `unit`

### `edit_food` (~123 tokens)

Fix a logged food item by id: a new amount (grams, or amount + unit), another food (name, or food_id from
lookup_food or an item's candidates), another meal, or the numbers themselves. delete=True removes it.

Input parameters:

- `amount`
- `carbs`
- `delete` (boolean)
- `fat`
- `food_id`
- `grams`
- `item_id` (integer, required)
- `kcal`
- `meal`
- `name`
- `protein`
- `unit`

### `lookup_food` (~63 tokens)

Search foods without logging: a name ("kimchi", "clif bar") or a product barcode. Returns candidates with
per-100 g macros, portions and a food_id to pass to log_food or edit_food.

Input parameters:

- `barcode`
- `query`

### `food_day` (~49 tokens)

One day's food (default today, YYYY-MM-DD): items by meal, totals, goals and what is left, streaks,
items not counted, and any workouts that day.

Input parameters:

- `date`

### `food_card` (~75 tokens)

Shareable card for a day of food (default today): text plus a PNG. theme: dark, light or clear; style:
full (every item) or story (one phone screen). Workouts that day appear on it too.

Input parameters:

- `date`
- `style` (string)
- `theme` (string)

### `set_goals` (~56 tokens)

Daily targets (kcal, grams of protein/carbs/fat). Omitted ones stay as they are; 0 clears one.

Input parameters:

- `carbs`
- `fat`
- `kcal`
- `protein`

### `streaks` (~29 tokens)

Current food-logging streak in days (and the best), and training streak in weeks with a workout.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/abhaymettu-bodylog/bodylog#diagnostics

## Score history

- 2026-10-16: 90
- 2026-10-15: 89
- 2026-10-14: 89
- 2026-10-13: 88
- 2026-10-12: 88
- 2026-10-04: 84
- 2026-10-03: 83
- 2026-10-02: 83
- 2026-10-01: 83
- 2026-09-30: 82
- 2026-09-29: 79
- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 68
- 2026-09-25: 68
- 2026-09-24: 66
- 2026-09-23: 66

## Common questions

### What is the bodylog MCP server?

bodylog is an MCP server listed in the public MCP registry as io.github.abhaymettu/bodylog. Agent-first workout and food log: sets and meals from chat, USDA and Open Food Facts macros, cards. This page covers its PyPI package (bodylog).

### Is the bodylog MCP server safe to use?

bodylog scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. 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 bodylog MCP server expose?

bodylog exposes 15 tools: log_set, edit_last_set, end_session, session_card, exercise_history, and 10 more. Their descriptions and schemas cost roughly 1,312 tokens of context every time the server is loaded.

### Is the bodylog MCP server still maintained?

bodylog is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the bodylog MCP server under?

bodylog declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/bodylog/
- Socket report: https://socket.dev/pypi/package/bodylog
- Repository: https://github.com/abhaymettu/bodylog
- Changelog RSS feed: https://verifymcp.io/servers/abhaymettu-bodylog/bodylog.xml
- Changelog JSON feed: https://verifymcp.io/servers/abhaymettu-bodylog/bodylog.json
- HTML version of this page: https://verifymcp.io/servers/abhaymettu-bodylog/bodylog