onchaincheck vs Celo MCP Server
onchaincheck is an MCP server published by lx1112. Marketplaces we read that list it: 1 (Official MCP Registry). Celo MCP Server is an MCP server published by celo.org. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Celo MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.4.3 Downloads/month (PyPI): 855 Downloads/week (PyPI): 323 Forks (GitHub): 15 Stars (GitHub): 5 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.4.3 Downloads/month (PyPI): 855 Downloads/week (PyPI): 323 Forks (GitHub): 15 Stars (GitHub): 5 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | onchaincheck | Celo MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 15 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Remote server (onchaincheck.dev/mcp) | On your machine (celo-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/celo-org/celo-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-08 | 2026-10-12 |
| Endpoint at the last check (differs) | Status out of date: last check 41 h ago returned HTTP 406 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
onchaincheck
100+ pay-per-call tools: token risk, wallet sanctions screening, onchain data, web, company, AI
Celo MCP Server
Query Celo blockchain data: blocks, tokens, NFTs, contracts, governance and staking
How to run each
onchaincheck As a remote MCP server
claude mcp add --transport http onchaincheck https://onchaincheck.dev/mcpCelo MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio celo-mcp -- uvx celo-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only onchaincheck has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Celo MCP Server nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: onchaincheck · What it can do: Celo MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.