a4sx sessions
PYPI · A4SX-MCP · 2 COMPONENTS
Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions.
Available components
Last scanned (22 hours ago)
Scores higher than 89% of PyPI servers
Category Code Search and Documentation
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crossvault/a4sx-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% 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 6 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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 21 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.
- 19 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.
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 4 Nov 2026 · Analysed pypi/a4sx-mcp@0.1.0rc2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crossvault/a4sx-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crossvault/a4sx-mcp/.github/workflows/release.yml@refs/tags/v0.1.0rc2 |
| Rekor log index | 3285217555 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:de9f3bc7f619ff06efc876e02cd589d93cf997876bd3a302f95c95470170b1a9 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| 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 →
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_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 ~175
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.
| 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. |
| 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). |
| visibility | string | – | Always private. Listing publicly is a separate step in the web app. |
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 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.
pypi · a4sx-mcp
claude mcp add com-session-exchange-sessions -- uvx a4sx-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 PyPI package (a4sx-mcp).
Is the a4sx sessions MCP server safe to use?
a4sx sessions scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.