SRIFT MCP server
Secure P2P file transfer and encrypted chat for AI agents. No accounts, no API keys.
1 stars113 downloads/wk
Reviews
Write oneNobody has reviewed SRIFT yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
SRIFT tools (8, 1 write)
write = sends, deletes, buys or postssrift_approve_joinFreeHost-only. Approve a pending guest join request by their temp user ID.
srift_close_sessionFreeClose the active session. Flushes E2EE keys, disconnects signaling, clears chat history.
srift_join_sessionFreeRequest to join an existing SRIFT session by its 7-character session ID. The host must approve before transfers/chat work.
srift_kick_userFreeHost-only. Disconnect and ban a peer from the active room.
srift_list_transfersFreeList all active and recent transfers with progress, speed, ETA, and status.
srift_reject_joinFreeHost-only. Reject a pending guest join request.
srift_session_statusFreeGet current session details: id, role (host/guest), connection state, pending join requests, peer count.
srift_start_sessionwrite actionFreeCreate a new SRIFT secure session. Returns the 7-character session ID and a shareable URL. The host approves all future joins. E2EE keys derive locally from the session ID + optional roomSecret.
Public scan report
scanner v0.1.9 · 2026-09-19 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned13/25
- Live reliabilityremote reachable in 1923ms20/20
- Tool poisoning8 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 8 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Findings (2)
- highWrite-action tools reachable without authentication
auth.open-write - highShell command built from a string (injection risk)
exec.shell-concatdist/index.js: …er')}` ].join(";"); execSync(`powershell -NoProfile -Command "${psCmd}"`, { stdio: "ignore" }); …
What the publisher says
From the SRIFT repository's README, as published. We do not edit it. Read it on GitHub
SRIFT — Secure P2P File Transfer & MCP Server for AI Agents
Zero-config, zero-token peer-to-peer secure file transfer, encrypted chat, and Model Context Protocol (MCP) server for AI coding agents & developers.
Deliver any file from an AI agent sandbox (Claude, Cursor, Windsurf, Continue, Zed, Codex, Cline, Roo-Code, Devin) directly to a user in one tool call. End-to-end encrypted with AES-256-GCM. No cloud storage, no account signups, no API keys.
🌐 Web Platform: https://srift.app 📦 GitHub Repository: https://github.com/srivardhan113/SRIFT-OpenSource 🤖 AI Agent Hub:** https://srift.app/ai-agents
⚡ Why SRIFT for AI Agents?
AI coding agents run in sandboxed environments. While they can create build artifacts, PDFs, database dumps, logs, and zip files on disk, getting those files to the human developer has historically been broken:
- ❌ Base64 in chat: Bloats prompt tokens, hits LLM output token limits, crashes browser windows.
- ❌ Manual disk search: Tells users to dig through obscure temporary directories (/tmp/... or ~/.cache/...).
- ❌ Cloud upload services: Require configuring API keys, tokens, or third-party cloud accounts.
The SRIFT Solution: One Command, Instant Delivery
SRIFT gives your agent a local headless daemon and toolset to seed files locally and generate a direct download link:
srift quick-share ./dist/release-bundle.zip
# ↳ https://srift.app/d/7k3m9xqThe user opens the link in any web browser or runs curl -OJ https://srift.app/d/7k3m9xq or wget --content-disposition https://srift.app/d/7k3m9xq. The recipient needs nothing installed.
Session transfers are end-to-end encrypted with AES-256-GCM, keys derived locally (PBKDF2-SHA256, 100,000 iterations) and never sent to any server.
⚠️ The sender's daemon must be alive for the link to work.
SRIFT keeps no server-side copy — the daemon streams the file from your disk
on demand. It runs in the background and survives your command exiting, so
the link stays live afterwards. But if the daemon stops (machine sleeps or
reboots, or srift daemon stop) the link returns 503 sender is offline.
This is the direct trade-off for zero retention: nothing is stored, so
nothing can be served once the source goes away.
Public quick-share links are designed to be opened by any browser, curl or wget — clients that hold no key and run no SRIFT code. What SRIFT guarantees for quick-share is zero retention: bytes stream from the sender straight to the open HTTP response, are never written to SRIFT storage, and are served Cache-Control: no-store. If you need the relay to be unable to read the content, use a session transfer instead of a public link.
🚀 Installation
Global Install via npm (Node.js 20+)
npm install -g srift-transferShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-09-19restoreC → Bscore 70: Write-action tools reachable without authentication; Shell command built from a string (injection risk)
Install directly
claude mcp add --transport http srift https://srift.app/mcp
SRIFT: common questions
- Is SRIFT MCP server safe?
- Mostly: it is graded B (73/100). Read the SRIFT safety report
- How do I install SRIFT?
- It runs remotely at srift.app. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does SRIFT need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is SRIFT maintained?
- The last commit was 10 days ago (2026-09-11). The latest release is v3.0.0.
- Is SRIFT up?
- 100% of our last 8 checks got an answer. We check remote servers about four times a day.