Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

handover.tools

by gammalandversion 1.1.0i★ –iRuns in the cloud
Registry nametools.handover/handover

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://handover.tools/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "handover": {
      "url": "https://handover.tools/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "handover": {
      "type": "http",
      "url": "https://handover.tools/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://handover.tools/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain handover.tools (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32680 servers in this category
  • Published to the registry more recently than 66% of the other 32680 servers in this category
  • Basic checks equal to or better than 100% of the other 32680 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is handover.tools safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 19 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

EmbeddedCI BenchPod

by embeddedci-com

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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-shotChannel
Use it forHanding over one piece of textSeveral rounds between two agents
EncryptionNone. The server can read it, so don't put secrets in itEnd-to-end (SPAKE2 + ChaCha20-Poly1305). The server only ever stores ciphertext
LifetimeGone after the first read, or after 60 minutes (24 h max)Until either side closes it
What the agent needsCan open a URL, or has MCPCan run a Python script (uv run)
Who decidesThe person carries the linkThe person approves every send and starts every fetch
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.
src/

entry.py routing, MCP (dual-era), content negotiation registry.py @tool decorator — one source for REST, MCP and discover tools/handoff.py, tools/channel.py the two tools guard.py quotas and the operator blocklist meter.py per-call metering page.py, docs.py, style.py the website and docs pages client/channel.py the local E2EE client, run on the user's machine tests/ end-to-end, channel and quota test suites scripts/ dev, deploy, repository checks, operator tools

Documentation

DocumentWhat it covers
docs/system-design.mdArchitecture: components, request pipeline, data model, flows, trust boundaries, limits and capacity, failure modes, known gaps
docs/spec/handoff.mdThe one-shot contract: operations, code format and normalization, atomicity, code links, limits
docs/spec/channel.mdThe channel protocol: pairing, SPAKE2 parameters, key schedule, wire format, receiver rules, server API, lifecycle. Detailed enough to write a second client
docs/decisions.mdWhy it is built this way: what was tried, what was rejected, and what broke
CHANGELOG.mdWhat changed, newest first. Also at handover.tools/changelog

The specs are the contract. A behavior change starts in the spec, then the code and tests follow.

Run it locally

Requires Node ≥ 22 and Python 3.12.

npm install

scripts/dev.sh # generates src/*_src.py and public/, then runs wrangler dev on :8787 tests/e2e.sh # end-to-end tests against the local server tests/channel.sh # two isolated clients: pairing, tampering, replay tests/quota.sh # quota gates (local only: edits counters directly) scripts/check.sh # repository rules: English only, every Dxx reference resolves

CI runs the check and the three suites on every push.

Deploy your own

  1. npx wrangler d1 create , then put the name and id into wrangler.toml.
  2. Change the routes pattern to your domain.
  3. CLOUDFLARE_API_TOKEN=… scripts/deploy.sh

Tables are created on the first request. scripts/block.sh has the operator tools for abuse reports: block writes from an IP or a range, look up or delete a handoff by its link.

Contributing and security

Issues and pull requests are welcome. AGENTS.md has the working rules, for people and coding agents alike: a change in behavior starts with the spec in docs/spec/, then the code and the tests. Report vulnerabilities privately: see SECURITY.md.

License

MIT. Fonts: Atkinson Hyperlegible, SIL OFL 1.1 (see assets/fonts/LICENSE.txt).

Ask PopNx