VeyraX vs NV oOS MCP Bridge
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). NV oOS MCP Bridge is an MCP server published by nvdigitalsolutions. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  NV oOS MCP Bridge |
|---|---|---|
| Docker MCP Catalog | Not seen in the last pass Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 659 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0-alpha.4 Downloads/month (npm): 657 Downloads/week (npm): 270 Forks (GitHub): 2 Stars (GitHub): 7 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 | NV oOS MCP Bridge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 7 (worse) |
| Pulls (Docker Hub) (differs) | 18 659 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 2 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | On your machine (@nvdigitalsolutions/nvoos-mcp-bridge) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/nvdigitalsolutions/mcp-ai-wpoos |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
NV oOS MCP Bridge
Stdio relay connecting Zed, Claude Desktop, Cursor and Codex to NV oOS WordPress MCP endpoints.
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)
NV oOS MCP Bridge As a local MCP server: npm package
claude mcp add --env "MCP_AI_BASE_URL=<YOUR_MCP_AI_BASE_URL>" --env "MCP_AI_TOKEN=<YOUR_MCP_AI_TOKEN>" --transport stdio nvoos-mcp-bridge -- npx -y @nvdigitalsolutions/nvoos-mcp-bridgeRequires: MCP_AI_BASE_URL, MCP_AI_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of NV oOS MCP Bridge publish no list of tools, so we do not compare tools.
Settings each asks for
Only VeyraX asks for
VEYRAX_API_KEY (secret)
Only NV oOS MCP Bridge asks for
MCP_AI_BASE_URLMCP_AI_HTTP_TIMEOUTMCP_AI_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: VeyraX · What it can do: NV oOS MCP Bridge · 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.