Remote MCP · Endpoint

telo MCP server

No. telo answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://telo.health/mcp

The last check completed an MCP handshake.

Registry name
health.telo/telo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
16 tools
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Hosted Apple Health MCP for Claude and ChatGPT, works outside the US. iPhone app, no local server.
Listing
From the official MCP registry (active).
Recent checks of telo
CheckedResultHandshake
57 minutes agoHandshake completed256 ms
3 days agoHandshake completed44 ms
12 days agoHandshake completed312 ms
13 days agoHandshake completed320 ms

The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with telo and makes no claim about it beyond what these checks measured.