Session Relay
NPM · SESSION-RELAY
Share coding-agent sessions with your team: /share in one agent, /pickup in another.
Available components
Last scanned (7 hours ago)
Scores higher than 38% of npm servers
Category Memory and Knowledge
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 26 Oct 26 +6
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → 0.86 ▲ functional
- 25 Oct 26 +10
- Known CVEs: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- 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. security
- Dependency health: 0.86 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 154 → 131 ▲ functional
- Schema quality: 154 → 127 ▲ functional
- 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 functional
- 24 Oct 26 49
First indexed and scored.
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 5 Nov 2026 · Analysed npm/session-relay@0.7.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_live_inbox Check live messages ~27
Take new messages from teammates sent to this live session (they are marked as read).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
comment_on_session Comment on a session ~62
Leave a short note on a shared session for the team: a question, a finding, or that you picked it up. Never include secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The note, in plain text or Markdown |
| id | string | yes | Session id |
No output schema declared.
No examples provided.
get_session Load a shared session ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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) |
No output schema declared.
No examples provided.
get_session_diff Get a session's code changes ~79
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Session id |
| max_chars | integer | – | Cut the diff at this many characters (default 100000) |
No output schema declared.
No examples provided.
list_sessions List shared sessions ~153
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
live_status Who's working live ~35
Who is working live right now: repo, branch, what they're doing, files they touched recently, and whether this session is live.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_sessions Search shared sessions ~101
Full-text search over shared sessions (titles, summaries, messages). The query can include "file:<path>" and "branch:<name>" filters.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Only sessions shared by this person: name, email or "me" |
| query | string | yes | Words to look for, e.g. "invoice rounding" or "file:billing.ts retry" |
| this_repo_only | boolean | – | Limit to the current repo (default false) |
No output schema declared.
No examples provided.
send_live_message Message a teammate's live session ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | "question" asks them to answer; "answer" replies to one (with reply_to) |
| message | string | yes | 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) |
No output schema declared.
No examples provided.
share_current_session Share this session ~389
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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) |
No output schema declared.
No examples provided.
share_template Get the repo's handoff template ~37
The handoff template for the current repo: extra sections (some required) and instructions to follow when sharing. Call it before share_current_session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_live Go live ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
stop_live Stop working live ~24
End this session's live session: teammates stop seeing it and messages stop arriving.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
team_activity Team activity ~49
What the team did recently: new shares by repo, handoffs for you, who picked up what, and new comments.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look back this many days (default 1) |
No output schema declared.
No examples provided.
update_live Update your live session ~92
Change what teammates see about this live session (title, current status), or whether this agent may act on their messages without asking.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
update_session Edit a shared session ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
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.
npm · session-relay
claude mcp add ryrahul-session-relay -- npx -y session-relay
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.