← All launches
0 Report

handover.tools

by FastDrop

MCP Verified 2 days ago Registry import free

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

Share

Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel. Official MCP Registry: tools.handover/handover@1.0.0. Remote endpoint: https://handover.tools/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as tools.handover/handover and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 9 Oct 2026. Not supplied by the maker.

  • handoff_put

    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

  • handoff_get

    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

  • handoff_revoke

    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 co

  • channel_open

    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/cha

  • channel_join

    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 ot

  • channel_send

    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-encod

  • channel_fetch

    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 fetc

  • channel_close

    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.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.