_ registry / mcp + a2a streamable-http · checked 1h ago

srift-mcp-server

https://srift.app

Registry code: 93376ece25b7294f

api record

SRIFT hosted MCP endpoint (https://srift.app/mcp). Session/peer orchestration only — no filesystem access, no E2EE key material ever touches this server. Use srift_start_session to open a room and share the URL with a human running the SRIFT web app or CLI; use srift_approve_join to let them in. File transfer + chat happen directly, E2EE, between the real peers. Read srift://docs/quickstart for the full guide and the local-vs-hosted tool differences.

endpoint
https://srift.app/mcp
door code
0a40ca6792a23765
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is srift-mcp-server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is srift-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does srift-mcp-server have?
9 tools: srift_session_status, srift_approve_join, srift_list_transfers, srift_join_session, srift_close_session, srift_start_session, srift_reject_join, srift_kick_user, ….
Is srift-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.1%· all time 99.3%

latency
1,868ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1255 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
_ what it is for
used for
  • start a secure peer-to-peer file transfer session
  • approve guests joining a session
  • monitor transfers
takes → gives
text → data
tools
3 reads6 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • srift_net_diagnose reads open 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "deep": {
          "type": "boolean",
          "description": "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": {
          "type": "boolean",
          "description": "Force a fresh probe instead of returning a cached result (slower, more accurate)."
        }
      }
    }
    arguments 13 lines
  • srift_session_status reads unknown 20h ago

    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).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • srift_approve_join changes data unknown never probed

    Host-only. Approve a pending guest join request by their temp user ID.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tempUserId"
      ],
      "properties": {
        "tempUserId": {
          "type": "string",
          "description": "Temp user ID from session_status pendingJoins"
        }
      }
    }
    arguments 12 lines
  • srift_list_transfers reads unknown never probed

    List all active and recent transfers with progress, speed, ETA, and status.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • srift_join_session changes data unknown never probed

    Request to join an existing SRIFT session by its 7-character session ID. The host must approve before transfers/chat work.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sessionId"
      ],
      "properties": {
        "username": {
          "type": "string",
          "description": "Display name (optional, defaults to AI-Agent)"
        },
        "sessionId": {
          "type": "string",
          "description": "7-character session ID (e.g. ABC1234)"
        },
        "roomSecret": {
          "type": "string",
          "description": "Optional shared secret matching the host's"
        }
      }
    }
    arguments 20 lines
  • srift_close_session changes data unknown never probed

    Close the active session. Flushes E2EE keys, disconnects signaling, clears chat history.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • srift_start_session changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "roomSecret": {
          "type": "string",
          "description": "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": {
          "type": "string",
          "description": "Human-readable session name (optional, e.g. \"Project Collab\")"
        }
      }
    }
    arguments 13 lines
  • srift_reject_join changes data unknown never probed

    Host-only. Reject a pending guest join request; the temp user ID comes from pendingJoins in srift_session_status.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tempUserId"
      ],
      "properties": {
        "reason": {
          "type": "string",
          "description": "Optional rejection reason message sent to guest"
        },
        "tempUserId": {
          "type": "string",
          "description": "Temp user ID from session_status pendingJoins"
        }
      }
    }
    arguments 16 lines
  • srift_kick_user changes data unknown never probed

    Host-only. Disconnect and remove a peer from the active room. Get the peer's userId from srift_session_status (participants).

    mcp-tool

    {
      "type": "object",
      "required": [
        "userId"
      ],
      "properties": {
        "userId": {
          "type": "string",
          "description": "User ID of the participant to disconnect and remove"
        }
      }
    }
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 93376ece25b7294f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/93376ece25b7294f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/93376ece25b7294f/badge.svg)](https://brick.blue/agent/93376ece25b7294f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.