trace_xgr_value_flow — XGR MCP Gateway MCP Tool
trace_xgr_value_flow
(trace xgr value flow) is one of 95 tools on the
XGR MCP Gateway
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call trace_xgr_value_flow from your client
- Claude Code XGR MCP Gateway trace_xgr_value_flow run in your project directory
- Claude Desktop XGR MCP Gateway trace_xgr_value_flow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor XGR MCP Gateway trace_xgr_value_flow ~/.cursor/mcp.json
- VS Code XGR MCP Gateway trace_xgr_value_flow .vscode/mcp.json
- Zed XGR MCP Gateway trace_xgr_value_flow ~/.config/zed/settings.json
- Windsurf XGR MCP Gateway trace_xgr_value_flow ~/.codeium/windsurf/mcp_config.json
- Cline XGR MCP Gateway trace_xgr_value_flow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI XGR MCP Gateway trace_xgr_value_flow ~/.gemini/settings.json
- Grok XGR MCP Gateway trace_xgr_value_flow .mcp.json (in your project root)
- ChatGPT XGR MCP Gateway trace_xgr_value_flow Settings → Connectors → Advanced → Developer mode
- Claude.ai XGR MCP Gateway trace_xgr_value_flow Settings → Connectors → Add custom connector
- LangChain XGR MCP Gateway trace_xgr_value_flow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xdala-workflow-builder https://mcp.xgr.network/mcpOther tools on this server
- get_xgr_network_info
- get_chain_status
- get_latest_block
- get_account_live_state
- get_transaction_evidence
- get_transaction_receipt
- search_transactions
- get_recent_value_transfers
- get_account_transactions
- get_block_transactions
- get_transaction_stats
- search_xgr_transactions
- get_address_relation_graph
- expand_address_relation_graph
- trace_xgr_transaction
- get_relation_edge_transactions
- get_session_transactions
- get_session_status_live
- list_wakeup_targets_by_address
- resolve_wakeup_payload_schema
- get_sessions_overview
- find_latest_xdala_session
- get_latest_session_payload
- get_recent_xdala_sessions
- list_xdala_session_owners
- list_xdala_sessions
- list_xdala_session_ids
- get_xdala_session_detail
- get_xdala_session_stats
- get_xdala_session_timeseries
- get_xdala_step_stats
- get_xdala_payload_key_stats
- get_xdala_payload_term_stats
- get_xdala_payload_field_value_stats
- get_xdala_active_sessions_timeseries
- get_xdala_start_payload_history
- get_session_receipt_logs
- get_xgr_core_addresses
- get_xgr_circulating_supply
- estimate_xdala_rule_gas
- get_xrc729_authority
- find_startable_xdala_workflows
- list_xrc_contracts
- get_xrc_contract
- list_xrc_events
- get_xrc_contract_events
- get_xrc729_ostc_state
- get_xrc_owner_summary
- read_xrc729_ostc_json
- read_xrc137_rule_json
- resolve_xrc729_process_graph
- get_xrc_usage
- list_xrc_process_sessions
- find_reusable_xrc137_rules
- get_unused_xrc137_rules
- get_xrc_failure_stats
- list_xrc729_contracts_by_executor
- create_operation_handoff
- get_operation_status
- cancel_operation_handoff
- create_xdala_bundle_deploy_handoff
- get_xdala_bundle_deploy_handoff
- get_xdala_bundle_deploy_result
- cancel_xdala_bundle_deploy_handoff
- create_xdala_session_start_handoff
- get_xdala_session_start_handoff
- cancel_xdala_session_start_handoff
- get_xdala_session_start_result
- list_recent_operations
- get_xdala_process_mermaid
- list_xgr_standards
- list_xgr_docs
- get_xgr_doc
- get_xdala_authoring_rules
- get_xgr_standard_reference
- get_xgr_standard_schema
- list_xgr_standard_examples
- get_xgr_standard_example
- get_xgr_multibundle_reference
- get_xgr_multibundle_schema
- get_xgr_session_start_schema
- validate_xgr_session_start
- validate_xgr_session_start_handoff
- validate_xgr_multibundle
- validate_xdala_bundle
- validate_xrc137_authoring
- validate_xdala_rules
- validate_xdala_blueprint
- get_xgr_purchase_options
- quote_xgr_purchase
- create_xgr_purchase_order
- create_xgr_purchase_order_by_budget
- get_xgr_starter_gas_options
- request_xgr_starter_gas
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.