x=hub

your toolset

    build deployment
    sign in

    mcp-vmanomaly

    mcpother official
    io.github.VictoriaMetrics/mcp-vmanomaly · v0.5.1
    deploy just this

    MCP Server for vmanomaly - VictoriaMetrics anomaly detection

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    #!/usr/bin/env bash
    # vmanomaly (io.github.VictoriaMetrics/mcp-vmanomaly), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-vmanomaly.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-vmanomaly -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1
    
    [Unit]
    Description=MCP server vmanomaly (toolset my-agent), generated by Hub
    After=network-online.target docker.service
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    SupplementaryGroups=docker
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/vmanomaly
    WorkingDirectory=/var/lib/mcp/vmanomaly
    ExecStart=/opt/mcp/my-agent/bin/vmanomaly.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/vmanomaly
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    docker run --rm -p 127.0.0.1:8101:8000 -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.5.1
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:49:16+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      vmanomaly:
        image: ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
          HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
          instead.'
        environment:
          VMANOMALY_ENDPOINT: ${VMANOMALY_ENDPOINT}
          VMANOMALY_BEARER_TOKEN: ${VMANOMALY_BEARER_TOKEN}
          VMANOMALY_BEARER_TOKEN_FILE: ${VMANOMALY_BEARER_TOKEN_FILE}
          VMANOMALY_HEADERS: ${VMANOMALY_HEADERS}
          MCP_SERVER_MODE: ${MCP_SERVER_MODE}
          MCP_LISTEN_ADDR: ${MCP_LISTEN_ADDR}
          MCP_LOG_LEVEL: ${MCP_LOG_LEVEL}
          MCP_LOG_FILE: ${MCP_LOG_FILE}
          MCP_ENABLED_TOOLS: ${MCP_ENABLED_TOOLS}
          MCP_DISABLED_TOOLS: ${MCP_DISABLED_TOOLS}
          MCP_HEARTBEAT_INTERVAL: ${MCP_HEARTBEAT_INTERVAL}
          MCP_DISABLE_RESOURCES: ${MCP_DISABLE_RESOURCES}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:49:16+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: vmanomaly
      namespace: mcp
      labels: &id001
        app: vmanomaly
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: vmanomaly
            image: ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: VMANOMALY_ENDPOINT
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: VMANOMALY_ENDPOINT
            - name: VMANOMALY_BEARER_TOKEN
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: VMANOMALY_BEARER_TOKEN
            - name: VMANOMALY_BEARER_TOKEN_FILE
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: VMANOMALY_BEARER_TOKEN_FILE
            - name: VMANOMALY_HEADERS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: VMANOMALY_HEADERS
            - name: MCP_SERVER_MODE
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_SERVER_MODE
            - name: MCP_LISTEN_ADDR
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_LISTEN_ADDR
            - name: MCP_LOG_LEVEL
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_LOG_LEVEL
            - name: MCP_LOG_FILE
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_LOG_FILE
            - name: MCP_ENABLED_TOOLS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_ENABLED_TOOLS
            - name: MCP_DISABLED_TOOLS
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_DISABLED_TOOLS
            - name: MCP_HEARTBEAT_INTERVAL
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_HEARTBEAT_INTERVAL
            - name: MCP_DISABLE_RESOURCES
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: MCP_DISABLE_RESOURCES
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: vmanomaly
      namespace: mcp
    spec:
      selector:
        app: vmanomaly
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T00:49:16+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      vmanomaly:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: vmanomaly
          image: ghcr.io/victoriametrics/mcp-vmanomaly:0.5.1
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: VMANOMALY_ENDPOINT
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: VMANOMALY_ENDPOINT
          - name: VMANOMALY_BEARER_TOKEN
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: VMANOMALY_BEARER_TOKEN
          - name: VMANOMALY_BEARER_TOKEN_FILE
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: VMANOMALY_BEARER_TOKEN_FILE
          - name: VMANOMALY_HEADERS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: VMANOMALY_HEADERS
          - name: MCP_SERVER_MODE
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_SERVER_MODE
          - name: MCP_LISTEN_ADDR
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_LISTEN_ADDR
          - name: MCP_LOG_LEVEL
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_LOG_LEVEL
          - name: MCP_LOG_FILE
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_LOG_FILE
          - name: MCP_ENABLED_TOOLS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_ENABLED_TOOLS
          - name: MCP_DISABLED_TOOLS
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_DISABLED_TOOLS
          - name: MCP_HEARTBEAT_INTERVAL
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_HEARTBEAT_INTERVAL
          - name: MCP_DISABLE_RESOURCES
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: MCP_DISABLE_RESOURCES
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    The form opens with CHANGE_ME for each value you supply: 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_RESOURCES. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    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.5.1
    {
      "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.5.1"
          ],
          "env": {
            "VMANOMALY_ENDPOINT": "${VMANOMALY_ENDPOINT}",
            "VMANOMALY_BEARER_TOKEN": "${VMANOMALY_BEARER_TOKEN}",
            "VMANOMALY_BEARER_TOKEN_FILE": "${VMANOMALY_BEARER_TOKEN_FILE}",
            "VMANOMALY_HEADERS": "${VMANOMALY_HEADERS}",
            "MCP_SERVER_MODE": "${MCP_SERVER_MODE}",
            "MCP_LISTEN_ADDR": "${MCP_LISTEN_ADDR}",
            "MCP_LOG_LEVEL": "${MCP_LOG_LEVEL}",
            "MCP_LOG_FILE": "${MCP_LOG_FILE}",
            "MCP_ENABLED_TOOLS": "${MCP_ENABLED_TOOLS}",
            "MCP_DISABLED_TOOLS": "${MCP_DISABLED_TOOLS}",
            "MCP_HEARTBEAT_INTERVAL": "${MCP_HEARTBEAT_INTERVAL}",
            "MCP_DISABLE_RESOURCES": "${MCP_DISABLE_RESOURCES}"
          }
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add vmanomaly -e "VMANOMALY_ENDPOINT=${VMANOMALY_ENDPOINT}" -e "VMANOMALY_BEARER_TOKEN=${VMANOMALY_BEARER_TOKEN}" -e "VMANOMALY_BEARER_TOKEN_FILE=${VMANOMALY_BEARER_TOKEN_FILE}" -e "VMANOMALY_HEADERS=${VMANOMALY_HEADERS}" -e "MCP_SERVER_MODE=${MCP_SERVER_MODE}" -e "MCP_LISTEN_ADDR=${MCP_LISTEN_ADDR}" -e "MCP_LOG_LEVEL=${MCP_LOG_LEVEL}" -e "MCP_LOG_FILE=${MCP_LOG_FILE}" -e "MCP_ENABLED_TOOLS=${MCP_ENABLED_TOOLS}" -e "MCP_DISABLED_TOOLS=${MCP_DISABLED_TOOLS}" -e "MCP_HEARTBEAT_INTERVAL=${MCP_HEARTBEAT_INTERVAL}" -e "MCP_DISABLE_RESOURCES=${MCP_DISABLE_RESOURCES}" -- 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.5.1
    
    {
      "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.5.1"
          ],
          "env": {
            "VMANOMALY_ENDPOINT": "${VMANOMALY_ENDPOINT}",
            "VMANOMALY_BEARER_TOKEN": "${VMANOMALY_BEARER_TOKEN}",
            "VMANOMALY_BEARER_TOKEN_FILE": "${VMANOMALY_BEARER_TOKEN_FILE}",
            "VMANOMALY_HEADERS": "${VMANOMALY_HEADERS}",
            "MCP_SERVER_MODE": "${MCP_SERVER_MODE}",
            "MCP_LISTEN_ADDR": "${MCP_LISTEN_ADDR}",
            "MCP_LOG_LEVEL": "${MCP_LOG_LEVEL}",
            "MCP_LOG_FILE": "${MCP_LOG_FILE}",
            "MCP_ENABLED_TOOLS": "${MCP_ENABLED_TOOLS}",
            "MCP_DISABLED_TOOLS": "${MCP_DISABLED_TOOLS}",
            "MCP_HEARTBEAT_INTERVAL": "${MCP_HEARTBEAT_INTERVAL}",
            "MCP_DISABLE_RESOURCES": "${MCP_DISABLE_RESOURCES}"
          }
        }
      }
    }
    {
      "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.5.1"
          ],
          "env": {
            "VMANOMALY_ENDPOINT": "${VMANOMALY_ENDPOINT}",
            "VMANOMALY_BEARER_TOKEN": "${VMANOMALY_BEARER_TOKEN}",
            "VMANOMALY_BEARER_TOKEN_FILE": "${VMANOMALY_BEARER_TOKEN_FILE}",
            "VMANOMALY_HEADERS": "${VMANOMALY_HEADERS}",
            "MCP_SERVER_MODE": "${MCP_SERVER_MODE}",
            "MCP_LISTEN_ADDR": "${MCP_LISTEN_ADDR}",
            "MCP_LOG_LEVEL": "${MCP_LOG_LEVEL}",
            "MCP_LOG_FILE": "${MCP_LOG_FILE}",
            "MCP_ENABLED_TOOLS": "${MCP_ENABLED_TOOLS}",
            "MCP_DISABLED_TOOLS": "${MCP_DISABLED_TOOLS}",
            "MCP_HEARTBEAT_INTERVAL": "${MCP_HEARTBEAT_INTERVAL}",
            "MCP_DISABLE_RESOURCES": "${MCP_DISABLE_RESOURCES}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.VictoriaMetrics/mcp-vmanomaly
    
    • not probed yet: tools unpinned, ingest lists them

    tools

    Probe result: faileddocker: the container exited: Error initializing config: failed to parse MCP_HEARTBEAT_INTERVAL: time: invalid duration "<secret>"

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-17 13:28 local-mac-vm docker failed gvisor docker: the container exited: Error initializing config: failed to parse MCP_HEARTBEAT_INTERVAL: time: invalid duration "<secret>"