Handover
REMOTE · HANDOVER.SH · SCANNED SEP 21
Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.
Available components
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1457 tokens (~85/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · handover.sh
claude mcp add --transport http sh-handover-handover 'https://handover.sh/api/mcp?profile=core'
{
"mcpServers": {
"sh-handover-handover": {
"url": "https://handover.sh/api/mcp?profile=core"
}
}
} {
"servers": {
"sh-handover-handover": {
"type": "http",
"url": "https://handover.sh/api/mcp?profile=core"
}
}
} [mcp_servers.sh-handover-handover] url = "https://handover.sh/api/mcp?profile=core"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sh-handover-handover": {
"type": "remote",
"url": "https://handover.sh/api/mcp?profile=core",
"enabled": true
}
}
} openclaw mcp add sh-handover-handover --url 'https://handover.sh/api/mcp?profile=core' --transport streamable-http
mcp_servers:
sh-handover-handover:
url: "https://handover.sh/api/mcp?profile=core" {
"McpServers": {
"sh-handover-handover": {
"Transport": "http",
"Url": "https://handover.sh/api/mcp?profile=core"
}
}
} assistant mcp add sh-handover-handover -t streamable-http -u 'https://handover.sh/api/mcp?profile=core'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 2 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
- 27 Aug 26 +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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://handover.sh/api/mcp?profile=core
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=handover.sh | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4ee76b08e1b5c1a913148c4365ccab75 |
| SANs: handover.sh, skills.handover.sh, *.skills.handover.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of handover.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| handover.sh. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://handover.sh/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://handover.sh/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://handover.sh/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://handover.sh/api/mcp |
| Authorisation server | https://handover.sh |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://handover.sh/api/mcp?profile=core | Verified | 200 | |
| http (plaintext) | http://handover.sh/api/mcp?profile=core | Inconclusive | 401 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
handover.annotate Annotate a handover artifact ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Actionable annotation body in plain text or Markdown. |
| handoverId | string | yes | Handover containing the artifact being annotated. |
| mentionPrincipalIds | array | – | Collaborator principal IDs to mention and notify. |
| target | object | yes | Immutable artifact location to anchor this annotation. |
No output schema declared.
No examples provided.
handover.annotations Read artifact annotations ~81
Read revision-anchored file comments, selected text, status, authorship, and resolution metadata. Use status=open to find feedback that still needs action.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactId | string | – | – |
| handoverId | string | yes | Handover whose annotation threads should be read. |
| revisionId | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
handover.assign Set handover owners ~65
Replace the open assignments with the supplied collaborator identities. This changes collaboration state, not the immutable handover revision.
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | yes | Handover whose open assignments will be replaced. |
| principalIds | array | yes | Complete replacement list of assigned collaborator principal IDs. |
No output schema declared.
No examples provided.
handover.comment Comment on a handover ~69
Append a discussion comment and optionally notify explicitly mentioned collaborators.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment body in plain text or Markdown. |
| handoverId | string | yes | Handover discussion to append the comment to. |
| mentionPrincipalIds | array | – | Collaborator principal IDs to mention and notify. |
No output schema declared.
No examples provided.
handover.continue Continue a handover ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | array | – | New or replacement files; omitted files remain inherited. |
| brief | object | – | Updated structured continuation brief. |
| expectedRevisionId | string | yes | Current revision ID returned by handover.get; prevents lost updates. |
| handoverId | string | yes | Handover to continue after reading its current snapshot. |
| note | string | – | What changed or what the next collaborator should know. |
No output schema declared.
No examples provided.
handover.create Create a handover ~105
Create durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Short, specific name for the durable context. |
No output schema declared.
No examples provided.
handover.get Inspect a handover ~74
Read a handover snapshot, continuation brief, artifact metadata, and revision history. Omit revisionId for the current snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | yes | Handover identifier returned by handover.search or handover.create. |
| revisionId | string | – | Optional immutable revision; omit to inspect the current revision. |
No output schema declared.
No examples provided.
handover.okf.export Export a handover as OKF ~61
Export a handover revision as an Open Knowledge Format bundle for another human or agent system.
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | yes | Handover to export. |
| revisionId | string | – | Immutable revision to export; defaults to the current revision. |
No output schema declared.
No examples provided.
handover.okf.import Import an OKF bundle ~100
Import Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| expectedRevisionId | string | – | Current revision ID used to prevent conflicting imports. |
| files | array | yes | Files from an Open Knowledge Format bundle. |
| handoverId | string | yes | Existing handover that will receive the imported bundle. |
| mode | string | – | Merge bundle files with inherited artifacts or replace them. |
No output schema declared.
No examples provided.
handover.publication Inspect a published report ~58
Read the stable report URL, entry file, access mode, and selected revision for a handover.
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | – | Handover whose publication should be inspected. |
| slug | string | – | Stable published report slug. |
No output schema declared.
No examples provided.
handover.publish Publish a handover as a report ~128
Create or update a stable /r/{slug}/ report projection of a Handover revision.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | Who can open the report URL. |
| entryPath | string | – | Artifact path opened first when readers visit the report. |
| handoverId | string | yes | 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. |
No output schema declared.
No examples provided.
handover.pull Pull a published report ~78
Return the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | Optional relative paths to return; omit for every file. |
| includeBinary | boolean | – | Return binary files as base64 when true. |
| slug | string | yes | Stable published report slug. |
No output schema declared.
No examples provided.
handover.read_artifact Read a handover artifact ~73
Read bounded artifact content after inspecting a handover. Text is returned as UTF-8 and binary content as base64; truncated results report that explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactId | string | yes | Artifact identifier returned by handover.get. |
| maxBytes | integer | – | Maximum decoded bytes to return before reporting truncation. |
No output schema declared.
No examples provided.
handover.search Search handovers ~72
Find current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content. Use an empty query to list recent handovers.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| mode | string | – | – |
| query | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
handover.thread Read a handover discussion ~44
Read comments, explicit mentions, assignments, and eligible collaborators without changing revision history.
| Name | Type | Req | Description |
|---|---|---|---|
| handoverId | string | yes | Handover whose discussion and assignments should be read. |
No output schema declared.
No examples provided.
handover.update_comment Edit or resolve a comment ~146
Edit an authored comment, or resolve/reopen an annotation. Set resolvedRevisionId when a new handover revision addressed the feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Replacement comment body; omit to preserve the current body. |
| commentId | string | yes | Comment or annotation to edit, resolve, or reopen. |
| handoverId | string | yes | 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. |
No output schema declared.
No examples provided.
handover.whoami Verify the active identity ~41
Return the authenticated person or service agent, organization, workspace, role, and granted scopes. Call this before reading or publishing to confirm attribution and tenancy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.