explain_transaction — TokenOS Wallet Inspector MCP Tool
explain_transaction
(explain transaction) is one of 3 tools on the
TokenOS Wallet Inspector
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain_transaction from your client
- Claude Code TokenOS Wallet Inspector explain_transaction run in your project directory
- Claude Desktop TokenOS Wallet Inspector explain_transaction ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TokenOS Wallet Inspector explain_transaction ~/.cursor/mcp.json
- VS Code TokenOS Wallet Inspector explain_transaction .vscode/mcp.json
- Zed TokenOS Wallet Inspector explain_transaction ~/.config/zed/settings.json
- Windsurf TokenOS Wallet Inspector explain_transaction ~/.codeium/windsurf/mcp_config.json
- Cline TokenOS Wallet Inspector explain_transaction ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TokenOS Wallet Inspector explain_transaction ~/.gemini/settings.json
- Grok TokenOS Wallet Inspector explain_transaction .mcp.json (in your project root)
- ChatGPT TokenOS Wallet Inspector explain_transaction Settings → Connectors → Advanced → Developer mode
- Claude.ai TokenOS Wallet Inspector explain_transaction Settings → Connectors → Add custom connector
- LangChain TokenOS Wallet Inspector explain_transaction pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wallet-inspector https://tokenos.ai/api/mcp/apps/wallet-inspectorOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.