Celo MCP Server
PYPI · CELO-MCP
Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking
Available components
Last scanned (18 hours ago)
Scores higher than 88% of PyPI servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 67 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to celo-org/celo-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1111 tokens (~65/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −11
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.27 ▲ functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/celo-mcp@0.4.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | celo-org/celo-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/celo-org/celo-mcp/.github/workflows/publish.yml@refs/tags/v0.4.3 |
| Rekor log index | 3522988049 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0ab33e3d469127c46df61d13b5a4aab59573360ceda31c092581b3d53c7e5d2b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 67 packages
| Packages resolved | 67 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_activatable_stakes ~40
Get information about pending stakes that can be activated for earning rewards.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to check activatable stakes for. |
No output schema declared.
No examples provided.
get_block ~97
Fetch detailed information about a specific block on the Celo blockchain using its number or hash. Optionally include full transaction details within the block.
| Name | Type | Req | Description |
|---|---|---|---|
| block_identifier | string|integer | yes | The unique identifier for the block, which can be a block number, hash, or the keyword 'latest' to get the most recent block. |
| include_transactions | boolean | – | Flag to determine whether to include detailed transaction information for each transaction in the block. |
No output schema declared.
No examples provided.
get_celo_balances ~35
Get CELO and stable token balances for an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to check balances for. |
No output schema declared.
No examples provided.
get_faucet_request_status ~80
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | The testnet the request was made on. |
| request_key | string | yes | The request key returned by request_faucet_funds. |
No output schema declared.
No examples provided.
get_gas_fee_data ~24
Get current gas fee data including EIP-1559 fees.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_governance_proposals ~130
Get Celo governance proposals with pagination support.
| Name | Type | Req | Description |
|---|---|---|---|
| include_inactive | boolean | – | Whether to include inactive/expired proposals |
| include_metadata | boolean | – | Whether to fetch metadata from GitHub repository (slower - only use when needed) |
| limit | integer | – | Maximum number of proposals to return (alternative to page_size) |
| offset | integer | – | Number of proposals to skip (alternative to page-based pagination) |
| page | integer | – | Page number (1-based). If provided, overrides offset/limit |
| page_size | integer | – | Number of proposals per page |
No output schema declared.
No examples provided.
get_latest_blocks ~106
Get information about the most recent blocks on the Celo blockchain, with the ability to specify the number of blocks to retrieve and starting offset.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | The number of latest blocks to retrieve information for, with a default of 10 and a maximum of 100. |
| offset | integer | – | Number of blocks to skip from the latest block. For example, offset=0 gets the very latest blocks, offset=10 gets blocks starting from 10 blocks ago. |
No output schema declared.
No examples provided.
get_network_status ~29
Retrieve the current status and connection information of the Celo network, including network health and connectivity details.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_proposal_details ~37
Get detailed information about a specific governance proposal including its content and voting history.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | integer | yes | The governance proposal ID |
No output schema declared.
No examples provided.
get_stable_token_balance ~42
Get balances of all major stable tokens and CELO for an address using multicall.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to check token balances for. |
No output schema declared.
No examples provided.
get_staking_balances ~43
Get staking balances for an address, including active and pending stakes broken down by validator group.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to check staking balances for. |
No output schema declared.
No examples provided.
get_token_balance ~46
Get the token balance for a specific address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address to check the balance for. |
| token_address | string | yes | The contract address of the token. |
No output schema declared.
No examples provided.
get_total_staking_info ~23
Get network-wide staking information including total votes and participation metrics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transaction ~43
Obtain detailed information about a specific transaction on the Celo blockchain using its transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | The unique hash of the transaction to retrieve details for. |
No output schema declared.
No examples provided.
get_validator_group_details ~37
Get detailed information about a specific validator group including its members and performance data.
| Name | Type | Req | Description |
|---|---|---|---|
| group_address | string | yes | The validator group address. |
No output schema declared.
No examples provided.
get_validator_groups ~100
Get information about all validator groups, including their members, votes, capacity, and performance metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of validator groups to return (alternative to page_size) |
| offset | integer | – | Number of validator groups to skip (alternative to page-based pagination) |
| page | integer | – | Page number (1-based). If provided, overrides offset/limit |
| page_size | integer | – | Number of validator groups per page |
No output schema declared.
No examples provided.
request_faucet_funds ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| beneficiary | string | yes | The address to send testnet funds to. |
| network | string | – | The testnet to fund on. |
| wait | boolean | – | Wait for the payout to land before returning (up to 20 seconds). Set false to return the request key immediately. |
No output schema declared.
No examples provided.
How do I install the Celo MCP Server server?
Celo MCP Server runs locally as a PyPI package, launched with uvx celo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · celo-mcp
claude mcp add org-celo-celo-mcp -- uvx celo-mcp
What is the Celo MCP Server server?
Celo MCP Server is listed in the public MCP registry as org.celo/celo-mcp. Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking. This page covers its PyPI package (celo-mcp).
Is the Celo MCP Server server safe to use?
Celo MCP Server scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Celo MCP Server server expose?
Celo MCP Server exposes 17 tools: get_network_status, get_block, get_transaction, get_latest_blocks, get_token_balance, and 12 more. Their descriptions and schemas cost roughly 1,111 tokens of context every time the server is loaded.
Is the Celo MCP Server server still maintained?
Celo MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Celo MCP Server server under?
Celo MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Celo MCP Server server?
VerifyMCP ran 16 checks on Celo MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.