Ext Ops Panel
Open dashboard
Comparison

io.github.CryptoAPIs-io/mcp-broadcast vs Vibes-Coded Agent Security and Commerce Tools

io.github.CryptoAPIs-io/mcp-broadcast is an MCP server published by CryptoAPIs-io. Marketplaces we read that list it: 1 (Official MCP Registry). Vibes-Coded Agent Security and Commerce 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-10-23. 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.CryptoAPIs-io/mcp-broadcastVibes-Coded Agent Security and Commerce Tools
Official MCP Registry Listed
Version: 0.5.0
Downloads/month (npm): 482
Downloads/week (npm): 56
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.6.1
Forks (GitHub): 0
Stars (GitHub): 3
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.CryptoAPIs-io/mcp-broadcast vs Vibes-Coded Agent Security and Commerce Tools
Factio.github.CryptoAPIs-io/mcp-broadcastVibes-Coded Agent Security and Commerce Tools
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@cryptoapis-io/mcp-broadcast)Remote server (vibes-coded-mcp-production.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/cryptoapis-io/cryptoapis-mcp-broadcastgithub.com/doteyeso-ops/mcp-server-vibes-coded
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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.CryptoAPIs-io/mcp-broadcast

In its own words, on Official MCP Registry:

MCP server for broadcasting signed raw transactions to multiple blockchains via Crypto APIs

Vibes-Coded Agent Security and Commerce Tools

In its own words, on Official MCP Registry:

Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools.

How to run each

io.github.CryptoAPIs-io/mcp-broadcast As a local MCP server: npm package

Claude Code
claude mcp add --env "CRYPTOAPIS_API_KEY=<YOUR_CRYPTOAPIS_API_KEY>" --transport stdio mcp-broadcast -- npx -y @cryptoapis-io/mcp-broadcast

Requires: CRYPTOAPIS_API_KEY (secret)

Vibes-Coded Agent Security and Commerce 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 Security and Commerce 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

The marketplaces of Vibes-Coded Agent Security and Commerce Tools publish no settings it asks for, so we do not compare settings.

What it can do: io.github.CryptoAPIs-io/mcp-broadcast · What it can do: Vibes-Coded Agent Security and Commerce 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