get_token_transactions — wallet tracker MCP Tool Read-only
get_token_transactions
(get token transactions) is one of 21 tools on the
wallet tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_token_transactions from your client
- Claude Code wallet tracker get_token_transactions run in your project directory
- Claude Desktop wallet tracker get_token_transactions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor wallet tracker get_token_transactions ~/.cursor/mcp.json
- VS Code wallet tracker get_token_transactions .vscode/mcp.json
- Zed wallet tracker get_token_transactions ~/.config/zed/settings.json
- Windsurf wallet tracker get_token_transactions ~/.codeium/windsurf/mcp_config.json
- Cline wallet tracker get_token_transactions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI wallet tracker get_token_transactions ~/.gemini/settings.json
- Grok wallet tracker get_token_transactions .mcp.json (in your project root)
- ChatGPT wallet tracker get_token_transactions Settings → Connectors → Advanced → Developer mode
- Claude.ai wallet tracker get_token_transactions Settings → Connectors → Add custom connector
- LangChain wallet tracker get_token_transactions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http wallet-tracker https://mcp.cabalspy.xyz/mcpOther tools on this server
- get_started
- get_api_status
- lookup_wallet
- get_wallet_tracker
- get_leaderboard
- list_wallets
- get_wallet_history
- get_wallet_holdings
- get_pnl_calendar
- get_wallet_connections
- compare_wallets
- get_token_stats
- get_token_holders
- compare_tokens
- detect_bundles
- get_recent_trades
- get_activity_metrics
- get_signals
- get_signal_history
- get_analytics
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.