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 分