identify_token_operator — XRPL.to Token Analytics MCP Tool
identify_token_operator
(identify token operator) is one of 89 tools on the
XRPL.to Token Analytics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call identify_token_operator from your client
- Claude Code XRPL.to Token Analytics identify_token_operator run in your project directory
- Claude Desktop XRPL.to Token Analytics identify_token_operator ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor XRPL.to Token Analytics identify_token_operator ~/.cursor/mcp.json
- VS Code XRPL.to Token Analytics identify_token_operator .vscode/mcp.json
- Zed XRPL.to Token Analytics identify_token_operator ~/.config/zed/settings.json
- Windsurf XRPL.to Token Analytics identify_token_operator ~/.codeium/windsurf/mcp_config.json
- Cline XRPL.to Token Analytics identify_token_operator ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI XRPL.to Token Analytics identify_token_operator ~/.gemini/settings.json
- Grok XRPL.to Token Analytics identify_token_operator .mcp.json (in your project root)
- ChatGPT XRPL.to Token Analytics identify_token_operator Settings → Connectors → Advanced → Developer mode
- Claude.ai XRPL.to Token Analytics identify_token_operator Settings → Connectors → Add custom connector
- LangChain XRPL.to Token Analytics identify_token_operator pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xrpl-to https://api.xrpl.to/v1/mcpOther tools on this server
- search_tokens
- get_token
- get_trending_tokens
- get_new_launches
- get_trades
- get_holders
- get_top_traders
- get_creator_activity
- get_token_flow
- analyze_token_risk
- get_frozen_lines
- get_issuer_actions
- get_wash_trading
- check_scam
- check_domain
- get_ohlc
- get_orderbook
- get_token_pairs
- get_account_info
- get_account_ancestry
- get_transaction
- get_global_stats
- get_network_activity
- get_validators
- get_escrows
- get_xrp_distribution
- get_oracle_prices
- get_top_movers
- get_tokens_by_category
- get_exit_liquidity
- get_wallet_risk
- get_offramp
- get_payment_flows
- get_cex_cashouts
- find_snipers
- find_sandwich_attacks
- describe_bot_activity
- find_arb_pairs
- get_wallet_pnl
- get_token_analytics
- get_holder_graph
- get_whale_activity
- get_trader_rotations
- get_related_projects
- get_social_mentions
- search_x
- get_amm_pools
- get_lp_positions
- get_holder_overlap
- get_account_transactions
- get_account_trustlines
- get_account_objects
- get_account_nfts
- get_nft_offers
- get_nft_activity
- get_nft_collection
- get_holder_cohorts
- get_holder_clusters
- scan_tweet_addresses
- pick_giveaway_winners
- get_testnet
- fund_testnet_account
- get_fear_greed_index
- get_trade_brief
- get_funding_rates
- get_liquidations
- get_crypto_market
- get_prediction_markets
- get_macro_indicators
- find_wallets
- identify_wallet_owner
- get_news
- api_get
- xrpl_command
- run_script
- get_job
- cancel_job
- decode_xrpl
- get_protocol_rules
- explain_result_code
- search_rippled_source
- search_forum_posts
- search_xrpl_docs
- get_api_docs
- save_note
- recall_notes
- delete_note
- get_swap_quote
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.