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
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Handover

by 44-pixelsversion 1.18.0i★ –iRuns in the cloud
Registry namesh.handover/handover

Install

Overview

Description from the maker (original English)

Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.

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.sh/api/mcp?profile=core

Run this in your terminal

claude mcp add --transport http handover 'https://handover.sh/api/mcp?profile=core'

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.sh/api/mcp?profile=core"
    }
  }
}

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.sh/api/mcp?profile=core"
    }
  }
}

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.sh/api/mcp?profile=core

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.sh (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 21% 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 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.18.0) reached the registry 3 months 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 MCP

Move active work between Claude Code, Codex, Cursor, Gemini CLI, people, and service agents without losing decisions, files, history, or authorship.

Handover provides shared, versioned context for humans and AI agents through a hosted Model Context Protocol server, a dependency-free CLI, and eight open Agent Skills. This repository is the public source, discovery, installation, and connection record for those interfaces.

Research and evidence

The Handover research and evidence index collects the open continuity benchmark, Reporter migration field report, Handoff Continuity Record, and runnable continuation demo. Findings stay beside their methods, source artifacts, first-party relationship, and material limitations.

The versioned research/v1/ package gives agents and researchers a stable JSON index, JSON Schema, citation metadata, and a bounded Markdown summary. The package is a first-party publication by Handover and 44pixels; it is designed for inspection and reuse, not presented as independent validation.

See a complete handoff

The public continuation demo shows the same workflow from both sides: an interactive human view and an agent-readable record. It includes Markdown, SQL, JSON, a visual artifact, three attributable revisions, a human review note, and the next agent's resolution. No account is required.

Build a private handoff prompt

The AI handoff prompt generator turns unfinished work into separate capture and receiver prompts without requiring an account. Draft fields stay inside the browser tab and are not sent to analytics or stored as a server-side draft.

The receiver prompt requires the next actor to inspect the evidence, separate verified and unverified state, identify blockers, and state one bounded next action before continuing. Copy or download the Markdown record, or carry the same private draft into a prefilled first handover.

Move from Claude Code to Codex

Codex's built-in import is the right first choice for a one-time move of supported Claude Code setup, projects, memories, and recent chats. Use Handover when Claude Code and Codex will alternate on unfinished work and need shared artifacts, separate identities, review, and revision history.

The Claude Code to Codex transfer recipe contains the exact sender checkpoint, two-host service-credential setup, receiver verification, optimistic-concurrency continuation, revocation test, and pass criteria. The rendered guide explains when to use native import and when to use a durable handoff.

Run the reviewed MCP handoff

The demo shows the finished record. The end-to-end MCP handoff procedure tests the workflow itself across separate authenticated identities:

  1. verify the publisher;
  2. publish Markdown, SQL, and JSON;
  3. read every artifact back;
  4. review exact evidence from another identity;
  5. publish a correction with optimistic concurrency;
  6. resolve the finding against the correcting revision; and
  7. prove a fresh successor can continue without the original chat.

It also exercises denied, read-only, stale-revision, and revoked-credential paths. Use the rendered guide for the rationale, or connect an agent through the install flow before running the repository procedure.

Use the AI agent handoff checklist

For a smaller local handoff, start with the Markdown checklist. It captures the objective, current state, decisions, evidence, constraints, next action, and ownership, then requires the receiving actor to read the current revision, open the evidence, reproduce one meaningful result, and mark the handoff as passed or blocked.

The rendered checklist and FAQ explains each verification step. The raw template works without Handover; use the hosted service when multiple actors need authenticated access, immutable revisions, search, annotations, or auditable ownership.

Test company AI context readiness

Before connecting company knowledge to several people and agents, use the company AI context readiness checklist. It separates approved source knowledge from changing continuation records, inventories human and service identities, declares company and workspace boundaries, and finishes with a two-person, two-agent pilot.

The pilot is intentionally stricter than an import count: it verifies authorized retrieval, attributable revisions, human review, denied searches, agent revocation, and fresh-session continuation. The source-linked architecture guide explains why a search index, private model memory, and canonical company records have different responsibilities.

Use the open handoff format

The Handoff Continuity Record is a platform-neutral JSON format for the state another human or AI agent needs to verify and continue work. It records the objective, verified and unverified state, decisions, evidence, constraints, next action, ownership, and open review without prescribing transport, routing, authentication, or storage.

The protocol/v1/ directory contains:

  • a JSON Schema Draft 2020-12 contract;
  • a valid inventory-reporting example;
  • a dependency-free Node.js conformance checker; and
  • producer, receiver, scope, and security requirements.
node protocol/v1/validate.mjs protocol/v1/example.json

MCP can expose the tools used to read and write the record. A2A or an orchestration framework can route it. Git or Handover can store it.

Connect

The canonical Streamable HTTP endpoint is:

https://handover.sh/api/mcp?profile=core

The recommended core profile exposes 17 tools for everyday identity, search, retrieval, review, continuation, publishing, and portability workflows. Use https://handover.sh/api/mcp?profile=native for all 27 first-party Handover operations. The unparameterized https://handover.sh/api/mcp endpoint retains all 55 tools and Reporter aliases for existing integrations.

The endpoint exposes its MCP handshake and tool schemas without an account so clients and directories can verify compatibility before connecting. Tool calls remain protected and return Handover's OAuth resource challenge when no valid human or service credential is present.

Interactive MCP hosts use Handover's first-party OAuth flow: standard discovery, dynamic client registration, PKCE, short-lived access tokens, and rotating refresh tokens. The host opens Handover in a browser; sign in as yourself, review the requested permissions, and approve the connection. Handover records your human identity on every attributable action.

Unattended runners and hosts without OAuth support use a separately named, scoped service credential created under Workspace or Company -> Agents. Human and service identities remain independently attributable and revocable.

For the complete setup, identity check, two-agent continuity test, and troubleshooting flow, see CONNECTING.md.

Codex
codex mcp add handover --url https://handover.sh/api/mcp?profile=core

codex mcp login handover

Claude Code
claude mcp add --transport http --scope user \

handover https://handover.sh/api/mcp?profile=core

Gemini CLI
gemini mcp add --transport http --scope user \

handover https://handover.sh/api/mcp?profile=core

Cursor

Add this to .cursor/mcp.json. Cursor discovers Handover's authorization server and prompts for browser sign-in when the connection starts:

{

"mcpServers": { "handover": { "url": "https://handover.sh/api/mcp?profile=core" } } }

Cline

Open Cline's MCP wizard:

cline mcp install handover --transport http https://handover.sh/api/mcp?profile=core

Choose Remote (HTTP) and Static headers, then enter the scoped service agent credential in Cline's private header prompt. The agent-readable llms-install.md includes the exact configuration, identity check, safe first write, two-agent continuation test, and revocation procedure. Use the first-party Cline setup page for the complete Handover flow. Do not paste a real credential into chat or commit Cline's private MCP settings.

Command-line client

The dependency-free Handover CLI supports the same durable workflow from a terminal:

npm install --global handover-sh

handover login handover doctor handover search "billing migration" handover pull --out ./continued-work handover publish ./report --title "Weekly report"

The published package source and metadata live in cli/. The audited dire

Only the beginning is shown; read the rest in the repo

Ask PopNx