a4sx sessions
REMOTE · SESSION-EXCHANGE.COM · 2 COMPONENTS
Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions.
Available components
Last scanned (4 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
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 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 5 Nov 26 0
- Server version: 0.715.0 → 0.717.0 functional
- 4 Nov 26 +1
- Server version: 0.714.3 → 0.715.0 functional
- 3 Nov 26 0
- Server version: 0.713.0 → 0.714.3 functional
- 2 Nov 26 +1
- Server version: 0.711.0 → 0.713.0 functional
- 1 Nov 26 0
- Server version: 0.707.0 → 0.711.0 functional
- 31 Oct 26 0
- Server version: 0.706.0 → 0.707.0 functional
- 30 Oct 26 +1
- Server version: 0.704.0 → 0.706.0 functional
- 29 Oct 26 0
- Server version: 0.702.0 → 0.704.0 functional
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 · Probed https://session-exchange.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=session-exchange.com | CN=YE1,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6185b157eaafbd4c372b5f318a6cfd72737 |
| SANs: *.session-exchange.com, session-exchange.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of session-exchange.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| session-exchange.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://session-exchange.com/mcp | Verified | 200 | |
| http (plaintext) | http://session-exchange.com/mcp | HTTPS enforced | 301 | https://session-exchange.com/mcp |
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 →
acquire_session Acquire session ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Marketplace listing id (from search_sessions). |
| tenant | string | – | Owning workspace of a marketplace listing (from search results). Optional. |
| version | string | – | – |
No output schema declared.
No examples provided.
fetch_session_context Load session as context ~118
Load a session from your library (saved, or added with acquire_session) as starting context for this conversation, sized to max_tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
get_purchase_request Purchase request status ~44
Status of a purchase you requested: pending, completed (with acquired_copy_id to load with fetch_session_context), declined or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_request_id | string | yes | – |
No output schema declared.
No examples provided.
get_session_summary Session summary ~75
Describe one session before using it: what it did, outline, price, and whether you already have access. source=marketplace (default) or library.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| source | string | – | – |
| tenant | string | – | Owning workspace of a marketplace listing (from search results). Optional. |
No output schema declared.
No examples provided.
publish_session Save session to library ~364
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
request_purchase Request a purchase ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Marketplace listing id (from search_sessions). |
| tenant | string | yes | The listing's workspace (from search_sessions). |
| version | string | – | The version you expect; must be the one on sale. |
No output schema declared.
No examples provided.
search_sessions Search sessions ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
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.
remote · session-exchange.com
claude mcp add --transport http com-session-exchange-sessions 'https://session-exchange.com/mcp'
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.