Chiliz MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORK | Yes | Network to connect to (mainnet or testnet) | |
| PRIVATE_KEY | No | Wallet private key for transactions (optional) | |
| CHILIZ_RPC_URL | Yes | Chiliz mainnet RPC endpoint | |
| CHILIZ_WSS_URL | Yes | WebSocket endpoint for real-time monitoring | |
| COINGECKO_API_KEY | No | CoinGecko API key (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fan_token_priceB | Get current price and market data for a fan token |
| get_multiple_pricesB | Get prices for multiple fan tokens at once |
| get_market_chartC | Get historical price chart data for a token |
| get_wallet_balanceB | Get CHZ and fan token balances for a wallet address |
| get_my_balanceB | Get balance of configured wallet (requires PRIVATE_KEY env) |
| get_blockchain_infoC | Get current Chiliz blockchain information |
| get_transactionC | Get details of a specific transaction |
| get_fan_tokens_listB | Get list of all supported fan tokens |
| get_token_holdersC | Get top holders of a specific fan token |
| send_tokensB | Send CHZ or fan tokens (requires PRIVATE_KEY env) |
| approve_tokenC | Approve token spending for a contract |
| swap_tokensC | Swap between tokens (DEX integration) |
| detect_whale_tradesC | Detect large transactions (whale trades) |
| calculate_token_velocityC | Calculate token velocity and turnover metrics |
| identify_unusual_patternsC | Identify unusual trading patterns |
| get_market_sentimentC | Get overall market sentiment analysis |
| get_social_sentimentC | Analyze social media sentiment for a token |
| track_social_momentumC | Track changes in social media activity |
| get_influencer_activityD | Track influencer mentions and activity |
| analyze_team_performanceC | Analyze correlation between team performance and token price |
| get_upcoming_matchesC | Get upcoming matches for fan token teams |
| get_league_standingsC | Get league standings for a specific league |
| start_block_monitoringB | Start real-time monitoring of new blocks on Chiliz Chain |
| start_log_monitoringC | Start monitoring contract events/logs in real-time |
| start_pending_tx_monitoringC | Start monitoring pending transactions in the mempool |
| monitor_fan_token_transfersC | Monitor real-time transfers of a specific fan token |
| get_recent_blocksC | Get recent blocks from monitoring history |
| get_recent_logsC | Get recent contract logs from monitoring history |
| get_recent_pending_transactionsC | Get recent pending transactions from monitoring |
| get_websocket_statusB | Get WebSocket connection and monitoring status |
| stop_all_monitoringA | Stop all WebSocket monitoring and disconnect |
| query_fan_token_analyticsC | Query detailed fan token analytics via The Graph protocol |
| get_governance_historyC | Get governance proposal and voting history for a token |
| analyze_holder_distributionC | Analyze token holder distribution and concentration |
| track_whale_movementsC | Track large holder (whale) movements via The Graph |
| get_token_velocity_metricsC | Get token velocity and turnover metrics from The Graph |
| compare_token_distributionsB | Compare holder distributions across multiple tokens |
| get_historical_price_dataC | Get historical price data from The Graph subgraph |
| find_best_swap_routeC | Find optimal swap route on KAYEN Protocol |
| calculate_price_impactB | Calculate price impact for a swap on KAYEN |
| detect_arbitrageC | Detect arbitrage opportunities between KAYEN and other DEXs |
| get_pool_apyB | Get APY for a KAYEN liquidity pool |
| track_liquidity_changesC | Track liquidity changes in KAYEN pools |
| compare_validatorsC | Compare Chiliz validators by performance and metrics |
| calculate_staking_rewardsC | Calculate staking rewards projection |
| get_validator_performanceC | Get detailed performance metrics for a validator |
| monitor_slashing_eventsC | Monitor recent slashing events on the network |
| get_validator_risksC | Assess risks of staking with a specific validator |
| calculate_optimal_stakeC | Calculate optimal stake distribution across validators |
| deploy_erc20_tokenC | Deploy a custom ERC-20 token on Chiliz blockchain |
| deploy_nft_collectionB | Deploy an ERC-721 NFT collection on Chiliz blockchain |
| deploy_custom_contractC | Deploy a custom Solidity smart contract on Chiliz blockchain |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 52 tools
Many tools overlap in purpose: get_multiple_prices/get_fan_token_price/get_market_chart/get_historical_price_data; detect_whale_trades/track_whale_movements; calculate_token_velocity/get_token_velocity_metrics; get_token_holders/analyze_holder_distribution/compare_token_distributions. An agent would struggle to choose correctly without additional discrimination cues.
Nearly all names use snake_case with a leading verb such as get_, start_, calculate_, track_, or deploy_, so the convention is predictable throughout. Minor near-duplicates in wording do not break the consistent verb_noun pattern.
52 tools is far beyond the 3-15 well-scoped range and matches the extreme mismatch level. Many tools are overlapping analytics variants or thin wrappers, so the set is bloated rather than purposefully scoped.
The surface covers many read and analytics areas, but core lifecycle actions are missing: staking/delegation execution, governance proposal/vote, NFT minting, generic contract read/write, and wallet transaction history. These gaps create dead ends for common blockchain workflows.