Human Handoff relay
REMOTE · RELAY.CLOUDFORBOTS.COM
Hands CAPTCHAs, 2FA codes and approvals from your agent to your human with one tap.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 681 tokens (~136/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://relay.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=relay.cloudforbots.com | CN=YR2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 59e225e1bc2cc30eab604d1217c826ee0bf |
| SANs: relay.cloudforbots.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of relay.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://relay.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://relay.cloudforbots.com/mcp | HTTPS enforced | 308 | https://relay.cloudforbots.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_request ~43
Cancel a pending request (for example your agent got past the step another way). The link stops working and any unread code is wiped.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
check_request ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
request_human ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Your agent's name, shown to the person. |
| callback_url | string | – | Pro: public https URL we POST the answer to, signed with X-Relay-Signature = hex HMAC-SHA256(callback_secret, timestamp + "." + body). |
| kind | string | yes | captcha (person solves it in their browser), 2fa_code (person pastes the code; you read it once), approve (yes/no), login (person signs in, then taps done). |
| notify_email | string | – | Pro: email address to send the one-tap link to. |
| notify_webhook | string | – | Pro: public https URL we POST {text, human_url} to (Slack/Discord incoming webhooks work). |
| step | string | yes | One plain sentence for the person, e.g. "Paste the 6-digit code GitHub just texted you". |
| timeout_minutes | integer | – | How long the person has, 1-1440. Default 30. |
| url | string | – | The page the person should open, if any (https). |
No output schema declared.
No examples provided.
usage_and_upgrade ~37
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Human Handoff relay MCP server?
Human Handoff relay is a hosted endpoint at https://relay.cloudforbots.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · relay.cloudforbots.com
claude mcp add --transport http com-botrecipe-relay 'https://relay.cloudforbots.com/mcp'
What is the Human Handoff relay MCP server?
Human Handoff relay is an MCP server listed in the public MCP registry as com.botrecipe/relay. Hands CAPTCHAs, 2FA codes and approvals from your agent to your human with one tap. This page covers its hosted endpoint (https://relay.cloudforbots.com/mcp).
Is the Human Handoff relay MCP server safe to use?
Human Handoff relay scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Human Handoff relay MCP server expose?
Human Handoff relay exposes 5 tools: request_human, check_request, cancel_request, weekly_report, usage_and_upgrade. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.
Does the Human Handoff relay MCP server require authentication?
No. We connected to Human Handoff relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Human Handoff relay MCP server still maintained?
Human Handoff relay is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.