Skip to content

Handoff: File Sharing for AI Agents

io.github.jueluddinsf/handoffjueluddinsfstreamable-httpv1.0.0Scanned

Private file storage and controlled share links for AI agents.

10 tools: 1 can delete or cancel things, 5 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 5 write, 4 read.
  • Reads private data · 3
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

10 tools

Deletes or cancels 1Claude Code: deny
  • revoke_sharePermanently revoke an owned share.No findings

    Why it is in this group

    • The name "revoke_share" says "revoke": a word for removing or ending something.
    • The description says "cannot be undone".
    Description, as the server wrote it
    Permanently revoke an owned share. Later downloads fail. This cannot be undone and does not delete the file. Requires your API key.
Changes things 5Claude Code: ask
  • approve_shareApprove an owned grant that was created with requires_approval.No findings

    Why it is in this group

    • The name "approve_share" says "approve": a word for a change.
    Description, as the server wrote it
    Approve an owned grant that was created with requires_approval. Opens stay blocked until this succeeds. Requires your API key.
  • deny_shareDeny an owned grant.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
    Deny an owned grant. A denied grant stays blocked. Requires your API key.
  • save_fileSave a private file for this account.No findings

    Why it is in this group

    • The name "save_file" says "save": a word for a change.
    Description, as the server wrote it
    Save a private file for this account. Use this after signup when you have bytes to store and do not want a public link yet. Returns the file id and metadata. Does not share the file. Requires your API key.
  • signupCreate a Handoff account and return an API key once.1 finding

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    Findings

    • Warn

      The description contains "any other tool", wording about other tools or servers.

      Matched text

      description: "...n API key once. Call this first, before any other tool. No Authorization header is required. S..."

      What this check looks for
    Description, as the server wrote it
    Create a Handoff account and return an API key once. Call this first, before any other tool. No Authorization header is required. Save api_key. On later calls send Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass api_key only if you cannot set headers. The key is a secret. Do not put it in a file you share.
Only reads 4Show 4 read-only tools
  • fetch_shared_fileDownload a file from a share url or token.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "fetch_shared_file" says "fetch": a word for reading.

    What it can reach

    • private-dataThe name "fetch_shared_file" says "fetch" and "file": it reads files.
    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Download a file from a share url or token. Use this when you were given a Handoff url and need the bytes. Honors expiry, open limits, approval, and agent audience. anyone_with_link needs no key. An agent audience uses your API key. Files up to 1048576 bytes return content_base64, plus content_text when the file is text. Larger files are not inlined: the error includes the byte size and tells you to GET the url. A successful inline return counts as an open. A file over the inline limit does not.
  • get_access_logRead the latest 1000 access attempts for an owned grant, including refused downloads.No findings

    Why it is in this group

    • The name "get_access_log" says "get": a word for reading.
    Description, as the server wrote it
    Read the latest 1000 access attempts for an owned grant, including refused downloads. Use this to see whether a share was opened. Requires your API key.
  • get_share_statusRead an owned grant: token_prefix (not the secret), audience, approval, expiry, revocation, and open_count.Reads private dataNo findings

    Why it is in this group

    • The name "get_share_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "secret": it reads secrets.
    Description, as the server wrote it
    Read an owned grant: token_prefix (not the secret), audience, approval, expiry, revocation, and open_count. Does not download the file and does not return the share URL. Requires your API key.
  • list_filesList this account's files, newest first, up to 1000.Reads private dataNo findings

    Why it is in this group

    • The name "list_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    List this account's files, newest first, up to 1000. Use this to find a file_id before sharing. Returns metadata only, never bytes or download URLs. Requires your API key.

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnsignup

    The description contains "any other tool", wording about other tools or servers.

    Matched text

    description: "...n API key once. Call this first, before any other tool. No Authorization header is required. S..."

    What this check looks for

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.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http handoff https://hand-off.space/mcp
claude mcp add --transport http handoff https://hand-off.space/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__handoff__list_files",
      "mcp__handoff__get_share_status",
      "mcp__handoff__get_access_log",
      "mcp__handoff__fetch_shared_file"
    ],
    "ask": [
      "mcp__handoff__signup",
      "mcp__handoff__save_file",
      "mcp__handoff__create_share_link",
      "mcp__handoff__approve_share",
      "mcp__handoff__deny_share"
    ],
    "deny": [
      "mcp__handoff__revoke_share"
    ]
  }
}

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 handoff. Review it before you use it.

Capability tags behind 3 rules
  • mcp__handoff__list_files private-data
  • mcp__handoff__get_share_status private-data
  • mcp__handoff__fetch_shared_file private-data, untrusted-input

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://anlyon.dev/api/v1/servers/io.github.jueluddinsf/handoff/verify?hash=d9e6b31c9ed8e328ccd0fbfa194124b9e6694ffa385c54ecea1b232ed825459f" | jq -e '.changed == false'

Pinned hash d9e6b31c9ed8, from Oct 29, 2026, 18:24 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.jueluddinsf/handoff/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.github.jueluddinsf/handoff
[![anlyon.dev](https://anlyon.dev/badge/io.github.jueluddinsf/handoff.svg)](https://anlyon.dev/servers/io.github.jueluddinsf/handoff)

Source: MCP Registry · repository. Synced Oct 29, 2026, 18:24 UTC.