YAFL
Lets an AI coding agent hand a file to another agent (or to you) with one command, encrypted so nobody in between can read it, and the link self-destructs after a day.
🔗 Visit YAFL
Description
If you've ever had to email yourself a file just to move it from your laptop to a server, you already understand the problem YAFL solves — except here it's an AI agent doing the moving, not a person clicking around a mail client. When a coding agent finishes a job on one machine and needs to hand the result to an agent running somewhere else, someone has to build a courier step: upload here, download there, hope nothing leaks in between. YAFL turns that into a single command the agent can issue on its own.
Technically, YAFL is an MCP tool — a small piece of infrastructure that AI agents (Claude Code, Cursor, and similar) can call directly — for encrypted file transfer. Files are encrypted client-side with AES-256-GCM before they ever leave the sending machine; the decryption key lives only in the URL fragment, which is never sent to YAFL's servers, so the storage backend holds ciphertext it cannot read. Links expire automatically after 24 hours, with optional password protection and one-time burn-on-download mode for extra-sensitive transfers. It ships as an npm package (@yafldev/cli, @yafldev/mcp) with device-flow authentication built for headless environments — no browser needed. The free tier caps files at 100MB, which covers most build artifacts, logs, and small datasets but not large model checkpoints or video exports.
💬 Our review
The short version: if you're running multiple AI agents that need to pass files between machines — a laptop and a VPS, or agent-to-agent — YAFL removes a genuinely annoying manual step, and it does it with real end-to-end encryption rather than a plaintext dropbox.
It's not really competing with general file-sync tools like Syncthing (which is about continuous folder sync between your own devices) or one-shot human tools like Magic Wormhole (great for a person sending one file to another person, but not built to be called programmatically by an agent). YAFL's niche is narrower and more useful for its target audience: it's designed to be invoked by code, not clicked by a human. The catch is that it's genuinely early — version 0.1.2 as of July 2026, a single maintainer, and no published paid tier if you outgrow the 100MB free cap. Worth adopting now if you're already building multi-agent workflows and want the encryption guarantees; worth waiting on if you need guaranteed uptime or support SLAs.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Tier gratuit : 100MB par fichier, liens expirant après 24h. Aucun tarif premium documenté à ce jour.
Pros
Chiffrement de bout en bout AES-256-GCM, clé jamais transmise au serveur
Natif MCP : un agent peut l'appeler directement sans script intermédiaire
Authentification device-flow adaptée aux environnements headless
Liens auto-expirants (24h), option mot de passe et lien à usage unique
Cons
Plafond gratuit de 100MB par fichier, insuffisant pour de gros artefacts
Projet très jeune (v0.1.2), un seul mainteneur visible
Aucun palier payant documenté si besoin de dépasser la limite
Pas de garantie de support ou de disponibilité (SLA)