telo MCP server

None of its 16 tools are described as changing anything. For 16 the reading was uncertain, so no mark is shown.

• create_workout_plan

  “Create one structured workout requested by the user, scheduled within the next 7 days.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  3 inputs, 3 required

  • idempotency_keystringrequired“Reuse exactly this key and payload when retrying this creation.”
  • scheduled_atstringrequired“Future date/time within 7 days, including local UTC offset, e.g.”
  • definitionobjectrequired
• workout_plans

  “Read the latest 50 planned workouts, or one by id, including the original prescription, delivery state and first exactly linked HealthKit workout.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • idstring“Get one plan and its exact HealthKit-linked result.”
• cancel_workout_plan

  “Request cancellation of the user's identified workout plan.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  1 input, 1 required

  • idstringrequired
• data_statuson 10 other servers

  “Inspect before health reviews or investigating missing data.”

  Publisher declares: read-only no · destructive no · open-world no

  Takes no inputs.

• list_metricson 20 other servers

  “Lists the available health metrics, the unit of each one, and how far back the data goes.”

  Publisher declares: read-only no · destructive no · open-world no

  Takes no inputs.

• query_dailyon 1 other server

  “Daily records or week/month aggregates.”

  Publisher declares: read-only no · destructive no · open-world no

  4 inputs, 3 required

  • metricsarrayrequired
  • fromstringrequired
  • tostringrequired
  • granularitystring
• workout_detail

  “Detail for a workout UUID from sessions.”

  Publisher declares: read-only no · destructive no · open-world no

  7 inputs, 1 required

  • wall_tolerance_snumber“Fixed swimming wall-gap tolerance in seconds (0–300).”
  • max_hrnumber“Personal maximum HR in bpm; otherwise uses observed workout maximum, an estimate”
  • uuidstringrequired“Workout UUID returned by sessions”
  • metricsarray“Optional series names; [] returns metadata and events only”
  • offsetinteger“Series bucket offset; use next_offset to continue”
  • limitinteger
  • event_offsetinteger“Independent event offset; use next_event_offset to continue”
• sessionson 4 other servers

  “Sleep nights or workouts within an inclusive date range.”

  Publisher declares: read-only no · destructive no · open-world no

  6 inputs, 3 required

  • kindstringrequired
  • fromstringrequired
  • tostringrequired
  • activitystring
  • granularitystring
  • max_hrnumber“Personal maximum HR in bpm; otherwise uses observed workout maximum, an estimate”
• derived_metrics

  “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.”

  Publisher declares: read-only no · destructive no · open-world no

  6 inputs, 2 required

  • fromstringrequired
  • tostringrequired
  • baseline_daysinteger
  • include_walkingboolean“Include walking in both duration and zone load; excluded by default”
  • include_trimpboolean“Include the legacy trimp object with coverage details; flat trimp_* fields are always returned”
  • max_hrnumber“Maximum HR for TRIMP; otherwise observed workout maximum through to”
• homeon 10 other servers

  “Read the cards on the user's telo iPhone home screen, the dated marks they asked you to keep (e.g.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• pin_card

  “Put a live chart on the user's telo iPhone home.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  13 inputs, 2 required

  • metricstringrequired“Exact metric name from list_metrics, e.g.”
  • stylestring“trend: line chart; stat: number and change; bars: per-day or per-week bars”
  • windowstring
  • displaystring“Only for running_speed or walking_speed: show min:sec per km instead of m/s”
  • compare_withstring“A second metric drawn on the same window, each on its own scale”
  • baselinestring“Draw the person's usual range: mean ± 1 SD of the 60 days before the last week”
  • titlestring
  • goalobject
  • colorstring“Only when the user asks for a color.”
  • sizestring“half: two consecutive half cards share a row, as a number and a small trend line.”
  • change_fromstring“What the card's change line compares today's value with.”
  • questionstringrequired“The user's question or request that led to this card, in their words”
  • positionstring
• pin_countdown

  “Add a countdown to a date the user named (a race, a trip, a test) to their telo home.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  7 inputs, 2 required

  • titlestringrequired“What the person is counting down to, in their words: '10K race'”
  • datestringrequired
  • detailstring“One short line, e.g.”
  • colorstring“Only when the user asks for a color.”
  • sizestring“half: two consecutive half cards share a row, as a number and a small trend line.”
  • questionstring“The user's question or request that led to this card, in their words”
  • positionstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.