# a4sx sessions (remote · session-exchange.com)

Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions.

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

## Components

- remote · `session-exchange.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange.md), [page](https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange)
- pypi · `a4sx-mcp`: 88/100, [markdown](https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp.md), [page](https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp)

## Channel facts

- Endpoint: `https://session-exchange.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1124 tokens (~160/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the a4sx sessions MCP server?

a4sx sessions is a hosted endpoint at https://session-exchange.com/mcp, so there is nothing to install locally. 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 --transport http com-session-exchange-sessions 'https://session-exchange.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-session-exchange-sessions": {
      "url": "https://session-exchange.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-session-exchange-sessions": {
      "type": "http",
      "url": "https://session-exchange.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-session-exchange-sessions]
url = "https://session-exchange.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-session-exchange-sessions": {
      "type": "remote",
      "url": "https://session-exchange.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-session-exchange-sessions --url 'https://session-exchange.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-session-exchange-sessions:
    url: "https://session-exchange.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-session-exchange-sessions": {
      "Transport": "http",
      "Url": "https://session-exchange.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-session-exchange-sessions -t streamable-http -u 'https://session-exchange.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-session-exchange-sessions": {
      "type": "http",
      "url": "https://session-exchange.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-05 (score 82, 0)

- [functional] Server version: 0.715.0 → 0.717.0

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

- [functional] Server version: 0.714.3 → 0.715.0

### 2026-11-03 (score 81, 0)

- [functional] Server version: 0.713.0 → 0.714.3

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

- [functional] Server version: 0.711.0 → 0.713.0

### 2026-11-01 (score 80, 0)

- [functional] Server version: 0.707.0 → 0.711.0

### 2026-10-31 (score 80, 0)

- [functional] Server version: 0.706.0 → 0.707.0

### 2026-10-30 (score 80, +1)

- [functional] Server version: 0.704.0 → 0.706.0

### 2026-10-29 (score 79, 0)

- [functional] Server version: 0.702.0 → 0.704.0

## MCP tools (7)

### `search_sessions` (~171 tokens)

Search sessions

Search vetted, published coding-agent sessions on a4sx (reviewed marketplace listings), or your own saved sessions with scope=library. Returns ids to use with the other tools.

Input parameters:

- `harness` (array): Only sessions recorded with these harnesses (claude-code, codex-cli, gemini-cli, opencode, grok-build; unknown = not identified). Only Claude Code sessions can be resumed today; the others are view &…
- `limit` (integer)
- `offset` (integer)
- `query` (string): Free-text search. Empty = browse.
- `scope` (string): `public`: vetted marketplace listings (no sign-in needed). `library`: your own saved sessions (needs library:read).
- `sort` (string)
- `tags` (array)

### `get_session_summary` (~75 tokens)

Session summary

Describe one session before using it: what it did, outline, price, and whether you already have access. source=marketplace (default) or library.

Input parameters:

- `id` (string, required)
- `source` (string)
- `tenant` (string): Owning workspace of a marketplace listing (from search results). Optional.

### `acquire_session` (~92 tokens)

Acquire session

Add a marketplace session you are entitled to (free, bought, or granted) to your private library. Never buys anything: for a paid listing it returns status=payment_required with the price and the listing URL.

Input parameters:

- `id` (string, required): Marketplace listing id (from search_sessions).
- `tenant` (string): Owning workspace of a marketplace listing (from search results). Optional.
- `version` (string)

### `fetch_session_context` (~118 tokens)

Load session as context

Load a session from your library (saved, or added with acquire_session) as starting context for this conversation, sized to max_tokens.

Input parameters:

- `id` (string, required): Library id: one of your saved sessions, or the library_id acquire_session returned for a marketplace listing.
- `include_tool_calls` (boolean): Add one-line stubs for tool calls and results.
- `max_tokens` (integer): Context budget. Long sessions keep the opening request and the newest turns that fit; the middle is elided.
- `version` (string)

### `publish_session` (~364 tokens)

Save session to library

Save a session transcript (JSONL), or markdown you composed (format=markdown), to your private a4sx library. The server only rewrites text that matches secret and personal-data patterns (such as tokens, private keys, emails, IP addresses and home-directory user names). It removes no record or field: a raw Claude Code transcript keeps the user's CLAUDE.md and session context (attachment records), file-history snapshot records (absolute file paths), other non-conversation records (such as pr-link), tool-output copies (toolUseResult), and cwd, gitBranch and version on every line; the reply counts them (except version) in unprepared_carriers. Prepare the transcript or compose markdown first, as GET /orient on this server without auth describes (route A, or route B steps 0-8). Private: it is never listed publicly by this tool.

Input parameters:

- `client_scrubbed` (boolean): The client scrubbed before sending. The server scrubs again regardless.
- `content_sha256` (string): Hex SHA-256 of the transcript's UTF-8 bytes; checked.
- `format` (string): jsonl: a transcript. markdown: content you composed (route A in GET /orient on this server without auth); stored as sent, after the same server scrub.
- `idempotency_key` (string)
- `label` (string)
- `parent` (string): Library id this session continues from (lineage).
- `title` (string)
- `transcript` (string, required): The session transcript as JSONL (Claude Code or Codex CLI format; detected automatically), or markdown you composed with format=markdown.
- `visibility` (string): Always private. Listing publicly is a separate step in the web app.

### `request_purchase` (~107 tokens)

Request a purchase

Start buying a paid marketplace listing for the account holder to confirm. Nothing is charged and you never pay: it returns a verify_url and a user_code to give to the account holder, who checks the code, confirms and pays. Then poll get_purchase_request.

Input parameters:

- `id` (string, required): Marketplace listing id (from search_sessions).
- `tenant` (string, required): The listing's workspace (from search_sessions).
- `version` (string): The version you expect; must be the one on sale.

### `get_purchase_request` (~44 tokens)

Purchase request status

Status of a purchase you requested: pending, completed (with acquired_copy_id to load with fetch_session_context), declined or expired.

Input parameters:

- `purchase_request_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 74
- 2026-10-16: 74
- 2026-10-15: 73
- 2026-10-14: 73
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 71

## Common questions

### What is the a4sx sessions MCP server?

a4sx sessions is an MCP server listed in the public MCP registry as com.session-exchange/sessions. Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions. This page covers its hosted endpoint (https://session-exchange.com/mcp).

### Is the a4sx sessions MCP server safe to use?

a4sx sessions scores 82 out of 100 on VerifyMCP. 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 a4sx sessions MCP server expose?

a4sx sessions exposes 7 tools: search_sessions, get_session_summary, acquire_session, fetch_session_context, publish_session, and 2 more. Their descriptions and schemas cost roughly 971 tokens of context every time the server is loaded.

### Does the a4sx sessions MCP server require authentication?

No. We connected to a4sx sessions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the a4sx sessions MCP server still maintained?

a4sx sessions 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.

## Links

- Remote endpoint: https://session-exchange.com/mcp
- Repository: https://github.com/crossvault/a4sx-mcp
- Website: https://session-exchange.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange.json
- HTML version of this page: https://verifymcp.io/servers/com-session-exchange-sessions/session-exchange