DEV Community

Philip D'Souza
Philip D'Souza

Posted on

health-export-mcp v1.6.0: an agent should check the clock before it trusts a number

health-export-mcp v1.6.0 adds two tools, bringing the server to 16.

get_freshness answers a question most health agents skip: is this export current? It returns stale against a threshold the server states (26 hours by default, HEALTH_STALE_AFTER_HOURS, or a maxAgeHours argument), plus age_hours, as_of, last_data_date, data_lag_days and per-file write times. It uses the same rule as the status --max-age cron gate.

resolve_metric answers the other quiet problem: one metric under many names. steps, StepCount, Body Weight, hrv and a HealthKit identifier all map to one canonical metric and unit, with the unit variants other apps use and the exact conversion formula. Ambiguous names come back with candidates. A different measure such as RMSSD vs SDNN is refused with the reason, never guessed. The data tools accept the same aliases and report resolvedFrom.

No file format changed, so 1.5.0 exports work as they are. Full notes: https://github.com/PhilipAD/health-export-mcp/releases/tag/v1.6.0?utm_source=devto&utm_medium=social&utm_campaign=exp-20261006-hea185-v160

Top comments (0)