ChainWeaver vs ChainRay
ChainWeaver is an MCP server published by dgenio. Marketplaces we read that list it: 1 (Official MCP Registry). ChainRay is an MCP server published by chainray.online. 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 |  ChainWeaver |  ChainRay |
|---|---|---|
| Official MCP Registry | Listed Version: 0.12.1 Downloads/month (PyPI): 117 Downloads/week (PyPI): 30 Forks (GitHub): 2 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 2.5.8 No figure published 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 | ChainWeaver | ChainRay |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (chainweaver) | Remote server (chainray.online/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dgenio/chainweaver | Not stated |
| 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-28 |
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
ChainWeaver
Expose deterministic ChainWeaver flows as MCP tools without LLM calls between steps.
ChainRay
Multi-chain on-chain intelligence for AI agents through a public remote MCP server.
How to run each
ChainWeaver As a local MCP server: PyPI package
claude mcp add --transport stdio chainweaver -- uvx --from "chainweaver[mcp]" chainweaver serve "<YOUR_FLOW_FILE>"Requires: <flow_file>
ChainRay As a remote MCP server
claude mcp add --transport http chainray https://chainray.online/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChainRay 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
Neither one's marketplaces publish the settings it asks for.
What it can do: ChainWeaver · What it can do: ChainRay · 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.