MCP server for Cronos Web3 Analytics - comprehensive blockchain analytics for Cronos and zkEVM networks with VVS Finance DEX integration
The Cronos Analytics MCP server presents a well-organized collection of 21 blockchain analytics tools with consistent naming patterns and proper schema definitions. However, several quality gaps prevent a higher score: (1) Output schemas are not explicitly documented in the source code, responses are inferred from handler logic rather than formally specified; (2) Error messages are generic and do not provide recovery guidance beyond 'Failed to X'; (3) Parameter descriptions lack detailed validation rules (ranges, constraints, format examples); (4) No input validation or rate-limiting logic visible; (5) Tool descriptions are functional but lack WHEN-to-use guidance and dependency hints. The naming convention is strong (all tools follow 'cronos_get_*' pattern with clear resource targets), and all 21 tools have descriptions. Schemas are present and properly typed using Zod, with address/hash validation via regex patterns. The tools are well-composed as read-only operations with no breaking cross-dependencies.
Get all yield farms for DeFi protocols with APR/APY data
Get all available trading pairs and market data from Crypto.com Exchange
Get block information by block number, 'latest', or 'pending'
Get the current latest block number and information
Get ERC20 token balance for any address and token contract on Cronos networks
Get specific farm details by LP symbol
Output schemas are not formally documented in source code. Handler responses are inferred from error handling blocks and manual object construction (status, message, data, blockExplorer fields). LLMs cannot guarantee parsing success without explicit output schema declarations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 54 | 2026-07-28+ | v2 |
| 2026-03-09 | C | 61 | - | v1 |
Get market summary and CRO-related trading data
Get native token balance (CRO/zkCRO) for any address on Cronos networks
Get current network information and statistics
Get specific trading pair data and market information
Get detailed transaction information by transaction hash
Get transaction confirmation status and details
Get all trading pairs on VVS with detailed liquidity and volume data
Get VVS DEX summary with top trading pairs and liquidity data
Get VVS token supply information (total, circulating, burned)
Get specific token information from VVS including USD and CRO prices
Get all tokens available on VVS with price information
Get top VVS trading pairs by liquidity with analytics
Get comprehensive wallet overview including all token balances and portfolio summary
Resolve a CronosId (like alice.cro) to its wallet address
Look up the CronosId associated with a wallet address
Error messages lack recovery guidance. All tools throw generic errors like 'Failed to get native balance: {error.message}' instead of categorizing as retryable/user-fixable/fatal and suggesting next steps (e.g., 'User not found. Try search_users() with a partial name.').
Parameter descriptions lack constraint details. For example, 'limit' params in cronos_get_vvs_tokens, cronos_get_vvs_pairs, cronos_get_all_tickers state 'default: 100, max: 1000' in description, but validation logic is not visible. No minimum value documentation. Missing actionable format rules for string inputs beyond regex.
Descriptions lack WHEN-to-use guidance and dependencies. E.g., cronos_resolve_cronosid and cronos_reverse_resolve_cronosid should note their inverse relationship and when to use each. Wallet tools (get_native_balance, get_erc20_balance) should hint that get_wallet_overview combines them.
No visible input validation logic. Tools accept Zod-validated schemas but do not show sanitization, early error reporting, or rate-limiting. No evidence of SQL injection, command injection, or path traversal guards.
No tool annotations (readOnlyHint, idempotentHint). All tools are read-only and idempotent but do not signal this via MCP annotations, forcing LLMs to infer intent from names and descriptions.