build-web3 vs Chain.Love MCP
build-web3 is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
build-web3 is a plugin bundle for AI coding tools published by Quicknode. No marketplace we read lists it any more. Chain.Love MCP is an MCP server published by app.chain.love. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Chain.Love MCP | |
|---|---|---|
| Community marketplace quicknode/agent-plugins | Removed on 2026-10-20 Version: 1.0.2 Forks (GitHub): 5 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 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 | build-web3no longer listed · | Chain.Love MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.quicknode.com/mcp) | Remote server (app.chain.love/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/quicknode/agent-plugins | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (5 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of build-web3
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Specialized agents for blockchain development, smart contracts, and Web3 applications
-
Blockchain RPC access for AI agents — 200+ networks via DRPC MCP gateway
-
agentforge io.github.acarchidi/agentforge
DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.
-
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
-
Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.
-
Screen Base ERC-20 tokens, inspect wallets, simulate txs, price gas. $0.01 in USDC.
What each says it does
build-web3
Build and improve Web3 apps with your AI agent, with optional Quicknode infrastructure for RPC access, live onchain events, historical data, and wallet-paid API access.
Chain.Love MCP
Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.
How to run each
build-web3
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Chain.Love MCP As a remote MCP server
claude mcp add --transport http chainlove-mcp https://app.chain.love/mcp --header "x-chainlove-cred-github: <YOUR_X_CHAINLOVE_CRED_GITHUB>"Requires: x-chainlove-cred-github header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Chain.Love 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
Neither one's marketplaces publish the settings it asks for.
What it can do: build-web3 · What it can do: Chain.Love MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.