VeyraX vs MCP Dev
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). MCP Dev is a plugin bundle for AI coding tools published by b-open-io. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 |  VeyraX |  MCP Dev |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 332 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Community marketplace b-open-io/claude-plugins | Not listed | Listed Version: 0.1.5 Forks (GitHub): 4 Stars (GitHub): 16 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 | VeyraX | MCP Dev |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 16 (worse) |
| Pulls (Docker Hub) (differs) | 18 332 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/b-open-io/prompts |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
MCP Dev
MCP servers and MCP Apps, including the json-render framework for interactive in-chat UI. Optional module for core.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
MCP Dev As a Claude Code plugin
/plugin marketplace add b-open-io/claude-plugins
/plugin install mcp-dev@b-open-ioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of MCP Dev publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of MCP Dev publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: MCP Dev · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.