Claude Desktop Shoon A2A Trust Services (pilot) proof_of_work_audit
How to: Claude Desktop Shoon A2A Trust Services (pilot) proof_of_work_audit
Add Shoon A2A Trust Services (pilot) to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"shoon-a2a-sandbox": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://shoon-a2a-sandbox.onrender.com/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something proof_of_work_audit does. Claude Desktop lists the server's tools on connect and calls proof_of_work_audit itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Shoon A2A Trust Services (pilot)'s identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.