VeyraX vs io.github.tang-vu/keryx
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.tang-vu/keryx is an MCP server published by tang-vu. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. 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 |  io.github.tang-vu/keryx |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 495 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.34 Downloads/month (npm): 4 572 Downloads/week (npm): 2 196 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.34 Downloads/month (npm): 4 572 Downloads/week (npm): 2 196 Forks (GitHub): 1 Stars (GitHub): 4 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 | io.github.tang-vu/keryx |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 48 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 18 495 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server or your machine |
| 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 (differs) | Not stated | MIT |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/tang-vu/keryx |
| Changes in the last 7 days (differs) | 0 | 18 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
io.github.tang-vu/keryx
Budgeted research with cited evidence and visible payment state on the selected Arc network.
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)
io.github.tang-vu/keryx As a remote MCP server
claude mcp add --transport http keryx https://keryx.cc/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.tang-vu/keryx has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.tang-vu/keryx publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.tang-vu/keryx publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: io.github.tang-vu/keryx · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.