Remote MCP · Endpoint

EKO-IKSI Fertility Clinic MCP server

No. EKO-IKSI Fertility Clinic answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://eko-iksi.uz/mcp

The last check completed an MCP handshake.

Registry name
uz.eko-iksi/eko-iksi-fertility-clinic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
397 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fertility clinic in Tashkent: prices, services, doctors, articles and contacts in uz, ru, en.
Listing
From the official MCP registry (active).
Recent checks of EKO-IKSI Fertility Clinic
CheckedResultHandshake
1 hour agoHandshake completed397 ms
2 days agoHandshake completed417 ms
5 days agoHandshake completed487 ms
7 days agoHandshake completed397 ms
9 days agoHandshake completed444 ms
11 days agoHandshake completed396 ms
13 days agoHandshake completed412 ms
15 days agoHandshake completed407 ms
17 days agoHandshake completed395 ms
19 days agoHandshake completed438 ms
20 days agoHandshake completed403 ms
22 days agoHandshake completed388 ms
23 days agoHandshake completed405 ms
25 days agoHandshake completed452 ms

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

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 EKO-IKSI Fertility Clinic and makes no claim about it beyond what these checks measured.