Remote MCP · Endpoint

MyAIDoctor / Elite Health AI MCP server

No. MyAIDoctor / Elite Health AI answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://myaidoctor.health/mcp

The last check completed an MCP handshake.

Registry name
health.myaidoctor/myaidoctor
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
544 ms
Tools exposed
9 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
EliteHealthAI. General wellness information and questions to prepare for your doctor.
Listing
From the official MCP registry (active).
Recent checks of MyAIDoctor / Elite Health AI
CheckedResultHandshake
6 hours agoHandshake completed544 ms
4 days agoHandshake completed742 ms
7 days agoHandshake completed550 ms

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

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 MyAIDoctor / Elite Health AI and makes no claim about it beyond what these checks measured.