World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Descripción del creador (original en inglés)
MCP Server for vmanomaly - VictoriaMetrics anomaly detection
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
VMANOMALY_ENDPOINT, VMANOMALY_BEARER_TOKEN, VMANOMALY_BEARER_TOKEN_FILE, VMANOMALY_HEADERS, MCP_SERVER_MODE, MCP_LISTEN_ADDR, MCP_LOG_LEVEL, MCP_LOG_FILE, MCP_ENABLED_TOOLS, MCP_DISABLED_TOOLS, MCP_HEARTBEAT_INTERVAL, MCP_DISABLE_RESOURCESLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"vmanomaly": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VMANOMALY_ENDPOINT",
"-e",
"VMANOMALY_BEARER_TOKEN",
"-e",
"VMANOMALY_BEARER_TOKEN_FILE",
"-e",
"VMANOMALY_HEADERS",
"-e",
"MCP_SERVER_MODE",
"-e",
"MCP_LISTEN_ADDR",
"-e",
"MCP_LOG_LEVEL",
"-e",
"MCP_LOG_FILE",
"-e",
"MCP_ENABLED_TOOLS",
"-e",
"MCP_DISABLED_TOOLS",
"-e",
"MCP_HEARTBEAT_INTERVAL",
"-e",
"MCP_DISABLE_RESOURCES",
"ghcr.io/victoriametrics/mcp-vmanomaly:0.6.0"
],
"env": {
"VMANOMALY_ENDPOINT": "your-value",
"VMANOMALY_BEARER_TOKEN": "your-value",
"VMANOMALY_BEARER_TOKEN_FILE": "your-value",
"VMANOMALY_HEADERS": "your-value",
"MCP_SERVER_MODE": "your-value",
"MCP_LISTEN_ADDR": "your-value",
"MCP_LOG_LEVEL": "your-value",
"MCP_LOG_FILE": "your-value",
"MCP_ENABLED_TOOLS": "your-value",
"MCP_DISABLED_TOOLS": "your-value",
"MCP_HEARTBEAT_INTERVAL": "your-value",
"MCP_DISABLE_RESOURCES": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add vmanomaly --env VMANOMALY_ENDPOINT=your-value --env VMANOMALY_BEARER_TOKEN=your-value --env VMANOMALY_BEARER_TOKEN_FILE=your-value --env VMANOMALY_HEADERS=your-value --env MCP_SERVER_MODE=your-value --env MCP_LISTEN_ADDR=your-value --env MCP_LOG_LEVEL=your-value --env MCP_LOG_FILE=your-value --env MCP_ENABLED_TOOLS=your-value --env MCP_DISABLED_TOOLS=your-value --env MCP_HEARTBEAT_INTERVAL=your-value --env MCP_DISABLE_RESOURCES=your-value -- docker run -i --rm -e VMANOMALY_ENDPOINT -e VMANOMALY_BEARER_TOKEN -e VMANOMALY_BEARER_TOKEN_FILE -e VMANOMALY_HEADERS -e MCP_SERVER_MODE -e MCP_LISTEN_ADDR -e MCP_LOG_LEVEL -e MCP_LOG_FILE -e MCP_ENABLED_TOOLS -e MCP_DISABLED_TOOLS -e MCP_HEARTBEAT_INTERVAL -e MCP_DISABLE_RESOURCES ghcr.io/victoriametrics/mcp-vmanomaly:0.6.0Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"vmanomaly": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VMANOMALY_ENDPOINT",
"-e",
"VMANOMALY_BEARER_TOKEN",
"-e",
"VMANOMALY_BEARER_TOKEN_FILE",
"-e",
"VMANOMALY_HEADERS",
"-e",
"MCP_SERVER_MODE",
"-e",
"MCP_LISTEN_ADDR",
"-e",
"MCP_LOG_LEVEL",
"-e",
"MCP_LOG_FILE",
"-e",
"MCP_ENABLED_TOOLS",
"-e",
"MCP_DISABLED_TOOLS",
"-e",
"MCP_HEARTBEAT_INTERVAL",
"-e",
"MCP_DISABLE_RESOURCES",
"ghcr.io/victoriametrics/mcp-vmanomaly:0.6.0"
],
"env": {
"VMANOMALY_ENDPOINT": "your-value",
"VMANOMALY_BEARER_TOKEN": "your-value",
"VMANOMALY_BEARER_TOKEN_FILE": "your-value",
"VMANOMALY_HEADERS": "your-value",
"MCP_SERVER_MODE": "your-value",
"MCP_LISTEN_ADDR": "your-value",
"MCP_LOG_LEVEL": "your-value",
"MCP_LOG_FILE": "your-value",
"MCP_ENABLED_TOOLS": "your-value",
"MCP_DISABLED_TOOLS": "your-value",
"MCP_HEARTBEAT_INTERVAL": "your-value",
"MCP_DISABLE_RESOURCES": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"vmanomaly": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"VMANOMALY_ENDPOINT",
"-e",
"VMANOMALY_BEARER_TOKEN",
"-e",
"VMANOMALY_BEARER_TOKEN_FILE",
"-e",
"VMANOMALY_HEADERS",
"-e",
"MCP_SERVER_MODE",
"-e",
"MCP_LISTEN_ADDR",
"-e",
"MCP_LOG_LEVEL",
"-e",
"MCP_LOG_FILE",
"-e",
"MCP_ENABLED_TOOLS",
"-e",
"MCP_DISABLED_TOOLS",
"-e",
"MCP_HEARTBEAT_INTERVAL",
"-e",
"MCP_DISABLE_RESOURCES",
"ghcr.io/victoriametrics/mcp-vmanomaly:0.6.0"
],
"env": {
"VMANOMALY_ENDPOINT": "your-value",
"VMANOMALY_BEARER_TOKEN": "your-value",
"VMANOMALY_BEARER_TOKEN_FILE": "your-value",
"VMANOMALY_HEADERS": "your-value",
"MCP_SERVER_MODE": "your-value",
"MCP_LISTEN_ADDR": "your-value",
"MCP_LOG_LEVEL": "your-value",
"MCP_LOG_FILE": "your-value",
"MCP_ENABLED_TOOLS": "your-value",
"MCP_DISABLED_TOOLS": "your-value",
"MCP_HEARTBEAT_INTERVAL": "your-value",
"MCP_DISABLE_RESOURCES": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
VMANOMALY_BEARER_TOKEN_FILE envVMANOMALY_HEADERS envMCP_SERVER_MODE envMCP_LISTEN_ADDR envMCP_LOG_LEVEL envMCP_LOG_FILE envMCP_ENABLED_TOOLS envMCP_DISABLED_TOOLS envMCP_HEARTBEAT_INTERVAL envMCP_DISABLE_RESOURCES envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 11 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub VictoriaMetrics, dueña del repo
Último cambio de código: hace 6 días
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 2 de 2 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: VMANOMALY_ENDPOINT, VMANOMALY_BEARER_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez hace 6 días, y la última versión (0.6.0) llegó al registro hace 6 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: World Monitor, Claude Flow, Tldraw
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
The implementation of Model Context Protocol (MCP) server for vmanomaly - VictoriaMetrics Anomaly Detection product.
This provides seamless integration with vmanomaly REST API and documentation for AI-assisted anomaly detection, model management, and observability insights.
This MCP server enables AI assistants like Claude to interact with vmanomaly for:
vmanomaly server health and build informationvmanomaly YAML configurationsvmalert alerting rules based on anomaly score metrics to simplify alerting setupvmanomaly documentation with fuzzy matchingThe MCP server contains embedded up-to-date vmanomaly documentation and is able to search it without online access.
The quality of the MCP Server and its responses depends very much on the capabilities of your client and the quality of the model you are using.
vmanomaly instance with REST API access:go install github.com/VictoriaMetrics/mcp-vmanomaly/cmd/mcp-vmanomaly@vX.Y.Z
Replace vX.Y.Z with the exact release you have reviewed.
Download the latest release from Releases page and put it to your PATH.
Example for Linux x86_64 (other architectures and platforms are also available). Select an explicit release rather than a mutable latest URL, verify its checksum, and then verify its GitHub build-provenance attestation:
version=vX.Y.Z
archive=mcp-vmanomaly_Linux_x86_64.tar.gz curl -fLO "https://github.com/VictoriaMetrics/mcp-vmanomaly/releases/download/${version}/${archive}" curl -fLO "https://github.com/VictoriaMetrics/mcp-vmanomaly/releases/download/${version}/checksums.txt" grep " ${archive}$" checksums.txt | sha256sum --check - gh attestation verify "${archive}" --repo VictoriaMetrics/mcp-vmanomaly tar axvf "${archive}" ./mcp-vmanomaly --version
Build-provenance attestations are available for releases produced by the hardened release workflow. Release tags must be annotated, cryptographically signed, and marked as verified by GitHub before that workflow publishes artifacts.
You can run vmanomaly MCP Server using Docker.
This is the easiest way to get started without needing to install Go or build from source.
docker run -d --name mcp-vmanomaly \
--add-host=host.docker.internal:host-gateway \ -e VMANOMALY_ENDPOINT=http://host.docker.internal:8490 \ -e MCP_SERVER_MODE=http \ -e MCP_LISTEN_ADDR=:8080 \ -p 127.0.0.1:8080:8080 \ ghcr.io/victoriametrics/mcp-vmanomaly:vX.Y.Z
Replace vX.Y.Z and the environment variables with your own parameters. When both services run in Docker, prefer a private Docker network and use the vmanomaly service name as the endpoint.
Note that the MCP_SERVER_MODE=http flag is used to enable Streamable HTTP mode. More details about server modes can be found in the Configuration section.
See available docker images in github registry.
Also see Using Docker instead of binary section for more details about using Docker with MCP server with clients in stdio mode.
For building binary from source code you can use the following approach:
git clone https://github.com/VictoriaMetrics/mcp-vmanomaly.git
cd mcp-vmanomaly
make build
docker build -t mcp-vmanomaly .
For local UI/Copilot testing from the vmanomaly repository, build with a local tag:
docker build -t mcp-vmanomaly:local .
Then run the vmanomaly repository helper with:
MCP_VMANOMALY_IMAGE=mcp-vmanomaly:local bin/run-mcp-http.sh
MCP Server for vmanomaly is configured via environment variables:
| Variable | Description | Required | Default | Allowed values |
|---|---|---|---|---|
VMANOMALY_ENDPOINT | vmanomaly server endpoint URL (e.g., http://localhost:8490) | Yes | - | - |
VMANOMALY_BEARER_TOKEN | Bearer token for authenticating with vmanomaly API (mutually exclusive with the token file) | No | - | - |
VMANOMALY_BEARER_TOKEN_FILE | Path to a bearer-token file, suitable for mounted container/orchestrator secrets | No | - | - |
VMANOMALY_HEADERS | Custom HTTP headers for requests (comma-separated key=value pairs, e.g., X-Custom=value1,X-Auth=value2) | No | - | - |
VMANOMALY_REQUEST_TIMEOUT | HTTP timeout for calls from MCP to vmanomaly, e.g. 60s | No | 30s | - |
VMANOMALY_TLS_CA_FILE | PEM CA bundle added to the system trust store to verify the vmanomaly server certificate | No | - | - |
VMANOMALY_TLS_CA_CERT | Same as VMANOMALY_TLS_CA_FILE, but the PEM content itself, for runtimes without file mounts; mutually exclusive with VMANOMALY_TLS_CA_FILE | No | - | - |
VMANOMALY_TLS_CERT_FILE | PEM client certificate for vmanomaly servers that require mutual TLS; set together with the key file | No | - | - |
VMANOMALY_TLS_KEY_FILE | PEM private key for VMANOMALY_TLS_CERT_FILE | No | - | - |
VMANOMALY_TLS_INSECURE_SKIP_VERIFY | Skip server certificate verification. Insecure, for development and testing only | No | false | false, true |
MCP_SERVER_MODE | Server operation mode. See Modes for details. | No | stdio | stdio, http, sse |
MCP_LISTEN_ADDR | Address for HTTP server to listen on | No | localhost:8080 | - |
MCP_ENABLED_TOOLS | Positive comma-separated tool allowlist; empty enables all registered tools | No | - | - |
MCP_DISABLED_TOOLS | Comma-separated tool denylist; takes precedence over the allowlist | No | - | - |
MCP_DISABLE_RESOURCES | Disable all resources (documentation search will continue to work) | No | false | false, true |
MCP_HEARTBEAT_INTERVAL | Heartbeat interval for streamable-http protocol (keeps connection alive through network infrastructure) | No | 30s | - |
MCP_LOG_LEVEL | Log level: debug (verbose), info (default), warn, or error | No | info | - |
MCP_LOG_FILE | Log file path (empty = stderr) | No | stderr | - |
Use an https:// URL in VMANOMALY_ENDPOINT. Server certificates are verified against the system trust store. For a private CA, set VMANOMALY_TLS_CA_FILE, or VMANOMALY_TLS_CA_CERT with the PEM content when the runtime cannot mount files; the CA is added to the system roots. When vmanomaly requires client certificates (mutual TLS), also set VMANOMALY_TLS_CERT_FILE and VMANOMALY_TLS_KEY_FILE. VMANOMALY_TLS_INSECURE_SKIP_VERIFY=true disables server certificate verification and cannot be combined with a custom CA; use it only for development or testing. Certificates are read at startup, so restart the server after rotating them.
MCP Server supports the following modes of operation (transports):
stdio - Standard input/output mode, where the server reads commands from standard input and writes responses to standard output. This is the default mode and is suitable for local servers.http - Streamable HTTP. Server will expose the /mcp endpoint for HTTP connections.sse - Server-Sent Events. Server will expose the /sse and /message endpoints for SSE connections.[!NOTE]
The
ssetransport mode was officially deprecated from MCP
Specification (version 2025-03-26)
and was replaced by Streamable HTTP transport (
httpmode).
In future releases its support can be deprecated, use Streamable HTTP transport if your client supports it.
More info about transports you can find in M