Skip to content

Handoff Watch MCP server

com.botrecipe/handoffbotrecipe.comstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Handoff Watch MCP server can do

The Handoff Watch MCP server is published by botrecipe.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: scan_handoffs and weekly_report), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (scan_handoffs).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • scan_handoffsPass the tasks your agents handed each other (e.g.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.webhooks): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • weekly_reportDraft a plain-English report of the last 7 days: stalled tasks found, nudges and reassigns made (Pro) or that would have been made (free).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • nudge_logList the latest nudges and reassigns (Pro) or would-nudges (free) for one board or all boards on your key.No findings

    Why it is in this group

    • The name "nudge_log" says "log": a word for reading.
    Description, as the server wrote it
    List the latest nudges and reassigns (Pro) or would-nudges (free) for one board or all boards on your key.
  • usage_and_upgradeShow today's usage for your key or IP and the $9/month upgrade link.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://handoff.cloudforbots.com/mcp: tools/list returned 4 tools to an anonymous client, including scan_handoffs (write), weekly_report (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http handoff https://handoff.cloudforbots.com/mcp
claude mcp add --transport http handoff https://handoff.cloudforbots.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__handoff__nudge_log",
      "mcp__handoff__usage_and_upgrade"
    ],
    "ask": [
      "mcp__handoff__scan_handoffs",
      "mcp__handoff__weekly_report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as handoff. Review it before you use it.

Capability tags behind 1 rule
  • mcp__handoff__scan_handoffs outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.botrecipe/handoff/verify?hash=b934bd0e8845d7c16cd9e9a073dfdc69b23523873695e0e9e490b47362bf682d" | jq -e '.changed == false'

Pinned hash b934bd0e8845, from Nov 17, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.botrecipe/handoff/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.botrecipe/handoff
[![Anlyon Radar](https://radar.anlyon.com/badge/com.botrecipe/handoff.svg)](https://radar.anlyon.com/servers/com.botrecipe/handoff)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

Handoff Watch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Handoff Watch MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Handoff Watch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Handoff Watch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Handoff Watch MCP server have?

4 tools: 2 write, 2 read. scan_handoffs, weekly_report, nudge_log and usage_and_upgrade.

Does the Handoff Watch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Handoff Watch MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_handoffs.

Has the Handoff Watch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.