Skip to content
ProtocolProbe
Explore

MCP servers › io.github.dimitrihilverda › claude-session-relay

MCP server · registry snapshot 2026-10-23

io.github.dimitrihilverda/claude-session-relay

Self-hosted relay: agent sessions on different machines share a board, chat and check git conflicts — the publisher's description

4 of 5 record checks metTopic: developer-tools · AI-classifiedversion 1.2.0PHPstreamable HTTP

Summary

io.github.dimitrihilverda/claude-session-relay is a remote MCP server listed in the official MCP registry at version 1.2.0.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Repository
public
Topic
developer-toolsAI-classified
Last tested
not tested

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
1.2.0, published 2026-10-07 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-07 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-07; 2 in the 90 days before the 2026-10-23 snapshot.
Most recent 2 versions
  • 1.2.0 · 2026-10-07
  • 1.1.0 · 2026-10-07
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.2.0 (published 2026-10-07).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://{relay_host}/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "claude-session-relay": {
      "url": "https://{relay_host}/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "claude-session-relay": {
      "type": "http",
      "url": "https://{relay_host}/mcp"
    }
  }
}
Claude Code
claude mcp add --transport http claude-session-relay "https://{relay_host}/mcp"
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url "https://{relay_host}/mcp" --transport http
  • The URL contains parts in { } that the entry marks as variables; replace them with your own values.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/dimitrihilverda/claude-session-relayOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.dimitrihilverda
GitHub owner
a personal account (dimitrihilverda)
Repository
github.com/dimitrihilverda/claude-session-relay
Stars
1
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.dimitrihilverda/claude-session-relay

Answered from the data above

Is io.github.dimitrihilverda/claude-session-relay safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.dimitrihilverda/claude-session-relay been security tested?

Not yet. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

Does io.github.dimitrihilverda/claude-session-relay publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.dimitrihilverda/claude-session-relay?

In github.com/dimitrihilverda/claude-session-relay, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “developer-tools”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
developer-tools
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.
Programming language
PHP
api.github.com · 2026-10-23
Hosting type
remote (hosted by the publisher)
registry · 2026-10-23
MCP capability
not checked
not read (no session)
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
active
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
active
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.dimitrihilverda/claude-session-relay: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.dimitrihilverda/claude-session-relay

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.dimitrihilverda/claude-session-relay)](https://protocolprobe.com/mcp/servers/io.github.dimitrihilverda/claude-session-relay)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology