ham.run
Description
Open-source marathon physiology calculators for endurance runners. 12 tools: race time prediction (Riegel model), pacing strategy, fueling plans, running economy analysis, caffeine protocols, heat acclimation planning, periodization comparison, and grade-adjusted pace. Strava-connected tools for training load and activity analysis. All models are citation-backed from peer-reviewed exercise physiology research. Stateless tools work without authentication at ham.run.
What our measurements say
ham.run is a remote MCP server published at mcp.ham.run. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 364 ms, placing it among the faster endpoints. It offers a narrow, focused set of 13 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are generally descriptive (e.g., 'predict_race_time', 'fueling_plan')
- Citations from peer-reviewed research add credibility
- Strava integration and stateless functionality enhance usability
Weaknesses
- Some descriptions truncate mid-sentence (e.g., 'Predictions are point estimates with no confidence interval — treat a m')
- Parameter requirements (e.g., 'useMyData:true') are not universally documented in tool descriptions
- Limited differentiation between training plan tools ('generate_training_plan' vs 'generate_workout')
- No explicit error handling or constraint documentation in tool specifications
predict_race_time— Truncated description cuts off explanation of confidence interval limitationsfueling_plan— Parameter 'useMyData' is mentioned but not explained in the descriptionpacing_strategy— Complex output parameters (HR drift, sodium levels) lack usage contextgenerate_training_plan— Overlaps with 'generate_workout' in training prescription scopeget_training_load— TSS estimation method is unclear without authentication context
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy', complianceScore improved from null to 100 · indicates successful migration to stable environment with full compliance
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 37ms → warm 35ms (penalty 2ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.0
- Supported versions: — → 2025-06-18
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/hamrun-hamrun)<a href="https://mcpmetrics.io/servers/hamrun-hamrun"><img src="https://mcpmetrics.io/badge/hamrun/hamrun/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see