Ext Ops Panel
Open dashboard
Comparison

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

Lumin is an MCP server published by getlumin.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-18. 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
MarketplaceLuminio.github.VictoriaMetrics-Community/mcp-victorialogs
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.8.0
Forks (GitHub): 29
Stars (GitHub): 102
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:d2a0826def2b
Forks (GitHub): 29
Stars (GitHub): 102
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

Lumin vs io.github.VictoriaMetrics-Community/mcp-victorialogs
FactLuminio.github.VictoriaMetrics-Community/mcp-victorialogs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub102
Forks (GitHub) (differs)No figure on GitHub29
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.getlumin.dev/v1/mcp)On your machine (ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published11
Environment variables it asks for (differs)Not published7, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)Not statedgithub.com/victoriametrics-community/mcp-victorialogs
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

Lumin

In its own words, on Official MCP Registry:

Read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.

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

Lumin As a remote MCP server

Claude Code
claude mcp add --transport http lumin https://api.getlumin.dev/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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.

Only Lumin has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Lumin publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Lumin publish no settings it asks for, so we do not compare settings.

What it can do: Lumin · What it can do: io.github.VictoriaMetrics-Community/mcp-victorialogs · 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.

Where the data comes from: how the catalog is built