F
licenseNot graded
qualityF
maintenanceEnables read and write access to the Celo blockchain including balance checks, token transfers, swaps, agent identity (ERC-8004), and x402 micropayments, returning unsigned transactions for user signing.
-
Celo MCP Server
Officialby celo-org
Related Servers
Alternatives to Celo MCP Server
No user-submitted related servers found.
Related Servers
onchainos MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables on-chain operations including token search, market data, wallet management, swap execution, and DApp interactions across 20+ blockchains.343MIT- FlicenseNot gradedqualityDmaintenanceEnables blockchain transactions on BSC including balance checks, transfers, token swaps, and reward claims.3-
- FlicenseNot gradedqualityDmaintenanceEnables querying native and ERC-20 balances, checking allowances, retrieving DEX swap quotes, estimating gas costs, and managing Real World Assets and ERC-8004 agent identities on the Mantle Network.1-
- AlicenseAqualityDmaintenanceEnables EVM blockchain operations through Alchemy RPC, including balance queries, contract interactions, transaction sending, and message signing, with multi-chain support across mainnets and testnets.1323 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the Etherlink blockchain, including balance checks, transactions, smart contract interactions, and token operations.98 npm4MIT
TDQS
B3.4/5.0
Scored across 17 tools
Disambiguation3/5
Most tools map cleanly to a distinct resource or action (blocks, transactions, governance, staking, faucet), and list-vs-detail pairs like get_validator_groups/get_validator_group_details are clear. However, the balance trio — get_token_balance, get_celo_balances, and get_stable_token_balance — heavily overlaps, since the latter two both return CELO plus major stablecoin balances via different mechanisms, forcing an agent to guess which to call.
Naming Consistency5/5
All 17 tools follow a predictable snake_case verb_noun pattern, overwhelmingly get_<resource> with two sensible action verbs (request_faucet_funds, get_faucet_request_status). No mixed conventions or vague standalone verbs.
Tool Count4/5
At 17 tools the surface is on the heavier side, but the domain is broad (blocks, transactions, balances, governance, staking, faucet) and each sub-area genuinely needs multiple tools. A few tools, notably the redundant balance variants, could be consolidated.
Completeness3/5
Read coverage is solid for blocks, transactions, governance proposals, validator groups, and staking balances, and the faucet pair forms a complete request/status loop. But the surface is entirely read-only: there is no governance voting, no stake/activate/unstake actions despite get_activatable_stakes, no generic contract read/call, and no event log or address-search tool, leaving dead ends for write-oriented workflows.
Maintenance
ActivityMaintained
ResponsivenessResponsive