Remote MCP · Endpoint
BioRobot MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://biorobot-mcp.biorobot.workers.dev/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- help.biorobot/biorobot
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Human for hire by AI agents: ground-truth checks, photo evidence, errands near Crystal Lake, IL
- Website
- https://biorobot.help/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 1.04 s |
| 4 days ago | Handshake completed | 141 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 3.
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 BioRobot and makes no claim about it beyond what these checks measured.