MCP Server for Cronos Blockchain
Overview
CATO (Cronos Agentic Tooling Orchestrator) is an MCP (Model Context Protocol) server that provides AI agents with comprehensive access to Cronos blockchain functionality, including:- Multi-chain portfolio aggregation (EVM, zkEVM, POS)
- DeFi yield comparison across protocols
- Transaction error debugging and analysis
- SDK documentation and code examples
- Smart contract templates with deployment scripts
- Cross-chain bridge instructions
- x402 gasless payment technology integration
Protocol: Model Context Protocol (MCP) v1.0
License: MIT
Quick Navigation
MCP Tools
7 powerful tools for blockchain interaction
MCP Resources
Access historical transaction data
Error Handling
Consistent error response format
Rate Limits
Understand usage limitations
MCP Tools
CATO provides 7 core tools for interacting with the Cronos blockchain:Portfolio & Assets
get_unified_portfolio
Aggregate token balances across all Cronos chains (EVM, zkEVM, POS) for a given address.
DeFi Analytics
find_best_yield
Compare yield opportunities across Cronos DeFi protocols (Tectonic, VVS Finance, Fulcrom).
Developer Tools
decode_transaction_error
Decode revert reasons from failed transactions
query_cronos_sdk_docs
Search across all Cronos documentation
get_contract_template
Retrieve smart contract templates
get_bridge_instructions
Get cross-chain bridge guides
Payment Technology
get_x402_examples
x402 payment technology documentation and code examples for gasless payments.
MCP Resources
Transaction History
cronos://history/{address}
Provides historical transaction data from BigQuery for a given Cronos address.
Error Handling
All tools return errors in a consistent format:Common Error Codes
| Error | Description | Solution |
|---|---|---|
Invalid address format | Address doesn’t match 0x… or cro1… pattern | Verify address format |
Transaction not found | TX hash doesn’t exist on chain | Check hash and chain parameter |
RPC timeout | Chain query exceeded 5s timeout | Retry request |
BigQuery auth failed | Missing GCP credentials | Run gcloud auth application-default login |
No results found | Search query returned no matches | Try broader search terms |
Rate Limits
CATO uses public RPC endpoints with the following limits:| Endpoint | Rate Limit | Timeout |
|---|---|---|
| Cronos EVM RPC | ~50 req/sec | 30s |
| Cronos zkEVM RPC | ~50 req/sec | 30s |
| Cronos POS RPC | ~50 req/sec | 30s |
| BigQuery | GCP quota | 60s |
Tool Categories
By Functionality
- Portfolio
- DeFi
- Development
get_unified_portfolio- Multi-chain balance aggregation
By Use Case
Building a DApp
Building a DApp
- Use
query_cronos_sdk_docsto find SDK examples - Get contract templates with
get_contract_template - Debug transactions using
decode_transaction_error
Managing Assets
Managing Assets
- Check portfolio with
get_unified_portfolio - Find yield opportunities using
find_best_yield - Bridge assets with
get_bridge_instructions
Integrating Payments
Integrating Payments
- Learn about x402 with
get_x402_examples - Get implementation guides
- Review code examples
Debugging Issues
Debugging Issues
- Decode errors with
decode_transaction_error - Check transaction history via resources
- Review gas analysis
Example Usage
Here’s a typical workflow using CATO tools:Check Portfolio & Find Opportunities
Debug & Fix Transactions
Additional Resources
Cronos Documentation
Official Cronos documentation
MCP Protocol Spec
Learn about Model Context Protocol
GitHub Repository
View source code and contribute
Support
Get help from the community
Last Updated: January 23, 2026
API Version: 1.0.0
API Version: 1.0.0