telo
REMOTE · TELO.HEALTH
Hosted Apple Health MCP for Claude and ChatGPT, works outside the US. iPhone app, no local server.
Available components
Last scanned (14 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (4)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +2
- HSTS header: fail → pass ▲ security
- 20 Nov 26 −44
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 19 Nov 26 0
- Tool “create_workout_plan” rewrote its description, which is the text the model reads security
- 18 Nov 26 +1
- Tool “list_metrics” rewrote its description, which is the text the model reads security
- 16 Nov 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.
- 13 Nov 26 +1
- Tool “create_workout_plan” rewrote its description, which is the text the model reads security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “data_status” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://telo.health/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=telo.health | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | dd0ef5592ea767311364ff35408885f7 |
| SANs: telo.health, *.telo.health | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of telo.health. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| health. | DS published | 42514 | 13 | Verified |
| telo.health. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://telo.health/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://telo.health/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://telo.health/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" |
Protected resource metadata
| Document | https://telo.health/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://telo.health/mcp |
| Authorisation server | https://telo.health |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://telo.health/mcp | Auth required | 401 | |
| http (plaintext) | http://telo.health/mcp | Inconclusive | 401 |
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 →
arrange_home Reorder or remove telo home cards ~130
Reorder cards, remove cards or remove marks, when the user asks to set up or tidy their home (e.g. 'set my home up for race week'). The reason is shown to the user in the change history, and every change can be undone on the phone.
| Name | Type | Req | Description |
|---|---|---|---|
| order | array | – | Card ids top to bottom; cards left out keep their relative order after these |
| reason | string | yes | Why, in one short line the user will read in the change history |
| remove | array | – | Card ids to remove |
| remove_marks | array | – | Mark ids to remove |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | – |
| marks | array | yes | – |
No examples provided.
cancel_workout_plan Cancel a planned workout ~87
Request cancellation of the user's identified workout plan. The iPhone must process removal, either during an automatic refresh or by opening telo > Planned workouts. Does not delete any recorded HealthKit result. Idempotent; cancel_requested is NOT confirmation of removal from Apple Watch. To change a prescription, cancel the old plan and create a new one for review.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| plan | object | yes | – |
No examples provided.
create_workout_plan Create a workout for Apple Watch ~682
Create one structured workout requested by the user, scheduled within the next 7 days. Stores a pending plan; does NOT immediately deliver to or start Apple Watch. The first delivery is manual: open telo on iPhone > Planned workouts and tap Schedule on Watch to grant permission. Afterwards the user may opt into automatic delivery for newly created plans on that iPhone. Background scheduling is opportunistic, not immediate; otherwise review each plan manually. Use seconds/meters and an explicit local UTC offset. definition.type picks the workout: custom (default: warmup, repeatable work/recovery blocks, cooldown), pacer (cover a distance in a set time; the Watch shows ahead/behind), single_goal (one goal for the whole session; the only way to set an active-calorie goal) or multisport (triathlon/duathlon legs). Each custom step may carry ONE alert (Apple Watch limit): heart_rate_range, heart_rate_zone (the Watch's zones 1-5), pace_range or pace_threshold (seconds per km or mi; e.g. 5:00-5:30/km = fastest_seconds 300, slowest_seconds 330), speed_range/speed_threshold (kph or mph), cadence_range/cadence_threshold, power_range/power_threshold (watts) or power_zone; metric average uses the step average instead of the current value. Support, from WorkoutKit: pace/speed for running and cycling; cadence and power for cycling and outdoor running only; power_zone for cycling only; walking, swimming, strength and the rest take heart-rate alerts only; distance goals for running, cycling, walking, hiking, swimming, wheelchair and outdoor rowing. Unsupported combinations are rejected here with the reason. Alerts, plan types other than custom and activities beyond running/cycling/walking/strength/functional_strength/hiit/swimming need telo 1.12+ on iPhone; next_step says when the user must update. Step names can describe reps/weights; these are instructions, not native repetition goals. Pool swimming uses activity=swimming and location=indoor only. Optional pool_length_m is displa…
| Name | Type | Req | Description |
|---|---|---|---|
| definition | – | yes | – |
| idempotency_key | string | yes | Reuse exactly this key and payload when retrying this creation. Use a new key for a different workout. |
| scheduled_at | string | yes | Future date/time within 7 days, including local UTC offset, e.g. 2026-10-27T07:00:00-03:00. |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| plan | object | yes | – |
No examples provided.
data_status Data availability and sync evidence ~191
Inspect before health reviews or investigating missing data. Returns the last received upload batch, collection date ranges/counts and per-metric coverage. Not a sync command. history_import is the iPhone's own report of its history import (complete, still arriving, or unknown for older app builds); while it is still arriving, collections.*.first_date and history_import.workout_details.reached_date say how far back it has reached, since it imports newest first; when next_step is present, relay its message to the user; last_night says whether last night's sleep is stored, may still be on its way, or did not come in an upload made after the user's usual wake time, and its message is what to say instead of 'no record'; HealthKit read permissions are unknown. An upload can be empty or re-send old records; old dates alone do not prove stalled sync. No account identifiers returned.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| collections | object | yes | – |
| healthkit_read_permissions | string | yes | – |
| history_import | object | yes | – |
| last_ingest | – | yes | – |
| last_night | – | yes | – |
| limitations | array | yes | – |
| metrics | array | yes | – |
| next_step | – | yes | – |
| refresh | – | – | – |
| setup | – | yes | – |
No examples provided.
derived_metrics Training load and personal baselines ~411
Duration-based training workload (minutes), excluding walking unless include_walking=true: rolling ATL 7 days, CTL 42 days, same-day TSB=CTL-ATL and acute/chronic ratio. Not intensity-weighted TSS. Every training row includes trimp_load, trimp_atl, trimp_ctl and trimp_tsb: simple zone TRIMP = sum(zone_seconds[z] * z / 60), with weights [0,1,2,3,4,5] for zones 0–5. TRIMP ATL/CTL use 7/42-day rolling means; TSB=CTL-ATL. max_hr overrides the observed workout maximum. include_trimp=true also returns the legacy trimp object with coverage details. Existing duration fields remain unchanged. TRIMP sums observed zone time; workouts without usable zones contribute zero, so rolling ATL/CTL/TSB remain numeric with incomplete coverage. trimp_coverage, trimp_coverage_7d and trimp_coverage_42d report the fraction of included workout duration with usable HR zones for the day and rolling windows. Covered seconds are capped per workout at its duration; coverage is null when there is no included duration. Missing workout days count as zero; coverage is reported. HRV SDNN and resting HR compared with the preceding 30–60 calendar days, excluding the target date; at least 7 valid daily values required. Includes mean, population SD, absolute/percentage delta and z-score. Maximum 500 total rows; narrow the range if truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_days | integer | – | – |
| from | string | yes | – |
| include_trimp | boolean | – | Include the legacy trimp object with coverage details; flat trimp_* fields are always returned |
| include_walking | boolean | – | Include walking in both duration and zone load; excluded by default |
| max_hr | number | – | Maximum HR for TRIMP; otherwise observed workout maximum through to |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| baselines | array | yes | – |
| method | string | yes | – |
| training_load | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
edit_card Edit a telo home card ~163
Change one card: title, window, style, comparison, usual range, color, size, change_from, or a goal the user stated. null removes an option. Call home first for ids.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | – | – | null removes the usual range |
| change_from | – | – | null returns to window_start |
| color | – | – | Only when the user asks. null returns to the category default |
| compare_with | – | – | null removes the comparison |
| goal | – | – | Only a goal the user stated. null removes it |
| id | string | yes | – |
| reason | string | – | – |
| size | – | – | half pairs with the next half card; null returns to full |
| style | string | – | – |
| title | string | – | – |
| window | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
home The user's telo home ~66
Read the cards on the user's telo iPhone home screen, the dated marks they asked you to keep (e.g. 'Sick', 'Intervals start'), and recent changes. Marks are context the user gave about their life; use them when interpreting their data. Call before editing the home.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | – |
| changes | array | yes | – |
| marks | array | yes | – |
No examples provided.
list_metrics List metrics ~84
Lists the available health metrics, the unit of each one, and how far back the data goes. Call this before query_daily if you do not know the exact metric names. On Telo Free, latest_before_window gives the last reading of sparse measurements (VO2 max, body mass, body composition) taken before the 7-day window; query_daily cannot read those dates.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| latest_before_window | array | – | – |
| metrics | array | yes | – |
| setup | object | – | – |
No examples provided.
mark_date Mark a date on the user's charts ~119
Keep a short note the user told you about a date or span (illness, travel, new training, new shoes). It appears on every telo chart covering that date and is returned by home to any assistant later. Only for facts the user stated, never your inference.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| end_date | string | – | For a span, e.g. a sick week |
| text | string | yes | 2-3 words the user will see on their charts: 'Sick', 'Intervals start', 'New shoes' |
| Name | Type | Req | Description |
|---|---|---|---|
| mark | object | yes | – |
No examples provided.
pin_card Pin a chart to the telo home ~464
Put a live chart on the user's telo iPhone home. Only when the user asks to pin, save, show or keep something on telo. The card keeps updating with each sync. Styles: trend (line), stat (number and change), bars. Optional: compare_with draws a second metric on the same window; baseline=personal draws the user's usual range; display=pace_km turns running_speed into min/km; goal only when the user stated one; color only when the user asks (cards default to a color per metric category); size=half puts two consecutive half cards side by side (a number and a small trend, details on tap); change_from=usual or year_ago changes what the change line compares with. Always pass the user's question in their words; it is shown on the card.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | – | Draw the person's usual range: mean ± 1 SD of the 60 days before the last week |
| change_from | string | – | What the card's change line compares today's value with. window_start (default): the first point of the window; usual: the user's own 60-day average ending a week ago; year_ago: the 14 days around th… |
| color | string | – | Only when the user asks for a color. Omit to use telo's default for the metric's category |
| compare_with | string | – | A second metric drawn on the same window, each on its own scale |
| display | string | – | Only for running_speed or walking_speed: show min:sec per km instead of m/s |
| goal | object | – | – |
| metric | string | yes | Exact metric name from list_metrics, e.g. vo2_max, running_speed, hrv_sdnn |
| position | string | – | – |
| question | string | yes | The user's question or request that led to this card, in their words |
| size | string | – | half: two consecutive half cards share a row, as a number and a small trend line. Default full |
| style | string | – | trend: line chart; stat: number and change; bars: per-day or per-week bars |
| title | string | – | – |
| window | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
pin_countdown Pin a countdown to the telo home ~177
Add a countdown to a date the user named (a race, a trip, a test) to their telo home. telo counts days; it never judges them.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Only when the user asks for a color. Omit to use telo's default for the metric's category |
| date | string | yes | – |
| detail | string | – | One short line, e.g. 'Target 5:00/km' |
| position | string | – | – |
| question | string | – | The user's question or request that led to this card, in their words |
| size | string | – | half: two consecutive half cards share a row, as a number and a small trend line. Default full |
| title | string | yes | What the person is counting down to, in their words: '10K race' |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No examples provided.
query_daily Query daily metrics ~184
Daily records or week/month aggregates. aggregation identifies sum or unweighted average of stored daily values; daily_min/max are extrema of daily values, not raw samples. days_present counts stored dates; days_expected counts calendar dates in period_start/end clipped to the request, not expected sensor wear. Units and aggregation methods are kept separate. Entirely missing buckets/metrics have no row: missing is not zero. Weekly labels use SQLite %Y-W%W (Monday weeks split at New Year), not ISO weeks; use period_start/end. Limit 500 rows. If truncated, discard the partial response and re-query smaller non-overlapping ranges aligned to complete buckets, or fewer metrics. Do not combine partial bucket averages without weighting by days_present.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| granularity | string | – | – |
| metrics | array | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | – |
| setup | object | – | – |
| truncated | boolean | yes | – |
No examples provided.
report_gap Note something telo cannot do yet ~197
Call when the user asked for something telo cannot do with the tools here: a chart or layout on the telo home, a metric telo does not have, data that is missing, a question no tool answers. Pass their request in their words, what you tried instead, and what is missing. Then tell the user you noted it for the telo team, without promising it will be built. Not for questions you can answer by reading their data.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | home: a chart, card or layout on the telo app; metric: a measure telo does not have; data: data missing or wrong; other |
| missing | string | yes | What telo lacks, e.g. 'bars stacked by workout activity', 'blood glucose', 'sleep before 2023' |
| request | string | yes | What the user asked for, in their words |
| tried | string | – | What you tried or offered instead, if anything |
| Name | Type | Req | Description |
|---|---|---|---|
| next_step | string | yes | – |
| noted | boolean | yes | – |
No examples provided.
sessions Sleep and workout sessions ~162
Sleep nights or workouts within an inclusive date range. Workout activity accepts run/bike/swim (or running/cycling/swimming). granularity=week groups workouts by Monday date and modality, summing duration, distance and estimated HR-zone seconds. Boundary weeks cover only the requested dates. Distance and zone coverage counts distinguish missing data from zero; max_hr uses the same definition as workout_detail. Filters and weekly grouping require kind=workout. Timestamps carry the local UTC offset.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | – |
| from | string | yes | – |
| granularity | string | – | – |
| kind | string | yes | – |
| max_hr | number | – | Personal maximum HR in bpm; otherwise uses observed workout maximum, an estimate |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | – |
| setup | object | – | – |
| truncated | boolean | yes | – |
No examples provided.
workout_detail Workout detail ~908
Detail for a workout UUID from sessions. Includes source/device, indoor flag, pool length, elevation gain, laps, classified segments, paired pause intervals, a swimming summary and reduced series when accessible in HealthKit. Summaries, events and zones are permanent; only raw series expire after 30 days. The iPhone must sync with a version that collects detail. raw_available and summary_available distinguish coverage. synced_at is the server ingestion time when recorded; older summaries fall back to the R2 object upload time (which may be the storage migration time). not_available means not synced. HR zones estimate active bucket time (excluding pauses) using one unambiguous HR source and six percent-max bands, including zone 0 below 50%. max_hr can override the observed personal workout maximum; observed maximum is an estimate, not a tested physiological maximum. Missing buckets are excluded and coverage is reported. Values[i] covers seconds [(offset+i)*interval_s, (offset+i+1)*interval_s) from workout start, clipped at elapsed_s; null is missing. Each series has its own source, do not sum or average duplicate metrics across sources. Averages are weighted by sample overlap; sums are prorated across buckets. Gaps and sampling limit precision, including time in HR zones. Events are normalized before pagination: pause/resume pairs become one pause with pause_kind and end_reason; unmatched resumes are marked, and trailing pauses end at workout end. Segment distance_basis distinguishes metadata from bucket estimates; distance_split labels are distance matches, not guaranteed native types. swimming_summary uses lap intervals minus the union of recorded pauses; gaps outside laps count as inferred rest. It preserves swimming_s, total_rest_s and pace_s_per_100m. wall_gaps exposes every consecutive unique lap transition (after_lap is 1-based, gap_s is next start minus previous end, manual_pause includes boundary/spanning pauses). sets contains HealthKit segments covering c…
| Name | Type | Req | Description |
|---|---|---|---|
| event_offset | integer | – | Independent event offset; use next_event_offset to continue |
| limit | integer | – | – |
| max_hr | number | – | Personal maximum HR in bpm; otherwise uses observed workout maximum, an estimate |
| metrics | array | – | Optional series names; [] returns metadata and events only |
| offset | integer | – | Series bucket offset; use next_offset to continue |
| uuid | string | yes | Workout UUID returned by sessions |
| wall_tolerance_s | number | – | Fixed swimming wall-gap tolerance in seconds (0–300). Default: clamp(P90 of non-manual gaps <=15s + 1s, 3s, 12s); fewer than 6 candidates uses 10s. Manual pauses always break continuity. |
| Name | Type | Req | Description |
|---|---|---|---|
| available_metrics | array | yes | – |
| detail | – | yes | – |
| event_offset | number | yes | – |
| hr_zones | object | yes | – |
| next_event_offset | number|null | yes | – |
| next_offset | number|null | yes | – |
| offset | number | yes | – |
| raw_available | boolean | yes | – |
| retention_days | number | yes | – |
| status | string | yes | – |
| summary_available | boolean | yes | – |
| synced_at | string|null | yes | – |
| total_buckets | number | yes | – |
| total_events | number | yes | – |
| truncated | boolean | yes | – |
| workout | – | yes | – |
No examples provided.
workout_plans Planned workouts and recorded results ~188
Read the latest 50 planned workouts, or one by id, including the original prescription, delivery state and first exactly linked HealthKit workout. pending awaits iPhone processing (manual review, or automatic scheduling if enabled on that iPhone); scheduled means the iPhone scheduler accepted it, NOT confirmed Watch delivery; cancel_requested awaits iPhone removal. recorded_workout=null means no linked result has synced, not proof the workout was skipped. A linked recording does not prove every prescribed interval was completed. Use its uuid with workout_detail for analysis and ask for perceived effort. If truncated, query a known id. Plans have no automatic edits. Automatic scheduling is an optional iPhone setting after a first manual delivery; its current value and background execution time are unknown to the server.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Get one plan and its exact HealthKit-linked result. Omit for the latest 50 plans. |
| Name | Type | Req | Description |
|---|---|---|---|
| plans | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
How do I install the telo MCP server?
telo is a hosted endpoint at https://telo.health/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · telo.health
claude mcp add --transport http health-telo-telo 'https://telo.health/mcp'
What is the telo MCP server?
telo is an MCP server listed in the public MCP registry as health.telo/telo. Hosted Apple Health MCP for Claude and ChatGPT, works outside the US. iPhone app, no local server. This page covers its hosted endpoint (https://telo.health/mcp).
Is the telo MCP server safe to use?
telo scores 33 out of 100 on VerifyMCP. 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 telo MCP server expose?
telo exposes 16 tools: create_workout_plan, workout_plans, cancel_workout_plan, data_status, list_metrics, and 11 more. Their descriptions and schemas cost roughly 4,213 tokens of context every time the server is loaded.
Does the telo MCP server require authentication?
Yes. telo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the telo MCP server still maintained?
telo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the telo MCP server?
VerifyMCP ran 4 checks on telo, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about telo: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.