ChainRPC MCP vs io.github.sudzikcoin/mcp-server
ChainRPC MCP is an MCP server published by John0n1. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.sudzikcoin/mcp-server is an MCP server published by sudzikcoin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  ChainRPC MCP |  io.github.sudzikcoin/mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.2 Downloads/month (npm): 145 Downloads/week (npm): 17 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.2.2 Downloads/month (npm): 138 Downloads/week (npm): 29 Forks (GitHub): 0 Stars (GitHub): 2 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 | ChainRPC MCP | io.github.sudzikcoin/mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 2 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (chainrpc-mcp.mitander.io/mcp) | On your machine (@suverselabs/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/john0n1/chainrpc-mcp | github.com/sudzikcoin/suverse-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-15 | 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
ChainRPC MCP
Safety-first EVM and Bitcoin RPC tools for balances, contracts, blocks, and transactions
io.github.sudzikcoin/mcp-server
Pay-per-call x402 tools: crypto market pulse, wallet reputation, token check, endpoint search.
How to run each
ChainRPC MCP As a remote MCP server
claude mcp add --transport http chainrpc-mcp https://chainrpc-mcp.mitander.io/mcpio.github.sudzikcoin/mcp-server As a local MCP server: npm package
claude mcp add --transport stdio io-github-sudzikcoin-mcp-server -- npx -y @suverselabs/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChainRPC MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.sudzikcoin/mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: ChainRPC MCP · What it can do: io.github.sudzikcoin/mcp-server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.