Yafl

dev.yafl由 yafl.dev 发布v0.1.6更新于 Oct 24, 2026

Agent-first E2EE file transfer over MCP: move files between machines in one tool call, gone in 24h.

已验证STDIO仅桌面文件与存储安全与监控

概览

AI 生成的概览

YAFL 是一个本地 MCP 服务器，让助手上传、下载、查询、列出、删除并通过邮件发送端到端加密、24 小时后失效的文件传输

可以做什么
上传文件或目录，在本地加密后传输，可选密码层和一次性链接，返回分享链接，目录会先打包。从链接下载并解密文件到本地目录。查询链接是否有效及剩余有效期，不下载任何字节。列出自己名下的传输（仅元数据），并在到期前撤销其中一项。在会话内把分享链接通过邮件发给收件人。通过设备流程登录为代理授权，使其持有独立可撤销的密钥。
适用场景
适合助手需要在不同机器或环境之间传递文件的场景，例如笔记本与 VPS 之间、代理与代理之间，无需人工搬运文件或复制链接。也适合无图形界面的服务器，用短期加密链接代替长期链接。
运行要求
通过 npx 在本地运行，需要 Node.js 18 或更高版本，无需全局安装。可通过环境变量 YAFL_API_KEY 提供 API 密钥，也可省略并在浏览器中批准设备流程登录。需要能访问 YAFL 服务的网络。仅支持桌面 MCP 客户端。
安装前请注意
上传会把文件字节发送到第三方存储，但文件已在你的机器上加密，服务方只能看到密文。API 密钥不是解密密钥，但密钥被盗会暴露该密钥名下传输的元数据，建议每个代理、每台机器使用一个可单独撤销的密钥。链接 24 小时后失效，免费额度单文件上限 100 MB。email_link 工具会把分享链接发送给会话之外的收件人。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Yafl，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

YAFL — Yet Another File Layer (MCP server + CLI)

Your AI agent moves files between machines with one MCP call — encrypted client-side, links gone in 24 hours.

This repository is the open-source MCP server and CLI client for YAFL. Your agents (Claude Desktop, Claude Code, Cursor, any MCP client — including agents on remote VPSes) hand files across environments — laptop ↔ VPS, agent ↔ agent — with a single tool call, instead of a human dragging files into WeTransfer and copying links around. Files are encrypted on your machine before they leave it; the service only ever sees ciphertext.

The client is open source so you can audit exactly what touches your files. The YAFL service lives at yafl.dev.

Install

Add YAFL to your MCP client config:

json
{  "mcpServers": {    "yafl": {      "command": "npx",      "args": ["-y", "@yafldev/mcp"],      "env": { "YAFL_API_KEY": "<your key — or leave unset and run yafl login>" }    }  }}

Works in Claude Desktop, Claude Code, Cursor, and any MCP client. Claude Desktop users can install the one-click .mcpb bundle. Prefer the CLI:

curl -fsSL https://yafl.dev/install.sh | sh

No API key is required to start. On the first tool call the server returns a guided error pointing to yafl login — an RFC 8628 device flow: the agent shows a short code, you approve it in a browser, and the agent holds its own revocable key. Built for headless boxes. Runs via npx (Node.js 18+); no global install needed.

Tools

ToolCallWhat it does
upload_file{ path, password?, oneTime? }Encrypts client-side, uploads ciphertext, returns the share link. Zips a directory first. Optional password layer; optional one-time link that burns after the first download.
download_file{ url, destDir?, password? }Fetches, decrypts, writes the file to local disk.
get_status{ url }Checks liveness and remaining TTL — no bytes downloaded.
list_files{ limit? }The caller's own transfers, metadata only.
delete_file{ id | url }Revoke one of your transfers before expiry.
email_link{ link, recipient }Email a share link straight to a recipient — the agent-to-human handoff without leaving the session.
logindevice flowAuthorize this agent (RFC 8628); it holds its own revocable key.

Errors are stable and machine-readable — your agent gets expired or not_found, not a mystery 404.

How encryption works

The file is encrypted with a fresh AES-256-GCM key before upload. The key travels only in the share URL's #fragment — browsers never send fragments to servers, so it is never transmitted to, logged by, or stored on any server. An optional link password adds a second derived layer the server never sees either, and a one-time link self-destructs after the first successful download. File bytes go directly to storage via pre-signed URLs; the app server never handles them, and storage only ever receives ciphertext. Access stops at 24 hours. Free tier: 100 MB per file.

What happens if an agent's key leaks

The API key is not the decryption key. If a machine is compromised and its YAFL key is stolen, the attacker can at most see ciphertext metadata for that key's own transfers — file contents stay unreadable, because decryption keys exist only in the links you exchanged. Revoke the key and move on. This is why the recommended setup is one key per agent, per machine — keys are named and individually revocable.

Links

License

MIT — see LICENSE.

来源：README.md，提交 fdd803f

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.1.6最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分