io.github.CyberPunk11147/cyberwarex-chain-data vs io.github.junct-bot/wormhole-mcp
io.github.CyberPunk11147/cyberwarex-chain-data is an MCP server published by CyberPunk11147. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.junct-bot/wormhole-mcp is an MCP server published by junct-bot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  io.github.CyberPunk11147/cyberwarex-chain-data |  io.github.junct-bot/wormhole-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | io.github.CyberPunk11147/cyberwarex-chain-data | io.github.junct-bot/wormhole-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/cyberpunk11147/cyberwarex-chain-data:1.5.0) | Remote server (wormhole.mcp.junct.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cyberpunk11147/cyberwarex-mcp | github.com/junct-bot/wormhole-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-12 |
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
io.github.CyberPunk11147/cyberwarex-chain-data
EVM onchain data: wallet, token, price, gas, transactions, ENS across 5 chains.
io.github.junct-bot/wormhole-mcp
Wormhole - 69 tools for cross-chain transfers and bridge data
How to run each
io.github.CyberPunk11147/cyberwarex-chain-data As a local MCP server: Docker image
claude mcp add --env "CHAIN_X_PAYMENT=<YOUR_CHAIN_X_PAYMENT>" --transport stdio cyberwarex-chain-data -- docker run -i --rm -e CHAIN_X_PAYMENT ghcr.io/cyberpunk11147/cyberwarex-chain-data:1.5.0Requires: CHAIN_X_PAYMENT (secret)
io.github.junct-bot/wormhole-mcp As a remote MCP server
claude mcp add --transport http wormhole-mcp https://wormhole.mcp.junct.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.junct-bot/wormhole-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.junct-bot/wormhole-mcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.CyberPunk11147/cyberwarex-chain-data · What it can do: io.github.junct-bot/wormhole-mcp · 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.