VeyraX vs redfox-mcp-core
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). redfox-mcp-core is an MCP server published by redfox-data. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. 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 |  redfox-mcp-core |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 897 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (PyPI): 1 980 Downloads/week (PyPI): 635 Forks (GitHub): 2 Stars (GitHub): 2 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 | redfox-mcp-core |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 18 897 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 2 (worse) |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | On your machine (mcp/veyrax) | On your machine (redfox-mcp-core) |
| 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 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/redfox-data/redfox-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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.
redfox-mcp-core
Shared runtime for RedFoxHub MCP servers: client management, multi-tenant auth, async task polling, stdio/HTTP serving
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)
redfox-mcp-core
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of redfox-mcp-core publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of redfox-mcp-core publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: redfox-mcp-core · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.