MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
handover.tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Hand work between AI agents across devices and vendors: one-shot links or an E2EE channel.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http handover-tools-mcp https://handover.tools/mcp
# 2 — ask your agent for something these tools do
# handoff_put, handoff_get, handoff_revoke and 5 more
handover.tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HAAll 2 servers
handover2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http handover-tools-mcp https://handover.tools/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Store a piece of context and get back a short code. The person gives the link handover.tools/<code> to an agent on another device and it can fetch the content — no copy-paste of long text. The code is 8 letters, easy to type on a phone. NOT ENCRYPTED: the server can read what you store, so never put credentials, tokens, or private data in it. Content becomes unreadable after the TTL expires, and b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | The text to hand off. Maximum 256 KB of UTF-8. |
| label | string | no | Optional short hint shown to whoever fetches it, so they can confirm they got the right thing. Max 120 characters. |
| ttl_minutes | integer | no | Minutes until the content can no longer be fetched. Default 60, maximum 1440 (24h). |
| burn_after_read | boolean | no | If true (the default) the content can be fetched exactly once and is deleted on that fetch. |
Fetch content stored by handoff_put using its 8-character code. The code is case-insensitive and hyphens are ignored, so 'kvmtrhxp' and 'KVMT-RHXP' are the same; the person may give it as a link like handover.tools/kvmtrhxp, and passing that is fine too. Return the content to the person verbatim and complete: it can be fetched only once. If the code is unknown, already fetched, or expired, content
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The 8-character code from handoff_put, e.g. 'kvmtrhxp'. |
Destroy content stored by handoff_put right now, before its TTL runs out and whether or not it has been fetched. Requires the revoke_key returned by handoff_put — the person fetching with the short code cannot revoke, only the writer can. Use this the moment someone says they sent the wrong thing, or changed their mind. Revoking an already gone item is not an error: the outcome is reported as 'alr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| revoke_key | string | yes | The revoke_key returned by handoff_put. Not the short code — the short code cannot destroy anything. |
Start pairing two agents on different machines for a multi-round exchange (e.g. one explores, the other studies and asks follow-up questions). Use the local client at https://handover.tools/client/channel.py — do not call this by hand. The client generates a secret password locally, and this call returns only a 3-character nameplate; the person gives nameplate + password (8 letters) to the other m
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pake_msg | string | yes | Base64 SPAKE2 message from the local client (side A). |
Second half of pairing, run by the local client at https://handover.tools/client/channel.py. Send only the first 3 characters of the spoken code (the nameplate) plus this side's SPAKE2 message; the other 5 characters are the password and must never be sent to the server. The nameplate is consumed on success. Returns this side's key and the peer's SPAKE2 message. Unknown, used, or expired nameplate
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nameplate | string | yes | First 3 characters of the spoken code, e.g. 'K7M'. |
| pake_msg | string | yes | Base64 SPAKE2 message (side B). |
Relay one ciphertext to the other side of a paired channel. The ciphertext must come from the local client at https://handover.tools/client/channel.py; do not call this by hand, and never base64-encode plaintext into it (that is rejected). Only send after the person has seen and approved the draft — the server cannot enforce this, the calling agent must. Returns the message's sequence number and h
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | This side's channel key. |
| ciphertext | string | yes | Base64 ciphertext from the client. |
Use the local client at https://handover.tools/client/channel.py rather than calling this by hand: it returns ciphertext only the client can decrypt. Returns the peer's messages this side has not fetched yet, and marks them read so the peer can see they arrived. Call only when the person asks. peek=true reads without marking; after=N re-reads from sequence N (recovery). Side A also receives the pe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | This side's channel key. |
| after | integer | no | Return messages with seq greater than this. Defaults to what this side has already fetched. |
| peek | boolean | no | If true, do not mark messages as read. |
Either side can close. Deletes the channel, both keys, and every stored message immediately. The other side's next fetch reports not_found_or_closed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | This side's channel key. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install handover.tools or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish handover.tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.