MCP.Market

SRIFT MCP server

online · 100% uptime
by srift.app·app.srift/srift·v4.4.0·1 stars
No reviews yet

Decentralized E2EE P2P file transfer + chat: human to human, human to AI, AI to AI. No accounts.

C56/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C56/100

not scanned yet

Adoption
Growing

1 stars130 downloads/wk

Reviews

Write one

Nobody has reviewed SRIFT yet.

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

SRIFT tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How SRIFT compares

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

Safety score
56/100
higher than 11% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
158 ms
faster than 73% of 30,027 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
130
more than 68% of 12,306 servers with a package

Release history: 6 versions in the registry since 2026-09-11, latest 2026-10-17, typically one every 6 days.

Install SRIFT in Claude Code, Cursor or VS Code

claude mcp add --transport http srift https://srift.app/mcp
Add to Cursor

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/7k3m9xq

The 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-transfer

Shortened. The full README is on GitHub.

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

Grade history

  • 2026-10-15downgradeB → Cscore 56: Write-action tools reachable without authentication; Shell command built from a string (injection risk); eval / new Function used
  • 2026-09-19restoreC → Bscore 70: Write-action tools reachable without authentication; Shell command built from a string (injection risk)

SRIFT: common questions

Is SRIFT MCP server safe?
With care: it is graded C, so read the findings first (56/100). Read the SRIFT safety report
How do I install SRIFT?
It runs remotely at srift.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop 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 2 settings from the environment.
Is SRIFT maintained?
The last commit was 31 days ago (2026-10-05). The latest release is v4.4.0.
Is SRIFT up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does SRIFT compare with other MCP servers?
safety score 56/100 (higher than 11% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 158 ms (faster than 73% of 30,027 servers). Full comparison.