get_network_status
Retrieve the current status and connection information of the Celo network, including network health and connectivity details.
Takes no parameters.

org.celoPublished by celo.orgv0.4.3Updated Oct 30, 2026
Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking
The publisher's own server: Celo Docs
Read-only MCP server for the Celo blockchain: lets an assistant look up blocks, transactions, token balances, governance proposals, staking data and request…
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
A Model Context Protocol (MCP) server for interacting with the Celo blockchain. This server provides comprehensive access to Celo blockchain data, token operations, NFT management, smart contract interactions, transaction handling, and governance operations.
To use this MCP server with Cursor IDE, add the following configuration to your MCP settings file (~/.cursor/mcp.json):
The --refresh flag ensures that the latest code is always loaded when the MCP server starts.
For Claude Desktop, add this configuration to your MCP settings file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
The server can also run as a remote MCP endpoint over Streamable HTTP, so clients connect with a single URL — no local Python install. The stdio setup above is unchanged; this is an additional transport.
Run it in HTTP mode:
Then point any remote-capable MCP client at the URL:
Configuration (environment variables):
GET /health returns 200 for hosting health checks. See
docs/DEPLOYMENT.md for container/hosting instructions.
get_network_status
get_block
block_identifier, include_transactions (optional)get_transaction
tx_hashget_account
addressget_latest_blocks
count (optional, default: 10, max: 100)get_token_info
token_addressget_token_balance
token_address, addressget_celo_balances
addressget_nft_info
contract_address, token_idget_nft_balance
contract_address, address, token_id (optional for ERC1155)call_contract_function
contract_address, function_name, abi, function_args (optional), from_address (optional)estimate_contract_gas
contract_address, function_name, abi, from_address, function_args (optional), value (optional)estimate_transaction
to, from_address, value (optional), data (optional)get_gas_fee_data
get_governance_proposals
include_inactive (optional), include_metadata (optional), page (optional), page_size (optional), offset (optional), limit (optional)get_proposal_details
proposal_idget_staking_balances
addressget_activatable_stakes
addressget_validator_groups
get_validator_group_details
group_addressget_total_staking_info
Both faucet tools are testnet-only and require CELO_MCP_FAUCET_API_KEY (see
Faucet access below).
request_faucet_funds
request_key to poll withbeneficiary, optional network (celo-sepolia), optional wait (default true)get_faucet_request_status
request_key, optional network (celo-sepolia)The faucet's browser flow is gated on reCAPTCHA v3, which scores headless
callers badly, so the faucet tools use its API-key path instead. Create a key at
faucet.celo.org/keys (sign in with GitHub; up to
2 keys, 90-day expiry) and set it in your MCP client's env block:
The key is read from the environment and never passed as a tool argument, so it does not enter the model's context or the conversation transcript.
Limits are set by the faucet, not by this server: 10 requests per 24 hours,
counted per GitHub account and per beneficiary address — holding two keys does
not double the allowance. Global daily and 10-minute burst ceilings apply across
all keys on top of that. celo-sepolia (chain ID 11142220) is the only
supported network; there is no mainnet faucet.
The faucet publishes its API contract at openapi.json and llms-full.txt; treat those as the source of truth if amounts or limits change.
Deployment note: the HTTP transport is open unless
MCP_AUTH_TOKENis set. Only configure a faucet key for stdio or authenticated deployments — otherwise anyone reaching/mcpcan spend your daily allowance on arbitrary addresses, and the key can be revoked for abuse.
This project is licensed under the MIT License - see the LICENSE file for details.
For questions, issues, or contributions, please:
Source: README.md at commit f2c1bac
Retrieve the current status and connection information of the Celo network, including network health and connectivity details.
Takes no parameters.
Fetch detailed information about a specific block on the Celo blockchain using its number or hash. Optionally include full transaction details within the block.
block_identifierrequiredinclude_transactionsObtain detailed information about a specific transaction on the Celo blockchain using its transaction hash.
tx_hashrequiredGet information about the most recent blocks on the Celo blockchain, with the ability to specify the number of blocks to retrieve and starting offset.
countoffsetGet the token balance for a specific address.
addressrequiredtoken_addressrequiredGet CELO and stable token balances for an address.
addressrequiredGet balances of all major stable tokens and CELO for an address using multicall.
addressrequiredGet current gas fee data including EIP-1559 fees.
Takes no parameters.
Get Celo governance proposals with pagination support.
pagelimitoffsetpage_sizeinclude_inactiveinclude_metadataGet detailed information about a specific governance proposal including its content and voting history.
proposal_idrequiredGet staking balances for an address, including active and pending stakes broken down by validator group.
addressrequiredGet information about pending stakes that can be activated for earning rewards.
addressrequiredGet information about all validator groups, including their members, votes, capacity, and performance metrics.
pagelimitoffsetpage_sizeGet detailed information about a specific validator group including its members and performance data.
group_addressrequiredGet network-wide staking information including total votes and participation metrics.
Takes no parameters.
Request testnet CELO from the Celo faucet for an address. Testnet only (celo-sepolia); there is no mainnet faucet. Sends 3 CELO per request; dispenses CELO only - no USDm or other stablecoins. Requires the CELO_MCP_FAUCET_API_KEY environment variable, set to a key created at https://faucet.celo.org/keys. Limited to 10 requests per 24 hours, per account and per beneficiary address. Returns the payout transaction hash if it lands while the request is open, otherwise a request_key to check with get_faucet_request_status.
waitnetworkbeneficiaryrequiredCheck whether a queued faucet request has paid out, using the request_key returned by request_faucet_funds. Returns the payout transaction hash once the status is Done.
networkrequest_keyrequired80% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Declare a license in the repository or the registry entry.
org.celoOfficial publisher
Remote MCP server that lets an assistant search and read the public Celo developer documentation and report documentation problems.
org.celoOfficial publisher
Read-only access to the Celo x402 facilitator: check supported payment kinds and assets, verify signed x402 payments, and look up on-chain authorization status.
git clone https://github.com/celo-org/celo-mcpcd celo-mcppip install -e .export CELO_MCP_RPC_URL="https://forno.celo.org" # Default: Celo mainnetexport CELO_MCP_USE_TESTNET=true # Use Celo Sepolia instead{ "mcpServers": { "celo-mcp": { "command": "uvx", "args": ["--refresh", "celo-mcp"] } }}{ "mcpServers": { "celo-mcp": { "command": "uvx", "args": ["--refresh", "celo-mcp"] } }}celo-mcp-server --transport http --port 3000# or via env:MCP_TRANSPORT=http PORT=3000 celo-mcp-server{ "mcpServers": { "celo": { "url": "https://<your-host>/mcp" } }}# Run the MCP serverpython -m celo_mcp.server
# Or use the CLI entry pointcelo-mcp-server{ "mcpServers": { "celo-mcp": { "command": "uvx", "args": ["celo-mcp"], "env": { "CELO_MCP_FAUCET_API_KEY": "cfk_..." } } }}# Install development dependenciespip install -e ".[dev]"
# Run testspytest
# Run with coveragepytest --cov=celo_mcp# Format codeblack src/isort src/
# Lint codeflake8 src/mypy src/