MCP.Market

handover.tools MCP server

online · 100% uptime
by handover.tools·tools.handover/handover·v1.1.0

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

B71/100grade B
What users say
No reviews yet
Be the first
Safety scan
B71/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed handover.tools yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

handover.tools tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How handover.tools compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 36% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
2,350 ms
faster than 4% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-09, latest 2026-10-19, typically one every 10 days.

Install handover.tools in Claude Code, Cursor or VS Code

claude mcp add --transport http handover https://handover.tools/mcp
Add to Cursor

What the publisher says

From the handover.tools repository's README, as published. We do not edit it. Read it on GitHub

handover.tools

One agent writes it, another agent reads it. You only carry an 8-letter link between them.

handover.tools moves a piece of work from one AI agent to another: across devices, across vendors, or to another person. Brainstorm with the agent on your phone, then say "hand this over with handover.tools". Paste the link it gives you (handover.tools/kvmtrhxp) into Claude Code on your laptop, and that agent picks the work up where your documents already are.

Bring the idea to your context, not your context to the idea.

There is no account and nothing to install. Any agent that can open a web page can use it.

Two modes

One-shot

curl -X POST https://handover.tools/api/handoff/put \
     -H 'Content-Type: application/json' \
     -d '{"content":"...","label":"notes"}'          # → {"code":"kvmtrhxp", "revoke_key":"...", ...}
curl "https://handover.tools/api/handoff/get?code=kvmtrhxp"

Opening handover.tools/ doesn't use up the code. That URL returns instructions, and the actual read is a second request. Link previews in Slack or iMessage therefore don't burn the content before the recipient sees it.

Channel

curl -so ~/.handoff/channel.py --create-dirs https://handover.tools/client/channel.py
uv run ~/.handoff/channel.py open --name study --brief "..."   # machine A: prints a code
uv run ~/.handoff/channel.py join kvmtrhxp --name study        # machine B
uv run ~/.handoff/channel.py send --name study --kind question --file q.md
uv run ~/.handoff/channel.py fetch --name study

The 8 letters are a 3-letter nameplate, which the server sees and uses to find the channel, plus a 5-letter password that is generated on machine A and never uploaded. The password goes into SPAKE2, the same construction magic-wormhole uses. The server never learns the password, so it cannot impersonate either side. /client/channel.py is served from client/channel.py, and its sha256 is published at /api/discover, so you can check that the client you downloaded matches this repository.

The threat model, including what we don't claim, is at handover.tools/security.

For agents

  • MCP endpoint: https://handover.tools/mcp. It serves both the 2026-07-28 (modern) and 2025-11-25 and earlier (legacy) protocol eras.
  • Plain text instructions: /llms.txt, /guide.md, /security.md
  • Full REST schema: /api/discover

How it's built

  • Cloudflare Python Workers + D1. One Worker, no other infrastructure. The routes, the MCP tools/list and /api/discover are all derived from a single tool registry (src/registry.py), so they can't drift apart.
  • Limits are layered: 10 writes and 200 calls per caller per day, plus a global daily cap. The site runs on the Workers Free plan, which makes $0 the hard spending ceiling.
  • Fonts are self-hosted and embedded in the Worker, so no visitor IP goes to a third party. Caller IPs are erased after 30 days.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

handover.tools: common questions

Is handover.tools MCP server safe?
Mostly: it is graded B (71/100). Read the handover.tools safety report
How do I install handover.tools?
It runs remotely at handover.tools. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does handover.tools need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is handover.tools maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v1.1.0.
Is handover.tools up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does handover.tools compare with other MCP servers?
safety score 71/100 (higher than 36% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 2,350 ms (faster than 4% of 30,031 servers). Full comparison.