Remote MCP · Endpoint

Labreador MCP server

No. Labreador answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://labreador.com/mcp

The last check completed an MCP handshake.

Registry name
com.labreador/labreador
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
962 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Bioassay & ecotoxicology calculators: ELISA 4PL/5PL curves, dietary risk, pollution indices.
Website
https://labreador.com/
Listing
From the official MCP registry (active).
Recent checks of Labreador
CheckedResultHandshake
17 minutes agoHandshake completed962 ms
9 days agoHandshake completed1.20 s
9 days agoHandshake completed1.54 s
11 days agoHandshake completed1.08 s
12 days agoHandshake completed1.97 s
13 days agoHandshake completed1.48 s
14 days agoHandshake completed1.86 s
14 days agoHandshake completed1.34 s
16 days agoHandshake completed1.44 s
19 days agoHandshake completed1.34 s
21 days agoHandshake completed1.45 s
24 days agoHandshake completed1.08 s
26 days agoHandshake completed982 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Labreador and makes no claim about it beyond what these checks measured.