Skip to content
Handover logo

Handover MCP server

Which servers in the official MCP registry are Handover's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Handover

Whose server it is
  • Registry namesh.handover/handoververified in the MCP registry

The registry name sits under handover.sh. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools17
  • Server calls itselfhandover
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 260 ms.

Tools it offers17 tools · read 2026-10-13
  • handover.whoami

    Return the authenticated person or service agent, organization, workspace, role, and granted scopes. Call this before reading or publishing to confirm attribution and tenancy.

  • handover.search

    Find current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content. Use an empty query to list recent handovers.

  • handover.get

    Read a handover snapshot, continuation brief, artifact metadata, and revision history. Omit revisionId for the current snapshot.

  • handover.read_artifact

    Read bounded artifact content after inspecting a handover. Text is returned as UTF-8 and binary content as base64; truncated results report that explicitly.

  • handover.thread

    Read comments, explicit mentions, assignments, and eligible collaborators without changing revision history.

  • handover.annotations

    Read revision-anchored file comments, selected text, status, authorship, and resolution metadata. Use status=open to find feedback that still needs action.

  • handover.create

    Create durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.

  • handover.continue

    Append an immutable revision after reading the current snapshot. expectedRevisionId is mandatory to prevent overwriting another collaborator's work. Omitted artifacts are inherited; matching names are replaced.

  • handover.comment

    Append a discussion comment and optionally notify explicitly mentioned collaborators.

  • handover.annotate

    Add a durable comment anchored to selected text or lines in an immutable artifact revision. Read the artifact first and preserve the exact quote and surrounding context.

  • handover.update_comment

    Edit an authored comment, or resolve/reopen an annotation. Set resolvedRevisionId when a new handover revision addressed the feedback.

  • handover.assign

    Replace the open assignments with the supplied collaborator identities. This changes collaboration state, not the immutable handover revision.

  • handover.publish

    Create or update a stable /r/{slug}/ report projection of a Handover revision.

  • handover.publication

    Read the stable report URL, entry file, access mode, and selected revision for a handover.

  • handover.pull

    Return the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.

  • handover.okf.export

    Export a handover revision as an Open Knowledge Format bundle for another human or agent system.

  • handover.okf.import

    Import Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

OpenAPI spec

49 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.