Ext Ops Panel
Open dashboard
Comparison

AWS CloudTrail vs io.github.VictoriaMetrics-Community/mcp-victorialogs

AWS CloudTrail is an MCP server published by awslabs. 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-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

Where each is published
MarketplaceAWS CloudTrailio.github.VictoriaMetrics-Community/mcp-victorialogs
Docker MCP Catalog Listed
Version: sha256:7952825f42e5
Forks (GitHub): 1 817
Pulls (Docker Hub): 15 605
Stars (Docker Hub): 0
Stars (GitHub): 9 798
Not marked · First seen
Listed
Version: sha256:d2a0826def2b
Forks (GitHub): 29
Stars (GitHub): 103
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.8.0
Forks (GitHub): 29
Stars (GitHub): 103
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

AWS CloudTrail vs io.github.VictoriaMetrics-Community/mcp-victorialogs
FactAWS CloudTrailio.github.VictoriaMetrics-Community/mcp-victorialogs
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 798 (better)103 (worse)
Pulls (Docker Hub) (differs)15 605No figure on Docker Hub
Forks (GitHub) (differs)1 817 (better)29 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cloudtrail-mcp-server)On your machine (ghcr.io/victoriametrics-community/mcp-victorialogs:1.8.0)
Transportstdiostdio
Tools it declares (differs)511
Environment variables it asks for (differs)1, secrets among them: 07, secrets among them: 1
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/awslabs/mcpgithub.com/victoriametrics-community/mcp-victorialogs
Changes in the last 7 days00
First seen2026-10-112026-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

AWS CloudTrail

In its own words, on Docker MCP Catalog:

AWS CloudTrail audit logging and monitoring.

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

AWS CloudTrail As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio awslabs-cloudtrail -- docker run -i --rm mcp/cloudtrail-mcp-server

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 AWS CloudTrail declares

  • get_query_results
  • get_query_status
  • lake_query
  • list_event_data_stores
  • lookup_events

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 AWS CloudTrail asks for

  • AWS_PROFILE

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: AWS CloudTrail · 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built