Agents Index

handover.tools

Online

Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel.

Visit publisherConnectJSON

What it can do: 9 tools

  • handoff_putStore a piece of context and get back a short code. The person gives the link handover.tools/<code> to an agent on another device and it can fetch the content — no copy-paste of long text. The code is 8 letters, easy to
  • handoff_getFetch content stored by handoff_put using its 8-character code. The code is case-insensitive and hyphens are ignored, so 'kvmtrhxp' and 'KVMT-RHXP' are the same; the person may give it as a link like handover.tools/kvmtr
  • handoff_revokeDestroy content stored by handoff_put right now, before its TTL runs out and whether or not it has been fetched. Requires the revoke_key returned by handoff_put — the person fetching with the short code cannot revoke, on
  • channel_openStart pairing two agents on different machines for a multi-round exchange (e.g. one explores, the other studies and asks follow-up questions). Use the local client at https://handover.tools/client/channel.py — do not cal
  • channel_joinSecond half of pairing, run by the local client at https://handover.tools/client/channel.py. Send only the first 3 characters of the spoken code (the nameplate) plus this side's SPAKE2 message; the other 5 characters are
  • channel_sendRelay one ciphertext to the other side of a paired channel. The ciphertext must come from the local client at https://handover.tools/client/channel.py; do not call this by hand, and never base64-encode plaintext into it
  • channel_fetchUse the local client at https://handover.tools/client/channel.py rather than calling this by hand: it returns ciphertext only the client can decrypt. Returns the peer's messages this side has not fetched yet. Call only w
  • channel_ackUse the local client at https://handover.tools/client/channel.py rather than calling this by hand. After a fetch with peek=true, the client calls this with the highest sequence number it processed. That is what the peer
  • channel_closeEither side can close. Deletes the channel, both keys, and every stored message immediately. The other side's next fetch reports not_found_or_closed.

Connect it

Claude Code
claude mcp add --transport http handover-tools https://handover.tools/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://handover.tools/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "handover-tools": {
      "url": "https://handover.tools/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "handover-tools": {
      "type": "http",
      "url": "https://handover.tools/mcp"
    }
  }
}

Questions

What does handover.tools do?

Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel. It exposes 9 tools to AI assistants.

What tools does handover.tools provide?

9 tools, including handoff_put, handoff_get, handoff_revoke, channel_open, channel_join, channel_send, channel_fetch, channel_ack, channel_close.

How do I connect handover.tools to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://handover.tools/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does handover.tools require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is handover.tools online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes handover.tools?

handover.tools. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Agents & Orchestration