Comparison

VeyraX vs io.github.VictoriaMetrics-Community/mcp-victorialogs

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.VictoriaMetrics-Community/mcp-victorialogs 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-17. 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

Where each is published
Marketplace	VeyraX	io.github.VictoriaMetrics-Community/mcp-victorialogs
Docker MCP Catalog	Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 434 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen 2026-10-11	Listed Version: sha256:d2a0826def2b Forks (GitHub): 29 Stars (GitHub): 102 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 1.8.0 Forks (GitHub): 29 Stars (GitHub): 102 Not marked · First seen 2026-10-11

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

VeyraX vs io.github.VictoriaMetrics-Community/mcp-victorialogs
Fact	VeyraX	io.github.VictoriaMetrics-Community/mcp-victorialogs
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	48 (worse)	102 (better)
Pulls (Docker Hub) (differs)	18 434	No figure on Docker Hub
Forks (GitHub) (differs)	19 (worse)	29 (better)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/veyrax)	On your machine (ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0)
Transport	stdio	stdio
Tools it declares (differs)	3	11
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-victorialogs
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

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

io.github.VictoriaMetrics-Community/mcp-victorialogs

In its own words, on Official MCP Registry:

MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation

How to run each

VeyraX As a local MCP server: Docker image

Claude Code

claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

io.github.VictoriaMetrics-Community/mcp-victorialogs As a local MCP server: Docker image

Claude Code

claude mcp add --env "VL_INSTANCE_BEARER_TOKEN=<YOUR_VL_INSTANCE_BEARER_TOKEN>" --env "VL_INSTANCE_ENTRYPOINT=<YOUR_VL_INSTANCE_ENTRYPOINT>" --transport stdio mcp-victorialogs -- docker run -i --rm -e VL_INSTANCE_BEARER_TOKEN -e VL_INSTANCE_ENTRYPOINT ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0

Requires: VL_INSTANCE_BEARER_TOKEN (secret), VL_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_flow
get_tools
tool_call

Only io.github.VictoriaMetrics-Community/mcp-victorialogs declares

documentation
field_names
field_values
flags
query
stats_query
stats_query_range
stream_field_names
stream_field_values
stream_ids
streams

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-victorialogs asks for

MCP_DISABLED_TOOLS
MCP_HEARTBEAT_INTERVAL
MCP_LISTEN_ADDR
MCP_SERVER_MODE
VL_INSTANCE_BEARER_TOKEN (secret)
VL_INSTANCE_ENTRYPOINT
VL_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-victorialogs · 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 2026-10-17. We publish no contact details for plugin publishers.