a4sx MCP server

• Registry namecom.session-exchange/sessionsverified in the MCP registry

The registry name sits under session-exchange.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools7
• Server calls itselfcom.session-exchange/sessions
• Server version0.698.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 158 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Use59 PyPI downloads a week
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer645 ms
• Space in an agent's context≈ 1,741 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 86 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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

• get_session_summary

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

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

• fetch_session_context

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

• publish_session

  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…

• request_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

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