SRIFT
REMOTE · SRIFT.APP · 3 COMPONENTS · SCANNED OCT 2
Decentralized P2P file transfer + encrypted chat for AI agents. Military-grade AES-256. No accounts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (srift_close_session). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 852 tokens (~71/item across 12 items; 9 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SRIFT MCP server?
SRIFT is a hosted endpoint at https://srift.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · srift.app
claude mcp add --transport http app-srift-srift 'https://srift.app/mcp'
{
"mcpServers": {
"app-srift-srift": {
"url": "https://srift.app/mcp"
}
}
} {
"servers": {
"app-srift-srift": {
"type": "http",
"url": "https://srift.app/mcp"
}
}
} [mcp_servers.app-srift-srift] url = "https://srift.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-srift-srift": {
"type": "remote",
"url": "https://srift.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-srift-srift --url 'https://srift.app/mcp' --transport streamable-http
mcp_servers:
app-srift-srift:
url: "https://srift.app/mcp" {
"McpServers": {
"app-srift-srift": {
"Transport": "http",
"Url": "https://srift.app/mcp"
}
}
} assistant mcp add app-srift-srift -t streamable-http -u 'https://srift.app/mcp'
{
"mcpServers": {
"app-srift-srift": {
"type": "http",
"url": "https://srift.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Tool “srift_start_session” rewrote its description, which is the text the model reads security
- Server version: 4.2.4 → 4.3.0 functional
- Server version: 4.2.0 → 4.2.4 functional
- “srift_start_session” reworded the description of “roomSecret” cosmetic
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Server version: 4.1.0 → 4.2.0 functional
- 25 Sept 26 +2
- Tool “srift_session_status” rewrote its description, which is the text the model reads security
- Tool “srift_kick_user” rewrote its description, which is the text the model reads security
- Schema quality: 52 → 71 ▼ functional
- Schema quality: 52 → 66 ▼ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 4.0.0 → 4.1.0 functional
- Server version: 3.0.0 → 4.0.0 functional
- New tool “srift_net_diagnose” functional
- “srift_start_session” reworded the description of “roomSecret” cosmetic
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 2 Oct 2026 · Probed https://srift.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=srift.app | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3031b571595dc9913745da6bcb531b5 |
| SANs: srift.app, *.srift.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of srift.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| srift.app. | present | 2371 | 13 | Verified |
| srift.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://srift.app/mcp | Verified | 200 | |
| http (plaintext) | http://srift.app/mcp | HTTPS enforced | 301 | https://srift.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
srift_approve_join Approve Join Request ~45
Host-only. Approve a pending guest join request by their temp user ID.
| Name | Type | Req | Description |
|---|---|---|---|
| tempUserId | string | yes | Temp user ID from session_status pendingJoins |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean | – | True if guest was approved |
| tempUserId | string | – | Approved user temporary ID |
No examples provided.
srift_close_session Close Session ~30
Close the active session. Flushes E2EE keys, disconnects signaling, clears chat history.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Confirmation message |
| success | boolean | – | True if session was closed cleanly |
No examples provided.
srift_join_session Join SRIFT Session ~86
Request to join an existing SRIFT session by its 7-character session ID. The host must approve before transfers/chat work.
| Name | Type | Req | Description |
|---|---|---|---|
| roomSecret | string | – | Optional shared secret matching the host's |
| sessionId | string | yes | 7-character session ID (e.g. ABC1234) |
| username | string | – | Display name (optional, defaults to AI-Agent) |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Status message or instructions |
| sessionId | string | yes | Session room code |
| status | string | – | Join request status (approved, pending, or joined) |
No examples provided.
srift_kick_user Kick Peer ~55
Host-only. Disconnect and remove a peer from the active room. Get the peer's userId from srift_session_status (participants).
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | User ID of the participant to disconnect and remove |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean | – | True if peer was successfully kicked |
| userId | string | – | ID of kicked peer |
No examples provided.
srift_list_transfers List Active Transfers ~27
List all active and recent transfers with progress, speed, ETA, and status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| transfers | array | – | List of live or recent file transfers |
No examples provided.
srift_net_diagnose Diagnose Network Transports ~215
Diagnose SRIFT on this machine: connectivity (DNS, proxy, HTTPS/TLS, WebSocket relay, UDP/P2P, peer discovery, clock), the local runtime (loopback, background processes, daemon + version, disk) and the environment (sandbox/CI/container detection, curl). Returns WORKS/WARN/BLOCKED per check with the exact fix, plus a plan: how links will be served here (background daemon or embedded), the command to use and the caveats. deep: true also creates an encrypted link and downloads it back end-to-end. Read-only apart from that temporary self-test link. Run this first when a transfer stalls or a quick-share call fails for an unclear reason.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Also run an end-to-end self-test: create an encrypted single-use link and download it back through the relay (≈2 MB, a few seconds). |
| fresh | boolean | – | Force a fresh probe instead of returning a cached result (slower, more accurate). |
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | The SRIFT server that was probed |
| checkedAt | string | – | When the probe ran (ISO 8601); cached results show an older time |
| context | object | – | runtime (mcp, cli, npx, binary, pypi…), cliVersion, serverVersion, daemonVersion |
| env | object | – | Relevant environment (proxy vars, sandbox indicators, Node version, etc.) |
| ok | boolean | – | True if the diagnostic ran successfully (independent of what it found) |
| plan | object | – | serveFrom (background-daemon | embedded | unavailable), transport, shareCommand, downloadCommand, advice[] — what to do in this environment |
| recommendedMode | string | – | "relay" when links can be served from here, otherwise "none" |
| rungs | array | – | Each transport rung checked, in order, with status and a fix hint if blocked |
| selfTest | object | – | deep only: { ok, ms, bytes, mbps, via, error? } |
| summary | string | – | One-line conclusion |
| verdict | string | – | "ok", "degraded", or "blocked" |
No examples provided.
srift_reject_join Reject Join Request ~53
Host-only. Reject a pending guest join request.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Optional rejection reason message sent to guest |
| tempUserId | string | yes | Temp user ID from session_status pendingJoins |
| Name | Type | Req | Description |
|---|---|---|---|
| success | boolean | – | True if guest join request was rejected |
| tempUserId | string | – | Rejected user temporary ID |
No examples provided.
srift_session_status Get Session Status ~60
Get current session details: session { id, role (host/guest), connection state, your userId }, pending join requests (approve with srift_approve_join), and members with their userIds (remove one with srift_kick_user).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| participants | array | – | Session members: pass userId to srift_kick_user to remove one |
| peerCount | number | – | Number of connected sockets in the room (hosted endpoint) |
| pendingJoins | array | – | List of pending guest join requests waiting for host approval |
| session | object | – | The active session (id is null when there is none) |
No examples provided.
srift_start_session Start SRIFT Session ~115
Create a new SRIFT secure session. Returns the 7-character session ID and a shareable URL. The host approves all future joins. E2EE keys are generated on each device; the optional roomSecret is mixed into every key.
| Name | Type | Req | Description |
|---|---|---|---|
| roomSecret | string | – | Optional shared secret mixed into every key. Never sent to the server; a member who joins with a different secret cannot read chat or files. |
| sessionName | string | – | Human-readable session name (optional, e.g. "Project Collab") |
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | User role in session (host) |
| sessionId | string | yes | 7-character unique session room code |
| url | string | – | Direct browser join URL to share with peers |
No examples provided.
What is the SRIFT MCP server?
SRIFT is an MCP server listed in the public MCP registry as app.srift/srift. Decentralized P2P file transfer + encrypted chat for AI agents. Military-grade AES-256. No accounts. This page covers its hosted endpoint (https://srift.app/mcp).
Is the SRIFT MCP server safe to use?
SRIFT scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SRIFT MCP server expose?
SRIFT exposes 9 tools: srift_start_session, srift_join_session, srift_session_status, srift_close_session, srift_approve_join, and 4 more. Their descriptions and schemas cost roughly 686 tokens of context every time the server is loaded.
Does the SRIFT MCP server require authentication?
No. We connected to SRIFT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SRIFT MCP server still maintained?
SRIFT is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.