# Handoff Watch (remote · handoff.cloudforbots.com)

Spots stalled agent-to-agent tasks and nudges or reassigns them. Works beside Offhand.

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

## Components

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

## Channel facts

- Endpoint: `https://handoff.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 4 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 622 tokens (~155/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Handoff Watch MCP server?

Handoff Watch is a hosted endpoint at https://handoff.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-handoff 'https://handoff.cloudforbots.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-botrecipe-handoff": {
      "type": "http",
      "url": "https://handoff.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-16 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (4)

### `scan_handoffs` (~340 tokens)

Pass the tasks your agents handed each other (e.g. the result of Offhand list_todos) and get back which are stalled or failing and what to do. A task is stalled when it is claimed (in_progress) or handed over but untouched for stall_minutes, and failing when it is blocked or has failed fail_limit times. Ladder: nudge the assignee, nudge again, then reassign to a backup agent (or ask the person). Pro acts: records each nudge with a cooldown so nobody is pinged twice, and POSTs the nudge to the agent's webhook if you give one. Free watch-only takes no action and returns would_nudge / would_reassign. It never changes a task in Offhand itself and never takes a task another agent holds; reassigning returns an Offhand add_task call for your agent to make.

Input parameters:

- `backup_agent` (string): Default agent to hand stalled work to.
- `board` (string): A stable name for this task list, e.g. "offhand" or "team-ops". Cooldowns and the escalation ladder are tracked per board.
- `fail_limit` (integer): Failures before a task counts as failing. Default 2.
- `nudges_before_reassign` (integer): Nudges before suggesting a reassign. Default 2.
- `stall_minutes` (integer): Minutes without activity before a task counts as stalled. Default 60.
- `tasks` (array, required): Up to 200 tasks.
- `webhooks` (object): Optional map of agent name to an https URL that wakes it (Pro posts nudges there).

### `nudge_log` (~77 tokens)

List the latest nudges and reassigns (Pro) or would-nudges (free) for one board or all boards on your key.

Input parameters:

- `board` (string): A stable name for this task list, e.g. "offhand" or "team-ops". Cooldowns and the escalation ladder are tracked per board.

### `weekly_report` (~49 tokens)

Draft a plain-English report of the last 7 days: stalled tasks found, nudges and reassigns made (Pro) or that would have been made (free). Read-only; sends nothing.

### `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-handoff/handoff#diagnostics

## Score history

- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 65

## Common questions

### What is the Handoff Watch MCP server?

Handoff Watch is an MCP server listed in the public MCP registry as com.botrecipe/handoff. Spots stalled agent-to-agent tasks and nudges or reassigns them. Works beside Offhand. This page covers its hosted endpoint (https://handoff.cloudforbots.com/mcp).

### Is the Handoff Watch MCP server safe to use?

Handoff Watch scores 66 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 Handoff Watch MCP server expose?

Handoff Watch exposes 4 tools: scan_handoffs, nudge_log, weekly_report, usage_and_upgrade. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.

### Does the Handoff Watch MCP server require authentication?

No. We connected to Handoff Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Handoff Watch MCP server still maintained?

Handoff Watch 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://handoff.cloudforbots.com/mcp
- Website: https://handoff.cloudforbots.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-botrecipe-handoff/handoff.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-botrecipe-handoff/handoff.json
- HTML version of this page: https://verifymcp.io/servers/com-botrecipe-handoff/handoff