Koskamo

Human Handoff relay MCP

A human-in-the-loop relay for AI agents that handles CAPTCHAs, 2FA codes, approvals, and sign-ins by handing blocked steps to a human via a one-tap link, then relaying the answer back to the agent securely.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Human Handoff relay MCP logo, by Cloud for BotsVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-17Operated by Cloud for Bots
MCP endpoint (Streamable HTTP)
https://relay.cloudforbots.com/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 0 of 5 declare behavior hints · 1 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to botrecipe.com ·
  • Passed Endpoint and vendor documentation share a domain
  • Uptime 100% over 90 days
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Hand CAPTCHAs or 2FA codes to a human for resolution
  • Relay approval or sign-in actions from agent to human
  • Poll for request status and receive single-read 2FA codes
  • View weekly reports on agent stuck points

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
human-handoff 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Human-in-the-loop relay for AI agents. When your agent hits a CAPTCHA, a 2FA code, an approval or a sign-in it should not do alone, it calls request_human; your person gets a one-tap link, solves it in their own browser or pastes the code, and the answer comes back to your agent. Codes are read once and wiped in 10 minutes. We never solve CAPTCHAs and never ask for passwords. Free 500 calls/day, then $9/month. No model inside: bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

Tools

5 advertised

request_human
Advertised by the server during the last successful anonymous check.

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.

request_human input schema
{
  "type": "object",
  "required": [
    "kind",
    "step"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The page the person should open, if any (https)."
    },
    "kind": {
      "enum": [
        "captcha",
        "2fa_code",
        "approve",
        "login"
      ],
      "type": "string",
      "description": "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)."
    },
    "step": {
      "type": "string",
      "description": "One plain sentence for the person, e.g. \"Paste the 6-digit code GitHub just texted you\"."
    },
    "agent": {
      "type": "string",
      "description": "Your agent's name, shown to the person."
    },
    "callback_url": {
      "type": "string",
      "description": "Pro: public https URL we POST the answer to, signed with X-Relay-Signature = hex HMAC-SHA256(callback_secret, timestamp + \".\" + body)."
    },
    "notify_email": {
      "type": "string",
      "description": "Pro: email address to send the one-tap link to."
    },
    "notify_webhook": {
      "type": "string",
      "description": "Pro: public https URL we POST {text, human_url} to (Slack/Discord incoming webhooks work)."
    },
    "timeout_minutes": {
      "type": "integer",
      "description": "How long the person has, 1-1440. Default 30."
    }
  }
}
check_request
Advertised by the server during the last successful anonymous check.

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.

check_request input schema
{
  "type": "object",
  "required": [
    "request_id"
  ],
  "properties": {
    "request_id": {
      "type": "string"
    }
  }
}
cancel_request
Advertised by the server during the last successful anonymous check.

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

cancel_request input schema
{
  "type": "object",
  "required": [
    "request_id"
  ],
  "properties": {
    "request_id": {
      "type": "string"
    }
  }
}
weekly_report
Advertised by the server during the last successful anonymous check.

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.

weekly_report input schema
{
  "type": "object",
  "properties": {}
}
usage_and_upgrade
Advertised by the server during the last successful anonymous check.

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

usage_and_upgrade input schema
{
  "type": "object",
  "properties": {}
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

100% (17 of 17 checks answered)

  1. 2026-11-18: 5 of 5 checks answered
  2. 2026-11-19: 4 of 4 checks answered
  3. 2026-11-20: 3 of 3 checks answered
  4. 2026-11-21: 4 of 4 checks answered
  5. 2026-11-22: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
433 ms
95th percentile latency
433 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 433 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http human-handoff-relay-mcp https://relay.cloudforbots.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add human-handoff-relay-mcp --url https://relay.cloudforbots.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable human-handoff-relay-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "human-handoff-relay-mcp": {
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "human-handoff-relay-mcp": {
      "type": "streamableHttp",
      "url": "https://relay.cloudforbots.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start human-handoff-relay-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "human-handoff-relay-mcp": {
      "type": "http",
      "url": "https://relay.cloudforbots.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http human-handoff-relay-mcp https://relay.cloudforbots.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://relay.cloudforbots.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "human-handoff-relay-mcp": {
      "serverUrl": "https://relay.cloudforbots.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Human Handoff relay MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Human Handoff relay MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing