# Session Relay (npm · session-relay)

Share coding-agent sessions with your team: /share in one agent, /pickup in another.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `session-relay`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ryrahul-session-relay/session-relay.md), [page](https://verifymcp.io/servers/ryrahul-session-relay/session-relay)

## Channel facts

- Registry: `npm`
- Package: `session-relay`
- Version: `0.7.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (AGPL-3.0-only).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1978 tokens (~131/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Session Relay MCP server?

Session Relay runs locally as an npm package, launched with npx -y session-relay. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add ryrahul-session-relay -- npx -y session-relay
```

### Cursor

```json
{
  "mcpServers": {
    "ryrahul-session-relay": {
      "command": "npx",
      "args": [
        "-y",
        "session-relay"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ryrahul-session-relay": {
      "command": "npx",
      "args": [
        "-y",
        "session-relay"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ryrahul-session-relay -- npx -y session-relay
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ryrahul-session-relay": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "session-relay"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ryrahul-session-relay --command npx --arg -y --arg session-relay
```

### Hermes

```yaml
mcp_servers:
  ryrahul-session-relay:
    command: "npx"
    args: ["-y", "session-relay"]
```

### Netclaw

```json
{
  "McpServers": {
    "ryrahul-session-relay": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "session-relay"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ryrahul-session-relay -t stdio -c npx -a -y session-relay
```

### Other

```json
{
  "mcpServers": {
    "ryrahul-session-relay": {
      "command": "npx",
      "args": [
        "-y",
        "session-relay"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 65, +6)

- [security regression] Known CVEs: unverified → fail
- [functional improvement] Dependency health: unverified → 0.86

### 2026-10-25 (score 59, +10)

- [security regression] Known CVEs: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: 0.86 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: 154 → 131
- [functional improvement] Schema quality: 154 → 127
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Destructive annotations: pass → 100
- [functional] Package version: 0.5.1 → 0.7.0
- [functional] Package version: 0.5.1 → 0.6.0

### 2026-10-24 (score 49)

First indexed and scored.

## MCP tools (15)

### `list_sessions` (~153 tokens)

List shared sessions

List sessions teammates have shared. Defaults to the current repo; pass all_repos to see everything. for_me lists handoffs assigned to you (from any repo).

Input parameters:

- `all_repos` (boolean): List sessions from every repo, not just the current one
- `author` (string): Name, email or "me"
- `branch` (string): Only sessions shared from this git branch
- `file` (string): Only sessions that touched this file (part of the path is fine)
- `for_me` (boolean): Only handoffs assigned to you
- `limit` (integer): How many to return, newest first (default 10)
- `tool` (string): Only sessions from this coding agent

### `search_sessions` (~101 tokens)

Search shared sessions

Full-text search over shared sessions (titles, summaries, messages). The query can include "file:<path>" and "branch:<name>" filters.

Input parameters:

- `author` (string): Only sessions shared by this person: name, email or "me"
- `query` (string, required): Words to look for, e.g. "invoice rounding" or "file:billing.ts retry"
- `this_repo_only` (boolean): Limit to the current repo (default false)

### `get_session` (~136 tokens)

Load a shared session

Load a shared session as a handoff: summary, decisions, next steps, files and conversation. mode "tail" (default) = summary + recent messages; "summary" = summary only; "full" = full transcript, paged with offset.

Input parameters:

- `id` (string, required): Session id from list_sessions or search_sessions
- `mode` (string): How much to load (default "tail")
- `offset` (integer): With mode "full": message to start from, for paging
- `tail` (integer): With mode "tail": only this many of the most recent messages (default: all that were shared)

### `share_current_session` (~389 tokens)

Share this session

Share the session you are in right now with the team. Write the summary yourself from the conversation: it is what teammates read first. Never include secrets.

Input parameters:

- `continues` (string): Id of the shared session this work continues. Defaults to the one loaded with get_session in this repo; "none" to unlink.
- `decisions` (array): Key decisions and why
- `done` (array): What was finished in this session
- `for` (string): Name or email of the teammate this handoff is for
- `goal` (string, required): What this session is trying to achieve
- `hide_prompts` (boolean): Leave the user's typed prompts out (a marker takes their place); your replies and tool steps are kept. Pass true when the user asks to share without their messages. Defaults to the user's setting (re…
- `ignore_template` (boolean): Share even if the repo's template has required sections you left empty
- `include` (string): What to upload besides your summary: nothing, the last 30 messages, or the whole transcript. Default "summary+tail"
- `include_diff` (boolean): Attach the uncommitted changes in this repo (redacted), so the next person gets the exact code state
- `next` (array): Concrete next steps for whoever continues
- `open_questions` (array): Unresolved questions the next person should know about
- `people` (array): Names or emails who can see it; omit for the whole team
- `pr_url` (string): Pull request URL. Defaults to the current branch's open PR (via gh); "none" to leave out
- `sections` (array): Extra sections, e.g. the ones share_template asks for
- `title` (string): Short title; defaults to the first prompt (or the goal, when the user's prompts are left out)

### `get_session_diff` (~79 tokens)

Get a session's code changes

The uncommitted changes a teammate attached to a shared session, as a unified diff. Use it to see exact code state; to apply it, write it to a file and run `git apply`.

Input parameters:

- `id` (string, required): Session id
- `max_chars` (integer): Cut the diff at this many characters (default 100000)

### `share_template` (~37 tokens)

Get the repo's handoff template

The handoff template for the current repo: extra sections (some required) and instructions to follow when sharing. Call it before share_current_session.

### `team_activity` (~49 tokens)

Team activity

What the team did recently: new shares by repo, handoffs for you, who picked up what, and new comments.

Input parameters:

- `days` (integer): Look back this many days (default 1)

### `comment_on_session` (~62 tokens)

Comment on a session

Leave a short note on a shared session for the team: a question, a finding, or that you picked it up. Never include secrets.

Input parameters:

- `body` (string, required): The note, in plain text or Markdown
- `id` (string, required): Session id

### `update_session` (~244 tokens)

Edit a shared session

Change a share you made (or any share, if you're an admin): title, summary fields, who it's for, the PR link or visibility. Summary lists you pass replace the old ones; use add_next to append next steps.

Input parameters:

- `add_next` (array): Next steps to append to the existing ones
- `decisions` (array): Replaces the decisions
- `done` (array): Replaces what was done
- `for` (string): Teammate name or email, or "none"
- `goal` (string): New goal
- `id` (string, required): Id of the session to change
- `next` (array): Replaces the next steps
- `open_questions` (array): Replaces the open questions
- `people` (array): Make it visible only to these people; an empty list makes it visible to the whole team
- `pr_url` (string): Pull request URL, or "none"
- `publish` (boolean): Publish a draft (saved automatically at session end) to the team, or to `people`
- `sections` (array): Replaces the extra sections
- `title` (string): New title

### `start_live` (~90 tokens)

Go live

Start working live in this repo: teammates see what you're working on and which files you touch, and their messages reach you between steps. Lists who else is live here.

Input parameters:

- `autonomy` (boolean): Let this agent act on teammates' messages without asking the user first. Only true if the user explicitly asked for it.
- `title` (string): What this session is working on, in a few words

### `live_status` (~35 tokens)

Who's working live

Who is working live right now: repo, branch, what they're doing, files they touched recently, and whether this session is live.

### `send_live_message` (~166 tokens)

Message a teammate's live session

Send a short message to a teammate who is working live: it reaches their agent between steps. Use it to tell them about a change that affects them, ask a question, or answer theirs. Never include secrets.

Input parameters:

- `kind` (string): "question" asks them to answer; "answer" replies to one (with reply_to)
- `message` (string, required): The message, in plain words
- `reply_to` (integer): Number of the message you're answering
- `to` (string): Teammate name or email, "everyone" (all live in this repo), or a live session id. Optional when replying.
- `wait_seconds` (integer): For questions: wait up to this long for the answer and return it (default 0, don't wait)

### `check_live_inbox` (~27 tokens)

Check live messages

Take new messages from teammates sent to this live session (they are marked as read).

### `update_live` (~92 tokens)

Update your live session

Change what teammates see about this live session (title, current status), or whether this agent may act on their messages without asking.

Input parameters:

- `autonomy` (boolean): true only if the user explicitly asked to let you act on teammates' messages without asking
- `status` (string): What you're doing right now, e.g. "running the migration tests"
- `title` (string): What this session is working on

### `stop_live` (~24 tokens)

Stop working live

End this session's live session: teammates stop seeing it and messages stop arriving.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ryrahul-session-relay/session-relay#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 66
- 2026-10-27: 66
- 2026-10-26: 65
- 2026-10-25: 59
- 2026-10-24: 49

## Common questions

### What is the Session Relay MCP server?

Session Relay is an MCP server listed in the public MCP registry as io.github.Ryrahul/session-relay. Share coding-agent sessions with your team: /share in one agent, /pickup in another. This page covers its npm package (session-relay).

### Is the Session Relay MCP server safe to use?

Session Relay scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Session Relay MCP server expose?

Session Relay exposes 15 tools: list_sessions, search_sessions, get_session, share_current_session, get_session_diff, and 10 more. Their descriptions and schemas cost roughly 1,684 tokens of context every time the server is loaded.

### Is the Session Relay MCP server still maintained?

Session Relay is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Session Relay MCP server under?

Session Relay declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/session-relay
- Socket report: https://socket.dev/npm/package/session-relay
- Repository: https://github.com/Ryrahul/session-relay
- Website: https://relay.rahulweb.online/
- Changelog RSS feed: https://verifymcp.io/servers/ryrahul-session-relay/session-relay.xml
- Changelog JSON feed: https://verifymcp.io/servers/ryrahul-session-relay/session-relay.json
- HTML version of this page: https://verifymcp.io/servers/ryrahul-session-relay/session-relay