Ext Ops Panel
Open dashboard
Comparison

VeyraX vs A.U.G.U.R Synapse · Pump & LP

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). A.U.G.U.R Synapse · Pump & LP is an MCP server published by agent.maddegen.art. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceVeyraXA.U.G.U.R Synapse · Pump & LP
Docker MCP Catalog Listed
Version: sha256:257d91533072
Forks (GitHub): 19
Pulls (Docker Hub): 18 716
Stars (Docker Hub): 4
Stars (GitHub): 48
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed, marked deprecated
Version: 2.2.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

VeyraX vs A.U.G.U.R Synapse · Pump & LP
FactVeyraXA.U.G.U.R Synapse · Pump & LP
Marketplaces that list it11
Stars (GitHub) (differs)48No figure on GitHub
Pulls (Docker Hub) (differs)18 716No figure on Docker Hub
Forks (GitHub) (differs)19No figure on GitHub
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/veyrax)Remote server (augur-trade.com/hub/mcp/pump)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/veyrax/veyrax-mcpNot stated
Changes in the last 7 days (differs)41
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

A.U.G.U.R Synapse · Pump & LP

In its own words, on Official MCP Registry:

Every pump.fun curve trade since 09-11: tape, launches, forensics, devs, odds + Meteora DLMM pools.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

A.U.G.U.R Synapse · Pump & LP As a remote MCP server

Claude Code
claude mcp add --transport http synapse-pump https://augur-trade.com/hub/mcp/pump

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

Only A.U.G.U.R Synapse · Pump & LP has a remote endpoint we check. How we check endpoints

Tools each declares

Only VeyraX has

  • get_flow
  • get_tools
  • tool_call

Only A.U.G.U.R Synapse · Pump & LP has

  • copy_backtest
  • dlmm_pool
  • dlmm_positions
  • dlmm_whales
  • pump_dev
  • pump_history
  • pump_launches
  • pump_odds
  • pump_pulse
  • pump_token
  • pump_wallet
  • smart_money

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (A.U.G.U.R Synapse · Pump & LP as of 2026-10-24). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of A.U.G.U.R Synapse · Pump & LP publish no settings it asks for, so we do not compare settings.

What it can do: VeyraX · What it can do: A.U.G.U.R Synapse · Pump & LP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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