# Celo MCP Server (pypi · celo-mcp)

Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `celo-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp.md), [page](https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp)

## Channel facts

- Registry: `pypi`
- Package: `celo-mcp`
- Version: `0.4.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 67 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to celo-org/celo-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1111 tokens (~65/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add org-celo-celo-mcp -- uvx celo-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "org-celo-celo-mcp": {
      "command": "uvx",
      "args": [
        "celo-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-celo-celo-mcp": {
      "command": "uvx",
      "args": [
        "celo-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-celo-celo-mcp -- uvx celo-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-celo-celo-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "celo-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-celo-celo-mcp --command uvx --arg celo-mcp
```

### Hermes

```yaml
mcp_servers:
  org-celo-celo-mcp:
    command: "uvx"
    args: ["celo-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-celo-celo-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "celo-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-celo-celo-mcp -t stdio -c uvx -a celo-mcp
```

### Other

```json
{
  "mcpServers": {
    "org-celo-celo-mcp": {
      "command": "uvx",
      "args": [
        "celo-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 70, −11)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.27

### 2026-11-01 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-28 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 66)

First indexed and scored.

## MCP tools (17)

### `get_network_status` (~29 tokens)

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

### `get_block` (~97 tokens)

Fetch detailed information about a specific block on the Celo blockchain using its number or hash. Optionally include full transaction details within the block.

Input parameters:

- `block_identifier` (string|integer, required): 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.

### `get_transaction` (~43 tokens)

Obtain detailed information about a specific transaction on the Celo blockchain using its transaction hash.

Input parameters:

- `tx_hash` (string, required): The unique hash of the transaction to retrieve details for.

### `get_latest_blocks` (~106 tokens)

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.

Input parameters:

- `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.

### `get_token_balance` (~46 tokens)

Get the token balance for a specific address.

Input parameters:

- `address` (string, required): The address to check the balance for.
- `token_address` (string, required): The contract address of the token.

### `get_celo_balances` (~35 tokens)

Get CELO and stable token balances for an address.

Input parameters:

- `address` (string, required): The address to check balances for.

### `get_stable_token_balance` (~42 tokens)

Get balances of all major stable tokens and CELO for an address using multicall.

Input parameters:

- `address` (string, required): The address to check token balances for.

### `get_gas_fee_data` (~24 tokens)

Get current gas fee data including EIP-1559 fees.

### `get_governance_proposals` (~130 tokens)

Get Celo governance proposals with pagination support.

Input parameters:

- `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

### `get_proposal_details` (~37 tokens)

Get detailed information about a specific governance proposal including its content and voting history.

Input parameters:

- `proposal_id` (integer, required): The governance proposal ID

### `get_staking_balances` (~43 tokens)

Get staking balances for an address, including active and pending stakes broken down by validator group.

Input parameters:

- `address` (string, required): The address to check staking balances for.

### `get_activatable_stakes` (~40 tokens)

Get information about pending stakes that can be activated for earning rewards.

Input parameters:

- `address` (string, required): The address to check activatable stakes for.

### `get_validator_groups` (~100 tokens)

Get information about all validator groups, including their members, votes, capacity, and performance metrics.

Input parameters:

- `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

### `get_validator_group_details` (~37 tokens)

Get detailed information about a specific validator group including its members and performance data.

Input parameters:

- `group_address` (string, required): The validator group address.

### `get_total_staking_info` (~23 tokens)

Get network-wide staking information including total votes and participation metrics.

### `request_faucet_funds` (~199 tokens)

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.

Input parameters:

- `beneficiary` (string, required): 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.

### `get_faucet_request_status` (~80 tokens)

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.

Input parameters:

- `network` (string): The testnet the request was made on.
- `request_key` (string, required): The request key returned by request_faucet_funds.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 70
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 66

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/celo-mcp/
- Socket report: https://socket.dev/pypi/package/celo-mcp
- Repository: https://github.com/celo-org/celo-mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-celo-celo-mcp/celo-mcp