Remote MCP · Endpoint

Human Handoff relay MCP server

No. Human Handoff relay answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://relay.cloudforbots.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/relay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
204 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hands CAPTCHAs, 2FA codes and approvals from your agent to your human with one tap.
Listing
From the official MCP registry (active).
Recent checks of Human Handoff relay
CheckedResultHandshake
13 minutes agoHandshake completed204 ms
10 days agoHandshake completed185 ms
10 days agoHandshake completed199 ms
11 days agoHandshake completed255 ms
13 days agoHandshake completed164 ms
14 days agoHandshake completed180 ms
14 days agoHandshake completed266 ms
15 days agoHandshake completed296 ms
17 days agoHandshake completed661 ms
19 days agoHandshake completed192 ms
21 days agoHandshake completed169 ms
24 days agoHandshake completed202 ms
26 days agoHandshake completed134 ms
28 days agoHandshake completed129 ms

The last 14 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 Human Handoff relay and makes no claim about it beyond what these checks measured.