Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Celo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
25
downloads a day
local
runs on your machine
814
downloads in 30d
What it does
Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user celo-mcp '--' uvx celo-mcp
# 2 — ask your agent for something these tools do
# get_network_status, get_block, get_transaction and 14 more
Celo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CEAll 3 servers
celo3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Celo as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user celo-mcp '--' uvx celo-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Retrieve the current status and connection information of the Celo network, including network health and connectivity details.
No parameter schema on file.
Fetch detailed information about a specific block on the Celo blockchain using its number or hash. Optionally include full transaction details within the block.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Flag to determine whether to include detailed transaction information for each transaction in the block. |
Obtain detailed information about a specific transaction on the Celo blockchain using its transaction hash.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tx_hash | string | yes | The unique hash of the transaction to retrieve details for. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | The number of latest blocks to retrieve information for, with a default of 10 and a maximum of 100. |
| offset | integer | no | 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 the token balance for a specific address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token_address | string | yes | The contract address of the token. |
| address | string | yes | The address to check the balance for. |
Get CELO and stable token balances for an address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The address to check balances for. |
Get balances of all major stable tokens and CELO for an address using multicall.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The address to check token balances for. |
Get current gas fee data including EIP-1559 fees.
No parameter schema on file.
Get Celo governance proposals with pagination support.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_inactive | boolean | no | Whether to include inactive/expired proposals |
| include_metadata | boolean | no | Whether to fetch metadata from GitHub repository (slower - only use when needed) |
| page | integer | no | Page number (1-based). If provided, overrides offset/limit |
| page_size | integer | no | Number of proposals per page |
| offset | integer | no | Number of proposals to skip (alternative to page-based pagination) |
| limit | integer | no | Maximum number of proposals to return (alternative to page_size) |
Get detailed information about a specific governance proposal including its content and voting history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| proposal_id | integer | yes | The governance proposal ID |
Get staking balances for an address, including active and pending stakes broken down by validator group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The address to check staking balances for. |
Get information about pending stakes that can be activated for earning rewards.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | The address to check activatable stakes for. |
Get information about all validator groups, including their members, votes, capacity, and performance metrics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (1-based). If provided, overrides offset/limit |
| page_size | integer | no | Number of validator groups per page |
| offset | integer | no | Number of validator groups to skip (alternative to page-based pagination) |
| limit | integer | no | Maximum number of validator groups to return (alternative to page_size) |
Get detailed information about a specific validator group including its members and performance data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_address | string | yes | The validator group address. |
Get network-wide staking information including total votes and participation metrics.
No parameter schema on file.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| beneficiary | string | yes | The address to send testnet funds to. |
| network | string | no | The testnet to fund on. |
| wait | boolean | no | Wait for the payout to land before returning (up to 20 seconds). Set false to return the request key immediately. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_key | string | yes | The request key returned by request_faucet_funds. |
| network | string | no | The testnet the request was made on. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Celo or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.4.3 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest6dab41ac4397f100bace57091b28885e290f3a700b224e15bd60631aee008980
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_network_status | no tags | |
| get_block | untrusted-input | untrusted-input: keyword "fetch" |
| get_transaction | no tags | |
| get_latest_blocks | no tags | |
| get_token_balance | sensitive-source | sensitive-source: keyword "get_token" |
| get_celo_balances | no tags | |
| get_stable_token_balance | no tags | |
| get_gas_fee_data | no tags | |
| get_governance_proposals | no tags | |
| get_proposal_details | no tags | |
| get_staking_balances | no tags | |
| get_activatable_stakes | no tags | |
| get_validator_groups | no tags | |
| get_validator_group_details | no tags | |
| get_total_staking_info | no tags | |
| request_faucet_funds | no tags | |
| get_faucet_request_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6dab41ac4397f100
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.3. Pin a release below and the command asks for exactly that one.
0.4.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Celo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.