{"id":"victoriametrics-mcp-victorialogs","name":"mcp-victorialogs","af_score":65.8,"security_score":49.8,"reliability_score":28.8,"what_it_does":"Provides a Model Context Protocol (MCP) server that gives tools/agents access to a VictoriaLogs instance for read-only log exploration and querying (including stream/field discovery, stats, and embedded documentation search). Supports multiple MCP transports: stdio (default), SSE, and Streamable HTTP (with /mcp endpoint) and exposes Prometheus /metrics and health checks.","best_when":"You want an MCP-compatible “log knowledge + query” interface to VictoriaLogs for engineers/agents using MCP clients, preferably in an environment where you can run the server (binary/Docker) and point it at your VictoriaLogs instance.","avoid_when":"You cannot supply/secure access to the underlying VictoriaLogs endpoint (e.g., need strong tenant isolation or fine-grained authorization not documented here) or you require a fully specified REST/GraphQL/SDK contract for agents beyond MCP.","last_evaluated":"2026-03-30T15:19:44.013787+00:00","has_mcp":true,"has_api":false,"auth_methods":["VL_INSTANCE_BEARER_TOKEN (VictoriaLogs API bearer token)","VL_INSTANCE_HEADERS (custom headers for upstream requests)"],"has_free_tier":false,"known_gotchas":["Upstream access: misconfigured VL_INSTANCE_ENTRYPOINT/headers/token will lead to failures that the MCP layer may surface as generic errors.","Tool breadth: many capabilities depend on the MCP client’s support for the chosen transport (stdio vs SSE vs HTTP).","Tool disabling: MCP_DISABLED_TOOLS may remove expected tools; agents should not assume all tools are always enabled."],"error_quality":0.0}