MCP.Market

Yafl MCP server

by yafl.dev·dev.yafl/mcp·v0.1.6
No reviews yet

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

B72/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

0 stars33 downloads/wk

Reviews

Write one

Nobody has reviewed Yafl yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Yafl tools (7, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • delete_filewrite action

    Permanently deletes ONE of the caller's own YAFL transfers, identified by `id` (a bare transfer id or a full share URL \u2014 the fragment/key, if present, is never read). This cannot be undone: the R2 object is purged and the transfer record is removed. Destructive action.

  • download_file

    Downloads and decrypts exactly the one file referenced by the given YAFL share `url`, writing it only into `destDir` (default: the current working directory) \u2014 never anywhere else. Requires the decryption key embedded in the URL fragment; the key is used only locally to decrypt and is never sent to the API. No YAFL API key is required for retrieval \u2014 anyone holding the link can download

  • email_linkwrite action

    Emails this YAFL share link to a recipient. The link carries the decryption key in its fragment \u2013 anyone with access to that inbox can open the file. Requires a verified account.

  • get_status

    Checks whether the YAFL share link at the given `url` is still live \u2014 live, expired, or not found \u2014 without downloading or decrypting anything. Returns liveness, size, and expiry only. Does not read the decryption key even if present in the URL fragment, and never fetches any file bytes.

  • list_files

    Lists the caller's OWN YAFL transfers only \u2014 metadata only (id, size, status, expiry, and a download path). Never returns file contents, never a decrypted name, and never another account's files. Optionally cap the number of results with `limit`.

  • login

    Starts a device-code login for an MCP agent that has no shell. Returns a verification URL and a short user code for the human to open and approve in a browser; approving is a one-time email-link sign-in that proves the human controls the account. This tool does NOT open a browser itself - relay the returned URL and code to the human. Once approved, the minted API key is stored locally and subseque

  • upload_filewrite action

    Encrypts and uploads exactly the file or directory at the given local `path` (absolute, or relative to the current working directory). A directory is zipped client-side into a single archive before upload. Reads only that one path \u2013 never scans unrelated files or directories. Returns a shareable link (24h expiry, 100MB cap) with the decryption key embedded in the URL fragment; the key is neve

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 54 days ago12/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Yafl compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 40% of 4,460 AI and agents servers
Tools
7
the typical AI and agents server has 6
Tools that change things
43%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
33
more than 22% of 1,538 AI and agents servers with a package

What its tools let an agent do: 4 read · 1 create · 1 delete · 1 send or post

Install Yafl in Claude Code, Cursor or VS Code

Runs npx -y @yafldev/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @yafldev/mcp
Add to Cursor

What the publisher says

From the Yafl repository's README, as published. We do not edit it. Read it on GitHub

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:

{
  "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

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

  • Website: https://yafl.dev
  • MCP guide: https://yafl.dev/mcp
  • Security / threat model: https://yafl.dev/security
  • npm: @yafldev/mcp · @yafldev/cli

License

MIT — see LICENSE.

Nothing above is checked by us. What we check is on the safety report.

Yafl: common questions

Is Yafl MCP server safe?
Mostly: it is graded B (72/100). Read the Yafl safety report
How do I install Yafl?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Yafl need an API key?
Yes. The registry entry asks for YAFL_API_KEY.
Is Yafl maintained?
The last commit was 95 days ago (2026-08-01). The latest release is v0.1.6.
What can I use instead of Yafl?
Servers from other publishers that do the same job: Basic Memory MCP server, agent-device MCP server and HOL Guard MCP server.
How does Yafl compare with other AI and agents MCP servers?
safety score 72/100 (higher than 40% of 4,460 AI and agents servers); tools 7 (the typical AI and agents server has 6); tools that change things 43% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Yafl

Same job from other publishers: the closest match first, then the best rated.

  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • agent-device
    Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
    A
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • Pm Claude Skills
    1310 professional Agent Skills + workflow recipes — searchable & fetchable over MCP.
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A