Remote MCP · Endpoint

io.github.pooriaarab/fertilityclinics MCP server

No. io.github.pooriaarab/fertilityclinics answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://fertilityclinics.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.pooriaarab/fertilityclinics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
US fertility and IVF clinics from the CDC's public data.
Listing
From the official MCP registry (active).
Recent checks of io.github.pooriaarab/fertilityclinics
CheckedResultHandshake
4 days agoHandshake completed175 ms
4 days agoHandshake completed2.40 s
5 days agoHandshake completed180 ms
7 days agoHandshake completed256 ms
8 days agoHandshake completed96 ms
9 days agoHandshake completed105 ms
10 days agoHandshake completed99 ms
11 days agoHandshake completed132 ms
12 days agoHandshake completed1.61 s
15 days agoHandshake completed454 ms
18 days agoHandshake completed197 ms
20 days agoHandshake completed1.03 s

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

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 io.github.pooriaarab/fertilityclinics and makes no claim about it beyond what these checks measured.