Ext Ops Panel
Open dashboard
Comparison

io.github.DELIGHT-LABS/walletconnect-mcp vs Vibes-Coded Agent Tools

io.github.DELIGHT-LABS/walletconnect-mcp is an MCP server published by DELIGHT-LABS. Marketplaces we read that list it: 1 (Official MCP Registry). Vibes-Coded Agent Tools is an MCP server published by doteyeso-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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

Where each is published
Marketplaceio.github.DELIGHT-LABS/walletconnect-mcpVibes-Coded Agent Tools
Official MCP Registry Listed
Version: 0.0.4
Downloads/month (npm): 325
Downloads/week (npm): 130
Not marked · First seen
Listed
Version: 1.30.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 3 (last published figure)
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

io.github.DELIGHT-LABS/walletconnect-mcp vs Vibes-Coded Agent Tools
Factio.github.DELIGHT-LABS/walletconnect-mcpVibes-Coded Agent Tools
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3 (last published figure)
Forks (GitHub) (differs)No figure on GitHub0 (last published figure)
Last release (differs)Not published2026-10-30
Where it runs (differs)On your machine (walletconnect-mcp)Remote server (vibes-coded-mcp-production.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/delight-labs/walletconnect-mcpgithub.com/doteyeso-ops/vibescoded
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 34 h ago returned HTTP 406

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.DELIGHT-LABS/walletconnect-mcp

In its own words, on Official MCP Registry:

Non-custodial EVM wallet bridge over WalletConnect: balances, signing, transactions.

Vibes-Coded Agent Tools

In its own words, on Official MCP Registry:

Web search, page-to-markdown, memory, leases and proof for agents. x402, no signup.

How to run each

io.github.DELIGHT-LABS/walletconnect-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio walletconnect-mcp -- npx -y walletconnect-mcp

Vibes-Coded Agent Tools As a remote MCP server

Claude Code
claude mcp add --transport http mcp-server-vibes-coded https://vibes-coded-mcp-production.up.railway.app/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Vibes-Coded Agent Tools 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: io.github.DELIGHT-LABS/walletconnect-mcp · What it can do: Vibes-Coded Agent Tools · 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.

Where the data comes from: how the catalog is built