VeyraX vs Vidova
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vidova is an MCP server published by vidova.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |   Vidova |
|---|---|---|
| Docker MCP Catalog | Not seen in the last pass Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 911 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | Vidova |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 18 911 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (mcp.vidova.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/youneslaaroussi/vidova-skills |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 36 h ago returned HTTP 405 |
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.
Vidova
Agentic AI video editor: edit a real timeline, generate clips, music and voice, then render.
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)
Vidova As a remote MCP server
claude mcp add --transport http vidova https://mcp.vidova.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vidova has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Vidova publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Vidova publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: Vidova · 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.