durability-mcp
Related Servers
Alternatives to durability-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables Claude to answer trail and ultra running questions from a local DuckDB warehouse built from Garmin FIT files, with 29 parameterised tools that compute running-only pace by grade, matched-terrain heart rate drift, segment comparisons and training load, each result stating its filters and exclusions.29MIT
- AlicenseBqualityBmaintenanceEnables local, read-only access to Oura API v2 data, returning pre-shaped physiology such as sleep, chronotype, temperature shifts, and baseline drift for interpretation by AI clients.91MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to query locally computed recovery, strain, sleep, workout, and heart-rate data from a personal SQLite database, with tools for daily and sleep summaries, workout details, heart-rate buckets, schema inspection, reports, sync, and read-only SQL.48MIT
- AlicenseNot gradedqualityAmaintenanceEnables read-only access to WHOOP recovery, sleep, HRV, strain, workout, and race-performance data so assistants like Claude, Codex, and GitHub Copilot can answer personal health questions, compare trends against personal baselines, and audit HYROX or triathlon training with local, evidence-backed dashboards. Includes aggregate mode, local-only race logging, and verification tools for recomputing claims.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local synchronization of Garmin activity and health data using a personal API key, then lets MCP-connected AI clients analyze training readiness and recovery with cited models and research. Supports viewing records, sleep/HRV, stress, Body Battery, and generating pre-run recommendations without hosting accounts or personal data.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables read-only access to WHOOP recovery, sleep, HRV, strain, and workout data so users can ask natural-language questions about daily readiness, personal baselines, sleep debt, and trends, plus HYROX and triathlon performance readiness and auditing. It runs locally with summary and aggregate modes, keeping data on the user's machine and sharing results only with the chosen AI assistant.14 npmMIT
TDQS
Scored across 3 tools
Each tool has a distinct scope: listing runs, evaluating one run's indices, and summarizing/trending over time. The descriptions explicitly delimit one-run vs aggregate analysis, so boundaries are clear.
All three names follow the same snake_case verb_durability_noun pattern: list_durability_runs, get_durability_indices, get_durability_trend. No mixed conventions or vague verbs.
Three tools are well-scoped for a focused read-only durability analytics server: list, detail, and trend. Each earns its place without redundancy.
The surface covers the natural read-only workflow: discover runs, inspect per-run durability indices with non-evaluable explanations, and compare trends over time. No create/update/delete is needed for this analysis-only domain.