Remote MCP · Endpoint

Lab4U MCP server

Yes, as of 38 minutes ago: the request timed out.

DownLast checked 38 minutes ago

Server URL

https://mcp.lab4u.ru/mcp

The last check failed: the request timed out.

Registry name
ru.lab4u.mcp/lab4u
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Lab4U (Russia): pick lab tests for a goal or a doctor's list and build a cart on lab4u.ru
Listing
From the official MCP registry (active).
Recent checks of Lab4U
CheckedResultHandshake
38 minutes agoFailed - the request timed out—
3 days agoHandshake completed419 ms
13 days agoHandshake completed377 ms
13 days agoHandshake completed431 ms
15 days agoHandshake completed415 ms
16 days agoHandshake completed571 ms
17 days agoHandshake completed390 ms
18 days agoHandshake completed363 ms
18 days agoHandshake completed385 ms
20 days agoHandshake completed441 ms
22 days agoHandshake completed561 ms
25 days agoHandshake completed451 ms
27 days agoHandshake completed593 ms

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

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