# Handover (remote · handover.sh)

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

- Trust score: 87/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `handover.sh`: 87/100 (this document), [markdown](https://verifymcp.io/servers/sh-handover-handover/api-mcp-2.md), [page](https://verifymcp.io/servers/sh-handover-handover/api-mcp-2)

## Channel facts

- Endpoint: `https://handover.sh/api/mcp?profile=core`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.18.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1457 tokens (~85/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Handover MCP server?

Handover is a hosted endpoint at https://handover.sh/api/mcp?profile=core, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "sh-handover-handover": {
      "type": "http",
      "url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sh-handover-handover]
url = "https://handover.sh/api/mcp?profile=core"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sh-handover-handover": {
      "type": "remote",
      "url": "https://handover.sh/api/mcp?profile=core",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sh-handover-handover --url 'https://handover.sh/api/mcp?profile=core' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sh-handover-handover:
    url: "https://handover.sh/api/mcp?profile=core"
```

### Netclaw

```json
{
  "McpServers": {
    "sh-handover-handover": {
      "Transport": "http",
      "Url": "https://handover.sh/api/mcp?profile=core"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sh-handover-handover -t streamable-http -u 'https://handover.sh/api/mcp?profile=core'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-03 (score 87, 0)

- [security] Stability: 0.97 → pass

### 2026-09-02 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-26 (score 83, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-24 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (17)

### `handover.whoami` (~41 tokens)

Verify the active identity

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` (~72 tokens)

Search handovers

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

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `mode` (string)
- `query` (string)
- `status` (string)

### `handover.get` (~74 tokens)

Inspect a handover

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

Input parameters:

- `handoverId` (string, required): Handover identifier returned by handover.search or handover.create.
- `revisionId` (string): Optional immutable revision; omit to inspect the current revision.

### `handover.read_artifact` (~73 tokens)

Read a handover 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.

Input parameters:

- `artifactId` (string, required): Artifact identifier returned by handover.get.
- `maxBytes` (integer): Maximum decoded bytes to return before reporting truncation.

### `handover.thread` (~44 tokens)

Read a handover discussion

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

Input parameters:

- `handoverId` (string, required): Handover whose discussion and assignments should be read.

### `handover.annotations` (~81 tokens)

Read artifact annotations

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

Input parameters:

- `artifactId` (string)
- `handoverId` (string, required): Handover whose annotation threads should be read.
- `revisionId` (string)
- `status` (string)

### `handover.create` (~105 tokens)

Create a handover

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

Input parameters:

- `artifacts` (array): Files attached to the initial immutable revision.
- `brief` (object): Structured continuation brief for humans and agents.
- `note` (string): Free-form continuation note recorded in the initial revision.
- `summary` (string): Concise explanation of what this handover contains.
- `title` (string, required): Short, specific name for the durable context.

### `handover.continue` (~128 tokens)

Continue a handover

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.

Input parameters:

- `artifacts` (array): New or replacement files; omitted files remain inherited.
- `brief` (object): Updated structured continuation brief.
- `expectedRevisionId` (string, required): Current revision ID returned by handover.get; prevents lost updates.
- `handoverId` (string, required): Handover to continue after reading its current snapshot.
- `note` (string): What changed or what the next collaborator should know.

### `handover.comment` (~69 tokens)

Comment on a handover

Append a discussion comment and optionally notify explicitly mentioned collaborators.

Input parameters:

- `body` (string, required): Comment body in plain text or Markdown.
- `handoverId` (string, required): Handover discussion to append the comment to.
- `mentionPrincipalIds` (array): Collaborator principal IDs to mention and notify.

### `handover.annotate` (~103 tokens)

Annotate a handover artifact

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.

Input parameters:

- `body` (string, required): Actionable annotation body in plain text or Markdown.
- `handoverId` (string, required): Handover containing the artifact being annotated.
- `mentionPrincipalIds` (array): Collaborator principal IDs to mention and notify.
- `target` (object, required): Immutable artifact location to anchor this annotation.

### `handover.update_comment` (~146 tokens)

Edit or resolve a comment

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

Input parameters:

- `body` (string): Replacement comment body; omit to preserve the current body.
- `commentId` (string, required): Comment or annotation to edit, resolve, or reopen.
- `handoverId` (string, required): Handover containing the comment.
- `mentionPrincipalIds` (array): Replacement collaborator mentions.
- `resolvedRevisionId`: Revision that addressed the feedback, or null when reopening.
- `status` (string): Open, resolve, or reopen the feedback thread.
- `target`: Replacement annotation target, or null to remove the anchor.

### `handover.assign` (~65 tokens)

Set handover owners

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

Input parameters:

- `handoverId` (string, required): Handover whose open assignments will be replaced.
- `principalIds` (array, required): Complete replacement list of assigned collaborator principal IDs.

### `handover.publish` (~128 tokens)

Publish a handover as a report

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

Input parameters:

- `access` (string): Who can open the report URL.
- `entryPath` (string): Artifact path opened first when readers visit the report.
- `handoverId` (string, required): Handover to project as a stable report.
- `revisionId` (string): Revision to pin; used when revisionMode is pinned.
- `revisionMode` (string): Follow new revisions automatically or keep one revision pinned.
- `slug` (string): Stable URL slug; generated from the title when omitted.

### `handover.publication` (~58 tokens)

Inspect a published report

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

Input parameters:

- `handoverId` (string): Handover whose publication should be inspected.
- `slug` (string): Stable published report slug.

### `handover.pull` (~78 tokens)

Pull a published report

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

Input parameters:

- `files` (array): Optional relative paths to return; omit for every file.
- `includeBinary` (boolean): Return binary files as base64 when true.
- `slug` (string, required): Stable published report slug.

### `handover.okf.export` (~61 tokens)

Export a handover as OKF

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

Input parameters:

- `handoverId` (string, required): Handover to export.
- `revisionId` (string): Immutable revision to export; defaults to the current revision.

### `handover.okf.import` (~100 tokens)

Import an OKF bundle

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

Input parameters:

- `expectedRevisionId` (string): Current revision ID used to prevent conflicting imports.
- `files` (array, required): Files from an Open Knowledge Format bundle.
- `handoverId` (string, required): Existing handover that will receive the imported bundle.
- `mode` (string): Merge bundle files with inherited artifacts or replace them.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sh-handover-handover/api-mcp-2#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 87
- 2026-09-18: 87
- 2026-09-17: 87
- 2026-09-16: 87
- 2026-09-15: 87
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 87
- 2026-09-11: 87
- 2026-09-10: 87
- 2026-09-09: 87
- 2026-09-08: 87
- 2026-09-07: 87
- 2026-09-06: 87
- 2026-09-05: 87
- 2026-09-04: 87
- 2026-09-03: 87
- 2026-09-02: 87
- 2026-09-01: 86
- 2026-08-31: 86
- 2026-08-30: 85
- 2026-08-29: 85
- 2026-08-28: 84
- 2026-08-27: 84
- 2026-08-26: 83
- 2026-08-25: 82
- 2026-08-24: 82
- 2026-08-23: 81

## Common questions

### What is the Handover MCP server?

Handover is an MCP server listed in the public MCP registry as sh.handover/handover. Shared, versioned context that humans and AI agents can publish, review, annotate, and continue. This page covers its hosted endpoint (https://handover.sh/api/mcp?profile=core).

### Is the Handover MCP server safe to use?

Handover scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Handover MCP server expose?

Handover exposes 17 tools: handover.whoami, handover.search, handover.get, handover.read_artifact, handover.thread, and 12 more. Their descriptions and schemas cost roughly 1,426 tokens of context every time the server is loaded.

### Does the Handover MCP server require authentication?

Yes. Handover asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Handover MCP server still maintained?

Handover is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://handover.sh/api/mcp?profile=core
- Repository: https://github.com/44-pixels/handover-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sh-handover-handover/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/sh-handover-handover/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/sh-handover-handover/api-mcp-2