io.github.VictoriaMetrics-Community/mcp-victorialogs vs io.github.VictoriaMetrics/mcp-vmanomaly
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). io.github.VictoriaMetrics/mcp-vmanomaly is an MCP server published by VictoriaMetrics. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |   io.github.VictoriaMetrics-Community/mcp-victorialogs | io.github.VictoriaMetrics/mcp-vmanomaly |
|---|---|---|
| Official MCP Registry | Listed Version: 1.8.0 Forks (GitHub): 31 Stars (GitHub): 107 Not marked · First seen |
Listed Version: 0.5.1 Forks (GitHub): 3 Stars (GitHub): 11 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:d2a0826def2b Forks (GitHub): 31 Stars (GitHub): 107 Not marked · First seen |
Not listed |
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 | io.github.VictoriaMetrics-Community/mcp-victorialogs | io.github.VictoriaMetrics/mcp-vmanomaly |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 107 (better) | 11 (worse) |
| Forks (GitHub) (differs) | 31 (better) | 3 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0) | On your machine (ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 11 | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 1 | 12, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/victoriametrics-community/mcp-victorialogs | github.com/victoriametrics/mcp-vmanomaly |
| 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
io.github.VictoriaMetrics-Community/mcp-victorialogs
MCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation
io.github.VictoriaMetrics/mcp-vmanomaly
MCP Server for vmanomaly - VictoriaMetrics anomaly detection
How to run each
io.github.VictoriaMetrics-Community/mcp-victorialogs As a local MCP server: Docker image
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.0Requires: VL_INSTANCE_BEARER_TOKEN (secret), VL_INSTANCE_ENTRYPOINT
io.github.VictoriaMetrics/mcp-vmanomaly As a local MCP server: Docker image
claude mcp add --env "VMANOMALY_BEARER_TOKEN=<YOUR_VMANOMALY_BEARER_TOKEN>" --env "VMANOMALY_ENDPOINT=<YOUR_VMANOMALY_ENDPOINT>" --transport stdio mcp-vmanomaly -- docker run -i --rm -e VMANOMALY_BEARER_TOKEN -e VMANOMALY_ENDPOINT ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1Requires: VMANOMALY_BEARER_TOKEN (secret), VMANOMALY_ENDPOINT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.VictoriaMetrics/mcp-vmanomaly publish no list of tools, so we do not compare tools.
Settings each asks for
Only io.github.VictoriaMetrics-Community/mcp-victorialogs asks for
VL_INSTANCE_BEARER_TOKEN (secret)VL_INSTANCE_ENTRYPOINTVL_INSTANCE_HEADERS
Only io.github.VictoriaMetrics/mcp-vmanomaly asks for
MCP_DISABLE_RESOURCESMCP_ENABLED_TOOLSMCP_LOG_FILEMCP_LOG_LEVELVMANOMALY_BEARER_TOKEN (secret)VMANOMALY_BEARER_TOKEN_FILEVMANOMALY_ENDPOINTVMANOMALY_HEADERS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.VictoriaMetrics-Community/mcp-victorialogs · What it can do: io.github.VictoriaMetrics/mcp-vmanomaly · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.