tools.handover/handover

Est-ce que tools.handover/handover est sûr ?

Au dernier audit MCP Hub, le serveur MCP « tools.handover/handover » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• channel_ack≈ 199 tokens

  Use the local client at https://handover.tools/client/channel.py rather than calling this by hand. After a fetch with peek=true, the client calls this with the highest sequence number it processed. That is what the peer sees as read, so a response lost in transit never turns into a false read receipt. The cursor never moves back or past the last stored message; calling again with the same seq changes nothing. Slides the channel's expiry.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    This side's channel key.
  • seq · integer · requis
    Highest sequence number this side processed.

  Exemple d'appel

  {"name": "channel_ack", "arguments": {"key": "texte", "seq": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• channel_close≈ 97 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    This side's channel key.

  Exemple d'appel

  {"name": "channel_close", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• channel_fetch≈ 304 tokens

  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. Call only when the person asks. Clients fetch with peek=true, which marks nothing, and then call channel_ack once they have processed the messages; without peek, the messages are marked read when the server sends them (kept for older clients); after=N returns messages after sequence N (the client passes the last one it processed, so a response lost in transit is fetched again; a smaller N re-reads). Side A also receives the peer's SPAKE2 message here to finish pairing. Large backlogs are paged: more=true means fetch again.

  Paramètres, retour & exemple (3)

  Paramètres

  • key · string · requis
    This side's channel key.
  • peek · boolean · optionnel
    If true, do not mark messages as read.
  • after · integer · optionnel
    Return messages with seq greater than this. Defaults to what this side has already fetched.

  Exemple d'appel

  {"name": "channel_fetch", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• channel_join≈ 204 tokens

  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 nameplates are deliberately indistinguishable.

  Paramètres, retour & exemple (2)

  Paramètres

  • pake_msg · string · requis
    Base64 SPAKE2 message (side B).
  • nameplate · string · requis
    First 3 characters of the spoken code, e.g. 'K7M'.

  Exemple d'appel

  {"name": "channel_join", "arguments": {"pake_msg": "texte", "nameplate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• channel_open≈ 233 tokens

  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 machine. The server never sees the password, so it cannot impersonate either side (SPAKE2). The person stays in the loop: send only after they approve, fetch only when they ask. Counts as one write against the daily write quota.

  Paramètres, retour & exemple (1)

  Paramètres

  • pake_msg · string · requis
    Base64 SPAKE2 message from the local client (side A).

  Exemple d'appel

  {"name": "channel_open", "arguments": {"pake_msg": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• channel_send≈ 192 tokens

  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 how far the peer has read.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    This side's channel key.
  • ciphertext · string · requis
    Base64 ciphertext from the client.

  Exemple d'appel

  {"name": "channel_send", "arguments": {"key": "texte", "ciphertext": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• handoff_get≈ 240 tokens

  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 is null with a reason — these cases are deliberately indistinguishable. A channel link (handover.tools/join/<code>, or anything the person said with "Join") is not fetched: join it with the channel client (see /llms.txt). Passed here, it returns reason channel_code with the steps.

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    The 8-character code from handoff_put, e.g. 'kvmtrhxp'.

  Exemple d'appel

  {"name": "handoff_get", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• handoff_put≈ 382 tokens

  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, and ask the person before storing an employer's or client's confidential material (security findings, internal system details, unreleased code). Content becomes unreadable after the TTL expires, and by default it can only be fetched once. The response also returns a revoke_key — keep it for the rest of this session so you can destroy the content immediately with handoff_revoke if the person changes their mind. Writes are limited to a small number per day; reads are not.

  Paramètres, retour & exemple (4)

  Paramètres

  • label · string · optionnel
    Optional short hint shown to whoever fetches it, so they can confirm they got the right thing. Max 120 characters.
  • content · string · requis
    The text to hand off. Maximum 256 KB of UTF-8.
  • ttl_minutes · integer · optionnel
    Minutes until the content can no longer be fetched. Default 60, maximum 1440 (24h).
  • burn_after_read · boolean · optionnel
    If true (the default) the content can be fetched exactly once and is deleted on that fetch.

  Exemple d'appel

  {"name": "handoff_put", "arguments": {"content": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• handoff_revoke≈ 185 tokens

  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 'already_gone'.

  Paramètres, retour & exemple (1)

  Paramètres

  • revoke_key · string · requis
    The revoke_key returned by handoff_put. Not the short code — the short code cannot destroy anything.

  Exemple d'appel

  {"name": "handoff_revoke", "arguments": {"revoke_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://handover.tools/mcp