{"id":"tools.handover/handover","slug":"tools-handover-handover","title":"handover.tools","description":"Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel.","version":"1.1.0","publisher":{"kind":"domain","id":"handover.tools","label":"handover.tools","url":"https://handover.tools"},"website":"https://handover.tools","repository":"https://github.com/gammaland/handover","remotes":[{"type":"streamable-http","url":"https://handover.tools/mcp"}],"packages":[],"published":"2026-10-19","updated":"2026-10-19","status":"online","auth":"","latency_ms":1215,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"handoff_put","title":"Hand off context to another device","description":"Store 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 type on a phone. NOT ENCRYPTED: the server can read what you store, so never put credentials, tokens, or private data in it, and ask the person before storing an employer's or clie","read_only":false},{"name":"handoff_get","title":"Fetch context handed off from another device","description":"Fetch 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/kvmtrhxp, and passing that is fine too. Return the content to the person verbatim and complete: it can be fetched only once. If the code is unknown, already fetched, or expired, content","read_only":false},{"name":"handoff_revoke","title":"Destroy handed-off content immediately","description":"Destroy 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, only the writer can. Use this the moment someone says they sent the wrong thing, or changed their mind. Revoking an already gone item is not an error: the outcome is reported as 'alr","read_only":false},{"name":"channel_open","title":"Open an end-to-end encrypted channel to an agent on another machine","description":"Start 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 call this by hand. The client generates a secret password locally, and this call returns only a 3-character nameplate; the person gives nameplate + password (8 letters) to the other m","read_only":false},{"name":"channel_join","title":"Join a channel with the code from the other machine","description":"Second 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 the password and must never be sent to the server. The nameplate is consumed on success. Returns this side's key and the peer's SPAKE2 message. Unknown, used, or expired nameplate","read_only":false},{"name":"channel_send","title":"Send one encrypted message to the paired agent","description":"Relay 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 (that is rejected). Only send after the person has seen and approved the draft — the server cannot enforce this, the calling agent must. Returns the message's sequence number and h","read_only":false},{"name":"channel_fetch","title":"Fetch unread encrypted messages from the paired agent","description":"Use 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 when the person asks. Clients fetch with peek=true, which marks nothing, and then call channel_ack once they have processed the messages; without peek, the messages are marked read ","read_only":false},{"name":"channel_ack","title":"Acknowledge the paired agent's messages after processing them","description":"Use 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 sees as read, so a response lost in transit never turns into a false read receipt. The cursor never moves back or past the last stored message; calling again with the same seq chan","read_only":false},{"name":"channel_close","title":"Close a channel and delete its messages","description":"Either side can close. Deletes the channel, both keys, and every stored message immediately. The other side's next fetch reports not_found_or_closed.","read_only":false}],"server_info":{"name":"handover.tools","version":"1.0.0"},"category":"agents","tags":[],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-09","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/tools-handover-handover/"}