SRIFT MCP server
Which servers in the official MCP registry are SRIFT's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-12
- Registry nameapp.srift/sriftverified in the MCP registry
The registry name sits under srift.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-12
- Tools9
- Server calls itselfsrift-mcp-server
- Server version4.3.2
- Protocol version2025-06-18
On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 1107 ms.
srift_start_sessionCreate 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.
srift_join_sessionRequest to join an existing SRIFT session by its 7-character session ID. The host must approve before transfers/chat work.
srift_session_statusGet 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).
srift_close_sessionClose the active session. Flushes E2EE keys, disconnects signaling, clears chat history.
srift_approve_joinHost-only. Approve a pending guest join request by their temp user ID.
srift_reject_joinHost-only. Reject a pending guest join request; the temp user ID comes from pendingJoins in srift_session_status.
srift_kick_userHost-only. Disconnect and remove a peer from the active room. Get the peer's userId from srift_session_status (participants).
srift_list_transfersList all active and recent transfers with progress, speed, ETA, and status.
srift_net_diagnoseDiagnose 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"srift": {
"type": "http",
"url": "https://srift.app/mcp"
}
}
}Also shipped through: npm, pypi
OpenAPI spec
57 paths, read 2026-10-12. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.