bodylog
PYPI · BODYLOG
Agent-first workout and food log: sets and meals from chat, USDA and Open Food Facts macros, cards.
Available components
Last scanned (17 hours ago)
Scores higher than 93% of PyPI servers
Category Health and Science
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to abhaymettu/bodylog). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1499 tokens (~99/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 4 Oct 26 +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.
- 1 Oct 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.
- 30 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 29 Sept 26 +11
- Provenance: unverified → pass ▲ security
- The attested source repository moved: abhaymettu/bodylog security
- 28 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
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 16 Oct 2026 · Analysed pypi/bodylog@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | abhaymettu/bodylog |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/abhaymettu/bodylog/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 2921884081 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:a1d4ac2694740971f3e2e7a3866b165091ed1da5df862997e00b7ad590e03a9c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
edit_food ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | – |
| carbs | – | – | – |
| delete | boolean | – | – |
| fat | – | – | – |
| food_id | – | – | – |
| grams | – | – | – |
| item_id | integer | yes | – |
| kcal | – | – | – |
| meal | – | – | – |
| name | – | – | – |
| protein | – | – | – |
| unit | – | – | – |
No output schema declared.
No examples provided.
edit_last_set ~79
Fix the most recent set in the open workout ("that was 10 reps", "that was cable pushdowns"), or delete it.
| Name | Type | Req | Description |
|---|---|---|---|
| delete | boolean | – | – |
| exercise | – | – | – |
| kind | – | – | – |
| notes | – | – | – |
| reps | – | – | – |
| rpe | – | – | – |
| unit | – | – | – |
| weight | – | – | – |
No output schema declared.
No examples provided.
end_session ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | – | – | – |
| theme | string | – | – |
| title | – | – | – |
| unit | – | – | – |
No output schema declared.
No examples provided.
exercise_history ~47
Per-session history for one exercise, newest first: sets, best set, top weight, estimated 1RM, volume.
| Name | Type | Req | Description |
|---|---|---|---|
| exercise | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
food_card ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
| style | string | – | – |
| theme | string | – | – |
No output schema declared.
No examples provided.
food_day ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
No output schema declared.
No examples provided.
import_chat ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
log_food ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | – | – | – |
| barcode | – | – | – |
| carbs | – | – | – |
| fat | – | – | – |
| food_id | – | – | – |
| grams | – | – | – |
| kcal | – | – | – |
| meal | – | – | – |
| name | – | – | – |
| protein | – | – | – |
| text | – | – | – |
| unit | – | – | – |
No output schema declared.
No examples provided.
log_set ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| exercise | – | – | – |
| kind | string | – | – |
| notes | – | – | – |
| reps | – | – | – |
| rpe | – | – | – |
| text | – | – | – |
| unit | – | – | – |
| weight | – | – | – |
No output schema declared.
No examples provided.
lookup_food ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | – | – | – |
| query | – | – | – |
No output schema declared.
No examples provided.
prs ~37
All-time records (heaviest weight, best estimated 1RM, most reps) for one exercise or all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| exercise | – | – | – |
No output schema declared.
No examples provided.
session_card ~116
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).
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | – | – | – |
| style | string | – | – |
| theme | string | – | – |
| unit | – | – | – |
No output schema declared.
No examples provided.
set_goals ~56
Daily targets (kcal, grams of protein/carbs/fat). Omitted ones stay as they are; 0 clears one.
| Name | Type | Req | Description |
|---|---|---|---|
| carbs | – | – | – |
| fat | – | – | – |
| kcal | – | – | – |
| protein | – | – | – |
No output schema declared.
No examples provided.
streaks ~29
Current food-logging streak in days (and the best), and training streak in weeks with a workout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_volume ~30
Training volume, workouts and sets per week (Monday start), oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| weeks | integer | – | – |
No output schema declared.
No examples provided.
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.
pypi · bodylog
claude mcp add abhaymettu-bodylog -- uvx bodylog
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.