Handover MCP server
sh.handover/handoverhandover.shstreamable-httpv1.18.0Scanned
Shared, versioned context that humans and AI agents can publish, review, annotate, and continue.
17 tools: 1 do something that can't be undone, 8 change things and 8 only read.
- Reads private data · 4
- Reads text others write · 3
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Handover MCP server can do
The Handover MCP server is published by handover.sh, a domain the MCP Registry verified. It has 17 tools. It can do things that cannot be undone, such as sending, paying or publishing (handover.publish) and create or change data (8 tools: handover.create, handover.continue, handover.comment, handover.annotate and 4 more), but cannot delete data. 8 tools only read.
4 tools read private data (handover.thread, handover.annotations, handover.publication and 1 more); 3 tools bring in text other people can write (handover.thread, handover.annotations and handover.publication); 2 tools can send data out of your system (handover.update_comment and handover.publish). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.18.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Can't be undone 1Claude Code: ask
handover.publishCreate or update a stable /r/{slug}/ report projection of a Handover revision.Can send data outNo findings
Why it is in this group
- The name "handover.publish" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "handover.publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Create or update a stable /r/{slug}/ report projection of a Handover revision.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 8Claude Code: ask
handover.annotateAdd a durable comment anchored to selected text or lines in an immutable artifact revision.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.assignReplace the open assignments with the supplied collaborator identities.No findings
Why it is in this group
- The name "handover.assign" says "assign": a word for a change.
Description, as the server wrote it Replace the open assignments with the supplied collaborator identities. This changes collaboration state, not the immutable handover revision.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.commentAppend a discussion comment and optionally notify explicitly mentioned collaborators.No findings
Why it is in this group
- The name "handover.comment" says "comment": a word for a change.
Description, as the server wrote it Append a discussion comment and optionally notify explicitly mentioned collaborators.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.continueAppend an immutable revision after reading the current snapshot.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.createCreate durable shared context with an initial immutable revision.No findings
Why it is in this group
- The name "handover.create" says "create": a word for a change.
Description, as the server wrote it Create durable shared context with an initial immutable revision. Authorship comes from the authenticated Handover identity.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.okf.exportExport a handover revision as an Open Knowledge Format bundle for another human or agent system.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Export a handover revision as an Open Knowledge Format bundle for another human or agent system.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.okf.importImport Open Knowledge Format files into a new immutable Handover revision.No findings
Why it is in this group
- The name "handover.okf.import" says "import": a word for a change.
Description, as the server wrote it Import Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
handover.update_commentEdit an authored comment, or resolve/reopen an annotation.Can send data outNo findings
Why it is in this group
- The name "handover.update_comment" says "update": a word for a change.
What it can reach
- outboundThe name "handover.update_comment" says "update" and "comment": it writes something other people read.
Description, as the server wrote it Edit an authored comment, or resolve/reopen an annotation. Set resolvedRevisionId when a new handover revision addressed the feedback.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 8Show 8 read-only tools
handover.annotationsRead revision-anchored file comments, selected text, status, authorship, and resolution metadata.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "file": it reads files.
- untrusted-inputThe description's first sentence says "read" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Read revision-anchored file comments, selected text, status, authorship, and resolution metadata. Use status=open to find feedback that still needs action.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.getRead a handover snapshot, continuation brief, artifact metadata, and revision history.No findings
Why it is in this group
- The name "handover.get" says "get": a word for reading.
Description, as the server wrote it Read a handover snapshot, continuation brief, artifact metadata, and revision history. Omit revisionId for the current snapshot.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.publicationRead the stable report URL, entry file, access mode, and selected revision for a handover.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "file": it reads files.
- untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Read the stable report URL, entry file, access mode, and selected revision for a handover.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.pullReturn the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.Reads private dataNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
Description, as the server wrote it Return the selected files of a published report with paths, hashes, media types, and UTF-8 or base64 content.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.read_artifactRead bounded artifact content after inspecting a handover.No findings
Why it is in this group
- The name "handover.read_artifact" says "read": a word for reading.
Description, as the server wrote it Read bounded artifact content after inspecting a handover. Text is returned as UTF-8 and binary content as base64; truncated results report that explicitly.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.searchFind current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content.No findings
Why it is in this group
- The name "handover.search" says "search": a word for reading.
Description, as the server wrote it Find current shared context with hybrid, semantic, or lexical retrieval across metadata and artifact content. Use an empty query to list recent handovers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.threadRead comments, explicit mentions, assignments, and eligible collaborators without changing revision history.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe name "handover.thread" says "thread": it reads messages.
- untrusted-inputThe name "handover.thread" says "thread": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Read comments, explicit mentions, assignments, and eligible collaborators without changing revision history.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handover.whoamiReturn the authenticated person or service agent, organization, workspace, role, and granted scopes.No findings
Why it is in this group
- The name "handover.whoami" says "whoami": a word for reading.
Description, as the server wrote it Return the authenticated person or service agent, organization, workspace, role, and granted scopes. Call this before reading or publishing to confirm attribution and tenancy.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__handover__handover_publish",
"mcp__handover__handover_update_comment"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:18 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://handover.sh/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://handover.sh
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://handover.sh/api/mcp?profile=core: tools/list returned 17 tools to an anonymous client, including handover.publish (irreversible), handover.create (write), handover.continue (write), handover.comment (write), handover.annotate (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.18.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http handover https://handover.sh/api/mcp?profile=coreclaude mcp add --transport http handover https://handover.sh/api/mcp?profile=coreRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__handover__handover_whoami",
"mcp__handover__handover_search",
"mcp__handover__handover_get",
"mcp__handover__handover_read_artifact",
"mcp__handover__handover_thread",
"mcp__handover__handover_annotations",
"mcp__handover__handover_publication",
"mcp__handover__handover_pull"
],
"ask": [
"mcp__handover__handover_create",
"mcp__handover__handover_continue",
"mcp__handover__handover_comment",
"mcp__handover__handover_annotate",
"mcp__handover__handover_update_comment",
"mcp__handover__handover_assign",
"mcp__handover__handover_publish",
"mcp__handover__handover_okf_export",
"mcp__handover__handover_okf_import"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as handover. Review it before you use it.
Capability tags behind 6 rules
- mcp__handover__handover_thread private-data, untrusted-input
- mcp__handover__handover_annotations private-data, untrusted-input
- mcp__handover__handover_update_comment outbound
- mcp__handover__handover_publish outbound
- mcp__handover__handover_publication private-data, untrusted-input
- mcp__handover__handover_pull private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/sh.handover/handover/verify?hash=fed012a964d615e2405ab2692cb80673ae615967632e0a91ba6fe26c4c9f8707" | jq -e '.changed == false'Pinned hash fed012a964d6, from Nov 18, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/sh.handover/handover/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/sh.handover/handover)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.
Handover MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Handover MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Handover MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Handover MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: handover.publish.
What tools does the Handover MCP server have?
- 17 tools: 1 irreversible, 8 write, 8 read. handover.publish, handover.create, handover.continue, handover.comment, handover.annotate, handover.update_comment, handover.assign, handover.okf.export and 9 more.
Does the Handover MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Handover MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): handover.update_comment and handover.publish.
Has the Handover MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.