@zackbart/connecta vs X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router
@zackbart/connecta is an MCP server published by zackbart. Marketplaces we read that list it: 1 (npm registry (MCP servers)). X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router is an MCP server published by x402broker.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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 |  @zackbart/connecta |  X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.47.1 Downloads/month (npm): 2 970 Downloads/week (npm): 1 197 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 7.0.17 Forks (GitHub): 0 Stars (GitHub): 0 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 | @zackbart/connecta | X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-13 (better) | 2026-10-21 (worse) |
| Where it runs (differs) | On your machine (@zackbart/connecta) | Remote server (x402broker.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/zackbart/connecta | github.com/robertoyanguas-ops/assay |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-21 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 13 h 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
@zackbart/connecta
One MCP to rule them all — a single MCP endpoint aggregating many downstream connectors behind a code-first surface of six meta-tools.
X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router
Single-connection MCP gateway discovering and executing 490+ verified MCP & A2A tools.
How to run each
@zackbart/connecta
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router As a remote MCP server
claude mcp add --transport http mcp-gateway https://x402broker.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of @zackbart/connecta nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: @zackbart/connecta · What it can do: X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.