VeyraX vs io.github.VictoriaMetrics-Community/mcp-victoriatraces
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.VictoriaMetrics-Community/mcp-victoriatraces is an MCP server published by VictoriaMetrics-Community. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-30. 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.VictoriaMetrics-Community/mcp-victoriatraces |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 771 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Listed Version: sha256:72b3227c0385 Forks (GitHub): 7 Stars (GitHub): 19 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Forks (GitHub): 7 Stars (GitHub): 19 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.VictoriaMetrics-Community/mcp-victoriatraces |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 48 (better) | 19 (worse) |
| Pulls (Docker Hub) (differs) | 18 771 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 7 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | On your machine (ghcr.io/victoriametrics-community/mcp-victoriatraces:1.5.0) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | 6 |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 7, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/victoriametrics-community/mcp-victoriatraces |
| Changes in the last 7 days (differs) | 4 | 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.
io.github.VictoriaMetrics-Community/mcp-victoriatraces
MCP Server for VictoriaTraces. Provides integration with VictoriaTraces API and documentation
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.VictoriaMetrics-Community/mcp-victoriatraces As a local MCP server: Docker image
claude mcp add --env "VT_INSTANCE_BEARER_TOKEN=<YOUR_VT_INSTANCE_BEARER_TOKEN>" --env "VT_INSTANCE_ENTRYPOINT=<YOUR_VT_INSTANCE_ENTRYPOINT>" --transport stdio mcp-victoriatraces -- docker run -i --rm -e VT_INSTANCE_BEARER_TOKEN -e VT_INSTANCE_ENTRYPOINT ghcr.io/victoriametrics-community/mcp-victoriatraces:1.5.0Requires: VT_INSTANCE_BEARER_TOKEN (secret), VT_INSTANCE_ENTRYPOINT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only VeyraX declares
get_flowget_toolstool_call
Only io.github.VictoriaMetrics-Community/mcp-victoriatraces declares
dependenciesdocumentationservice_operationsservicestracetraces
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only VeyraX asks for
VEYRAX_API_KEY (secret)
Only io.github.VictoriaMetrics-Community/mcp-victoriatraces asks for
MCP_DISABLED_TOOLSMCP_HEARTBEAT_INTERVALMCP_LISTEN_ADDRMCP_SERVER_MODEVT_INSTANCE_BEARER_TOKEN (secret)VT_INSTANCE_ENTRYPOINTVT_INSTANCE_HEADERS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: VeyraX · What it can do: io.github.VictoriaMetrics-Community/mcp-victoriatraces · 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.