Handoff Watch
REMOTE · HANDOFF.CLOUDFORBOTS.COM
Spots stalled agent-to-agent tasks and nudges or reassigns them. Works beside Offhand.
Available components
Last scanned (6 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Workflow Automation
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 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. 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 Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 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://handoff.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=handoff.cloudforbots.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 509999d189b00eb9b23d3daff01792691fd |
| SANs: handoff.cloudforbots.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 handoff.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://handoff.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://handoff.cloudforbots.com/mcp | HTTPS enforced | 308 | https://handoff.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 →
nudge_log ~77
List the latest nudges and reassigns (Pro) or would-nudges (free) for one board or all boards on your key.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | A stable name for this task list, e.g. "offhand" or "team-ops". Cooldowns and the escalation ladder are tracked per board. |
No output schema declared.
No examples provided.
scan_handoffs ~340
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Up to 200 tasks. |
| webhooks | object | – | Optional map of agent name to an https URL that wakes it (Pro posts nudges there). |
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 ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · handoff.cloudforbots.com
claude mcp add --transport http com-botrecipe-handoff 'https://handoff.cloudforbots.com/mcp'
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.