Remote MCP · Endpoint

Biohacking Kompakt MCP server

No. Biohacking Kompakt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.biohackingkompakt.de/mcp

The last check completed an MCP handshake.

Registry name
de.biohackingkompakt/biohacking-kompakt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
187 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Evidence-rated German database of supplements, peptides and longevity methods, plus podcast.
Listing
From the official MCP registry (active).
Recent checks of Biohacking Kompakt
CheckedResultHandshake
1 hour agoHandshake completed187 ms
1 day agoHandshake completed208 ms
3 days agoHandshake completed178 ms
6 days agoHandshake completed262 ms
7 days agoHandshake completed165 ms
9 days agoHandshake completed46 ms
10 days agoHandshake completed301 ms
11 days agoHandshake completed262 ms
13 days agoHandshake completed145 ms
15 days agoHandshake completed183 ms
17 days agoHandshake completed261 ms
19 days agoHandshake completed459 ms
20 days agoHandshake completed124 ms
21 days agoHandshake completed126 ms
22 days agoHandshake completed132 ms

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

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