# trainbud

Talk to your own fitness data. Findings computed in code against your own 28-day baselines.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.8.0
- **Author:** io.github.Zsadigzade
- **License:** MIT
- **npm:** trainbud
- **Source:** https://github.com/Zsadigzade/trainbud
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-16T11:26:46.171Z
- **Version scanned:** 0.8.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get_latest_activity` — Returns the most recent Garmin activity with distance, duration, pace, and heart rate stats.
- `get_activities_range` — Returns Garmin activities within an ISO 8601 date range.
- `get_body_composition` — Returns weight, body fat, and muscle mass trends over a time period.
- `compare_workouts` — Compares one workout against the user's own earlier workouts of the same type and a similar distance (or duration, for sports that record no distance). Reports 
- `remember_context` — Records something about the user that Garmin does not know: a goal, a race and its date, an injury, or a free-form note. Use this whenever the user mentions one
- `get_user_context` — Returns the goals, races, injuries and notes on record for the user. Read this before giving training advice.
- `log_subjective` — Records how a day or session actually felt, rated 1-10: perceived effort (rpe), soreness, or mood. Garmin has no equivalent.
- `get_findings` — Returns what stands out in the user's stored history against their own 28-day baselines: resting heart rate elevation, sleep debt, HRV trend breaks, and trainin
- `get_heart_rate_trends` — Returns resting, max, and average heart rate trends over a time period.
- `get_recovery_status` — Combines HRV, sleep, stress, and resting heart rate into a recovery score and training recommendation.
- `get_sleep_data` — Returns sleep duration, quality score, stage breakdown, and interruptions for recent nights.
- `get_stress_levels` — Returns daily stress averages and trends from Garmin Connect.
- `get_training_insights` — Returns a combined weekly training summary: latest activity, recent workouts, sleep, recovery, and stress.
- `get_vo2_max_trends` — Returns VO2 max fitness trends over time from Garmin Connect.
- `get_week_review` — Returns this training week against the previous one — sessions, training load, sleep, resting heart rate, HRV and stress — plus where the acute:chronic load rat

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"trainbud\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"trainbud\"\n      ],\n      \"env\": {\n        \"GARMIN_PASSWORD\": \"<YOUR_GARMIN_PASSWORD>\",\n        \"ANTHROPIC_API_KEY\": \"<YOUR_ANTHROPIC_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `GARMIN_PASSWORD` — Garmin Password (required)
- `ANTHROPIC_API_KEY` — Anthropic API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 25, ceiling 25 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/trainbud
- Install plan: https://forgeregistry.com/api/v1/packages/trainbud/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/trainbud
- HTML page: https://forgeregistry.com/registry/trainbud
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.