a4sx sessions MCP server
com.session-exchange/sessionssession-exchange.comstreamable-httpv0.1.2Scanned
Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions.
7 tools: 2 do something that can't be undone, 1 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the a4sx sessions MCP server can do
The a4sx sessions MCP server is published by session-exchange.com, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_session and request_purchase) and create or change data (1 tool: acquire_session), but cannot delete data. 4 tools only read.
1 tool reads private data (fetch_session_context); 1 tool brings in text other people can write (fetch_session_context); 1 tool can send data out of your system (publish_session). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.1.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Can't be undone 2Claude Code: ask
publish_sessionSave a session transcript (JSONL), or markdown you composed (format=markdown), to your private a4sx library.Can send data outNo findings
Why it is in this group
- The name "publish_session" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "publish_session" says "publish": it sends or publishes something to other people.
Description, as the server wrote it 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 first. Route A, safer when it is enough: compose the decisions, constraints, state and files worth carrying as markdown and send format=markdown. Route B (Claude Code transcripts; other formats: route A), on a copy, never the original transcript: keep only user, assistant and summary records, re-pointing each parentUuid to the nearest kept ancestor (or null); delete cwd, gitBranch, version and toolUseResult; list the hostnames, KEY=value secrets and client or employer names left (show the user counts, not values), and replace the ones the user approves, literally, in decoded strings and object keys. Either way, get the user's explicit yes before sending. Private: it is never listed publicly by this tool.
Annotations the server declares
- title: Save session to library
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
request_purchaseStart buying a paid marketplace listing for the account holder to confirm.No findings
Why it is in this group
- The name "request_purchase" says "request": a word for a change.
- The name "request_purchase" also says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Request a purchase
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 1Claude Code: ask
acquire_sessionAdd a marketplace session you are entitled to (free, bought, or granted) to your private library.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Acquire session
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
fetch_session_contextLoad a session from your library (saved, or added with acquire_session) as starting context for this conversation, sized to max_tokens.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "fetch_session_context" says "fetch": a word for reading.
What it can reach
- private-dataThe description's first sentence says "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
Description, as the server wrote it Load a session from your library (saved, or added with acquire_session) as starting context for this conversation, sized to max_tokens.
Annotations the server declares
- title: Load session as context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_purchase_requestStatus of a purchase you requested: pending, completed (with acquired_copy_id to load with fetch_session_context), declined or expired.No findings
Why it is in this group
- The name "get_purchase_request" says "get": a word for reading.
Description, as the server wrote it Status of a purchase you requested: pending, completed (with acquired_copy_id to load with fetch_session_context), declined or expired.
Annotations the server declares
- title: Purchase request status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_session_summaryDescribe one session before using it: what it did, outline, price, and whether you already have access.No findings
Why it is in this group
- The name "get_session_summary" says "get": a word for reading.
Description, as the server wrote it Describe one session before using it: what it did, outline, price, and whether you already have access. source=marketplace (default) or library.
Annotations the server declares
- title: Session summary
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_sessionsSearch vetted, published coding-agent sessions on a4sx (reviewed marketplace listings), or your own saved sessions with scope=library.No findings
Why it is in this group
- The name "search_sessions" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search sessions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__sessions__publish_session"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://session-exchange.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://session-exchange.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (2 destructive, 1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://session-exchange.com/mcp: tools/list returned 7 tools to an anonymous client, including acquire_session (destructive), publish_session (destructive), request_purchase (irreversible)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:publish_sessionCan't be undonedescriptioninputSchema
Tools11 removed, 1 changed.−11 removed~1 changedView diff
- Removed:ask_operator
- Removed:get_operator_reports
- Removed:get_operator_status
- Removed:get_operator_ticket
- Removed:get_world_sim_access
- Removed:list_my_modules
- Removed:list_operator_tickets
- Removed:list_operators
- Removed:list_pending_decisions
- Removed:list_world_sim_templates
- Removed:request_operator_change
- Changed:publish_sessionCan't be undonedescriptioninputSchema
Install
Pinned to version 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http sessions https://session-exchange.com/mcpclaude mcp add --transport http sessions https://session-exchange.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__sessions__search_sessions",
"mcp__sessions__get_session_summary",
"mcp__sessions__fetch_session_context",
"mcp__sessions__get_purchase_request"
],
"ask": [
"mcp__sessions__acquire_session",
"mcp__sessions__publish_session",
"mcp__sessions__request_purchase"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sessions. Review it before you use it.
Capability tags behind 2 rules
- mcp__sessions__fetch_session_context private-data, untrusted-input
- mcp__sessions__publish_session outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.session-exchange/sessions/verify?hash=156d1e39442665ecbd15e478e929ce2c513aa6e9f4e3fce4def887451e0b3b56" | jq -e '.changed == false'Pinned hash 156d1e394426, from Nov 11, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.session-exchange/sessions/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.session-exchange/sessions)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:04 UTC.
a4sx sessions MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the a4sx sessions MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the a4sx sessions MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the a4sx sessions MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: publish_session and request_purchase.
What tools does the a4sx sessions MCP server have?
- 7 tools: 2 irreversible, 1 write, 4 read. publish_session, request_purchase, acquire_session, search_sessions, get_session_summary, fetch_session_context and get_purchase_request.
Does the a4sx sessions MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the a4sx sessions MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_session.
Has the a4sx sessions MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.