Celo MCP (official)
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested PyPI celo-mcp 0.4.3 (MIT per PyPI; repo celo-org/celo-mcp). Stdio, 17 tools, uses public Celo mainnet RPC with no key. Real read calls: get_latest_blocks, get_gas_fee_data and get_governance_proposals returned live chain data. get_network_status is a self-check. Wallet/transfer and faucet tools were not called.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 3 of 3 read function calls passed against public mainnet RPC. Faucet and transaction tools not called. Evidence: local test run, Nov 11, 2026.
Transport (tested 2026-11-11): stdio
Token cost (estimate): approx. 1538 tokens, cl100k estimate (17 tools, measured 2026-11-11, version 0.4.3). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 16 read, 0 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
get_activatable_stakes— readget_block— readget_celo_balances— readget_faucet_request_status— readget_gas_fee_data— readget_governance_proposals— readget_latest_blocks— readget_network_status— readget_proposal_details— readget_stable_token_balance— readget_staking_balances— readget_token_balance— readget_total_staking_info— readget_transaction— readget_validator_group_details— readget_validator_groups— readrequest_faucet_funds— unclassified
handshake and tools listed without a recorded key or OAuth
Score 100/100 · Tools 17 · Token cost approx. 1,538 tokens · Compare · Last tested 2026-11-11 · Version tested 0.4.3 · Package celo-mcp · Repo celo-org/celo-mcp
Summary: Celo MCP (official) completed an MCP handshake without credentials and exposed 17 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 17
- Context cost
- approx. 1538 tokens, cl100k estimate (17 tools, measured 2026-11-11, version 0.4.3; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-11
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | uv pip install celo-mcp (Python venv, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 17 tools listed in 2.4s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 5 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (PyPI long_description (package README)). |
| license | pass | 10 | MIT License (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 1538 tokens, cl100k estimate for 17 tools · about 19% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-11
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 17 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-11 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
26f9922ae30b: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "celo-mcp",
"version": "0.4.3",
"registry": "pypi",
"status": "working",
"tested": "2026-11-11",
"tools_count": 17,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`uv pip install celo-mcp` (Python venv, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 17 tools listed in 2.4s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 5 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (PyPI long_description (package README))."
],
"license": [
"pass",
10,
"MIT License (OSI-approved)."
]
}
}Install
uvx celo-mcp
Pin the version we tested
uvx celo-mcp==0.4.3
pip install celo-mcp==0.4.3
tested 2026-11-11. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"celo-mcp": {
"command": "uvx",
"args": [
"celo-mcp==0.4.3"
]
}
}
}Tools listed
get_activatable_stakes, get_block, get_celo_balances, get_faucet_request_status, get_gas_fee_data, get_governance_proposals, get_latest_blocks, get_network_status, get_proposal_details, get_stable_token_balance, get_staking_balances, get_token_balance, get_total_staking_info, get_transaction, get_validator_group_details, get_validator_groups, request_faucet_funds
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"celo-mcp": {
"command": "uvx",
"args": [
"celo-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
uv pip install celo-mcp(Python venv). This is the exact command we ran on 2026-11-11. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (17 in our test).
{
"mcpServers": {
"celo-mcp": {
"command": "uvx",
"args": [
"celo-mcp"
]
}
}
}Test history
- 2026-11-11: New
FAQ
Is Celo MCP deprecated?
No. celo-mcp was not deprecated or archived when we last tested it on 2026-11-11.
What replaces Celo MCP?
Nothing; Celo MCP (official) is not deprecated as of 2026-11-11.
Does Celo MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 17 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.