Remote MCP · Endpoint

Laborregister Deutschland MCP server

No. Laborregister Deutschland answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://laborregister.de/mcp

The last check completed an MCP handshake.

Registry name
de.laborregister/laborregister
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
424 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Orderable lab tests in Germany by analysis parameter, sample type and provider, with source links.
Listing
From the official MCP registry (active).
Recent checks of Laborregister Deutschland
CheckedResultHandshake
1 hour agoHandshake completed424 ms
10 days agoHandshake completed394 ms
10 days agoHandshake completed356 ms
11 days agoHandshake completed351 ms
12 days agoHandshake completed363 ms
14 days agoHandshake completed358 ms
14 days agoHandshake completed390 ms
15 days agoHandshake completed377 ms
17 days agoHandshake completed367 ms
19 days agoHandshake completed381 ms
21 days agoHandshake completed363 ms
24 days agoHandshake completed362 ms
26 days agoHandshake completed396 ms
28 days agoHandshake completed366 ms

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

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