# a4sx sessions (pypi · a4sx-mcp)

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

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

## Components

- remote · `session-exchange.com`: 82/100, [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 (this document), [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

- Registry: `pypi`
- Package: `a4sx-mcp`
- Version: `0.1.0rc2`
- 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**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to crossvault/a4sx-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 722 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% 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 6 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 runs locally as a PyPI package, launched with uvx a4sx-mcp. 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 com-session-exchange-sessions -- uvx a4sx-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-session-exchange-sessions": {
      "command": "uvx",
      "args": [
        "a4sx-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-session-exchange-sessions": {
      "command": "uvx",
      "args": [
        "a4sx-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-session-exchange-sessions -- uvx a4sx-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-session-exchange-sessions": {
      "type": "local",
      "command": [
        "uvx",
        "a4sx-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-session-exchange-sessions --command uvx --arg a4sx-mcp
```

### Hermes

```yaml
mcp_servers:
  com-session-exchange-sessions:
    command: "uvx"
    args: ["a4sx-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-session-exchange-sessions": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "a4sx-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-session-exchange-sessions -t stdio -c uvx -a a4sx-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-session-exchange-sessions": {
      "command": "uvx",
      "args": [
        "a4sx-mcp"
      ]
    }
  }
}
```

## 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 88, +1)

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

### 2026-11-03 (score 87, +1)

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

### 2026-11-01 (score 86, +1)

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

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

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

### 2026-10-28 (score 84, +1)

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

### 2026-10-26 (score 83, +1)

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

### 2026-10-24 (score 82, +1)

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

### 2026-10-21 (score 81, +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.

## MCP tools (5)

### `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` (~175 tokens)

Save session to library

Save a session transcript (JSONL) to your private a4sx library. The server scrubs token-shaped secrets before storing. 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.
- `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).
- `visibility` (string): Always private. Listing publicly is a separate step in the web app.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 87
- 2026-11-03: 87
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 84
- 2026-10-28: 84
- 2026-10-27: 83
- 2026-10-26: 83
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 78

## 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 PyPI package (a4sx-mcp).

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

a4sx sessions scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 5 tools: search_sessions, get_session_summary, acquire_session, fetch_session_context, publish_session. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.

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

### What licence is the a4sx sessions MCP server under?

a4sx sessions declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/a4sx-mcp/
- Socket report: https://socket.dev/pypi/package/a4sx-mcp
- Repository: https://github.com/crossvault/a4sx-mcp
- Website: https://session-exchange.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-session-exchange-sessions/a4sx-mcp