# Human Handoff relay (remote · relay.cloudforbots.com)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `relay.cloudforbots.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-botrecipe-relay/relay.md), [page](https://verifymcp.io/servers/com-botrecipe-relay/relay)

## Channel facts

- Endpoint: `https://relay.cloudforbots.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-botrecipe-relay 'https://relay.cloudforbots.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-botrecipe-relay": {
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-botrecipe-relay": {
      "type": "http",
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-botrecipe-relay]
url = "https://relay.cloudforbots.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-botrecipe-relay": {
      "type": "remote",
      "url": "https://relay.cloudforbots.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-botrecipe-relay --url 'https://relay.cloudforbots.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-botrecipe-relay:
    url: "https://relay.cloudforbots.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-botrecipe-relay": {
      "Transport": "http",
      "Url": "https://relay.cloudforbots.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-botrecipe-relay -t streamable-http -u 'https://relay.cloudforbots.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-botrecipe-relay": {
      "type": "http",
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 65)

First indexed and scored.

## MCP tools (5)

### `request_human` (~343 tokens)

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.

Input parameters:

- `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, required): 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, required): 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).

### `check_request` (~68 tokens)

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.

Input parameters:

- `request_id` (string, required)

### `cancel_request` (~43 tokens)

Cancel a pending request (for example your agent got past the step another way). The link stops working and any unread code is wiped.

Input parameters:

- `request_id` (string, required)

### `weekly_report` (~59 tokens)

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.

### `usage_and_upgrade` (~37 tokens)

Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-botrecipe-relay/relay#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://relay.cloudforbots.com/mcp
- Website: https://relay.cloudforbots.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-botrecipe-relay/relay.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-botrecipe-relay/relay.json
- HTML version of this page: https://verifymcp.io/servers/com-botrecipe-relay/relay