mcpbeat Sign in

Human Handoff relay MCP Server

not responding

Human Handoff relay is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Hands CAPTCHAs, 2FA codes and approvals from your agent to your human with one tap.

Uptime history 16 days of history · worst day 38%
16 days agonow
47.8%
Uptime 24h
44 of 92 checks
5
Tools
read from the server
348 ms
Response time
average over 24h
open, no key
Access
streamable-http

Human Handoff relay does not always answer

Over the last week it answered 55.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add relay --transport http https://relay.cloudforbots.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://relay.cloudforbots.com/mcp
~/.codex/config.toml
[mcp_servers.relay]
url = "https://relay.cloudforbots.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "relay": {
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "relay": {
      "type": "http",
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

request
check_request
Poll a request: pending, done, approved, denied, code_ready, expired or cancelled. For 2fa_code, the code is returned exactly once (single read) and only within 10 minutes of the person sending it; then it is wiped.
request_human
Hand one blocked step to your human: a CAPTCHA, a 2FA/OTP code, an approval, or a sign-in your agent should not do alone. Pro acts: sends your person a one-tap link (to notify_webhook, Slack/Discord-compatible, and/or notify_email), returns request_id, and later an HMAC-signed POST to callback_url when they answer. Free watch-only logs a would_request for the weekly stuck report and sends nothing. We never solve CAPTCHAs and never ask for passwords.
cancel
cancel_request
Cancel a pending request (for example your agent got past the step another way). The link stops working and any unread code is wiped.
usage
usage_and_upgrade
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
weekly
weekly_report
Plain-English summary of the last 7 days: where your agent got stuck (by kind and by site), requests sent or that would have been, how many your person answered and how fast. Read-only; sends nothing. Needs a free API key.

Endpoints

URLTransportStateLatencyChecked
https://relay.cloudforbots.com/mcp streamable-http answering 49 ms 14 min ago

Alternatives to Human Handoff relay

same job, measured the same way
Repotector
by dir-ai

The repo guardian AI agents handshake with before they touch your code.

87 installs/wk local only
Prometheor
by prometheor

Your AI apps as one team: hand work to Codex, Claude Code or Cursor on your Mac, with a logbook.

answering
Reado
by watermelonbros

Your code review comments from Reado, the read-first IDE, as context and tools for your agent.

local only
xhostd
by xhostd

Agent-first hosting: create apps, push code, and deploy to HTTPS URLs from your coding agent.

answering
OTPilot
by otpilot

Use your OTPilot accounts (passwords, 2FA codes) to sign in and run commands, without seeing them.

94 installs/wk local only
codemcp
by stackunseen

Code mode for MCP: search, describe and execute over all your servers, with a sandbox and approvals.

804 installs/wk local only
ContinueWith
by continuewith-ai

Install the ContinueWith AI handoff widget from coding agents (Cursor, Claude Code, Codex).

49 installs/wk local only
Letmediff MCP
by letmediff

The official Letmediff MCP server helping you review your code with an agent first workflow

55 installs/wk local only

Human Handoff relay — questions

Answers built from our own checks of this server.

What can Human Handoff relay do?
It exposes 5 tools, read directly from the server on our last check. Among them: cancel_request, check_request, request_human, usage_and_upgrade, weekly_report. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Human Handoff relay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 44 of 92 checks got a reply (47.8%), average response time 348 ms. The bar chart above shows every period we have measured.
The registry lists Human Handoff relay as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Human Handoff relay?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Human Handoff relay need an API key?
No. Human Handoff relay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Human Handoff relay?
It answers our handshake in 348 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.