Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Grafana

OCI · DOCKER.IO/GRAFANA/MCP-GRAFANA · 2 COMPONENTS

An MCP server giving access to Grafana dashboards, data and more.

Available components

remote · mcp.grafana.com 37 oci · docker.io/grafana/mcp-grafana 9
0 this week 9 Trust /100

Last scanned (5 hours ago)

Scores higher than 17% of OCI servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • A critical CVE affects apt, and no fixed version has been published yet. View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • CVE-2023-45853 affects this package: none ▼ security
    • CVE-2019-1010022 affects this package: none ▼ security
    • CVE-2026-5450 affects this package: none ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Package version: 2.1.1 → 2.2.0 functional
  • 20 Oct 26 0
    • Package version: 2.0.2 → 2.1.1 functional
    • Package version: 2.0.2 → 2.1.0 functional
  • 14 Oct 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
  • 13 Oct 26 0
    • Provenance: unverified → fail ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 12 Oct 26 0
    • Provenance: fail → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 2.0.1 → 2.0.2 functional
  • 7 Oct 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 2.0.0 → 2.0.1 functional
  • 1 Oct 26 0
    • Package version: 1.6.3 → 2.0.0 functional
  • 30 Sept 26 0
    • Package version: 1.6.2 → 1.6.3 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/docker.io/grafana/mcp-grafana@2.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Vulnerabilities 100 findings
ID CVE Severity Vector Fix available
DEBIAN-CVE-2011-3374 CVE-2011-3374 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-109518 CVE-2026-109518 none yes
DEBIAN-CVE-2022-0563 CVE-2022-0563 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2025-14104 CVE-2025-14104 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H no
DEBIAN-CVE-2026-13595 CVE-2026-13595 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H no
DEBIAN-CVE-2026-27456 CVE-2026-27456 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2026-3184 CVE-2026-3184 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-53613 CVE-2026-53613 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2026-53615 CVE-2026-53615 high CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H no
DEBIAN-CVE-2026-78410 CVE-2026-78410 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2016-2781 CVE-2016-2781 medium CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N no
DEBIAN-CVE-2017-18018 CVE-2017-18018 medium CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N no
DEBIAN-CVE-2025-5278 CVE-2025-5278 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L no
DEBIAN-CVE-2026-56391 CVE-2026-56391 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H no
DEBIAN-CVE-2026-56392 CVE-2026-56392 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H no
DEBIAN-CVE-2026-102473 CVE-2026-102473 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-102474 CVE-2026-102474 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-53910 CVE-2026-53910 none no
DEBIAN-CVE-2022-27943 CVE-2022-27943 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-102010 CVE-2026-102010 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H no
DEBIAN-CVE-2026-114690 CVE-2026-114690 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-114691 CVE-2026-114691 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-115455 CVE-2026-115455 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H no
DEBIAN-CVE-2026-95619 CVE-2026-95619 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H no
GO-2026-5932 none yes
DEBIAN-CVE-2022-3219 CVE-2022-3219 low CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L no
DEBIAN-CVE-2025-30258 CVE-2025-30258 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2025-68972 CVE-2025-68972 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N no
DEBIAN-CVE-2026-105712 CVE-2026-105712 low CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L no
DEBIAN-CVE-2026-57062 CVE-2026-57062 low CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-41991 CVE-2026-41991 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N no
DEBIAN-CVE-2026-41992 CVE-2026-41992 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2026-54369 CVE-2026-54369 none no
DEBIAN-CVE-2026-54370 CVE-2026-54370 none no
DEBIAN-CVE-2026-54371 CVE-2026-54371 none no
DEBIAN-CVE-2026-42250 CVE-2026-42250 none no
DEBIAN-CVE-2010-4756 CVE-2010-4756 none no
DEBIAN-CVE-2018-20796 CVE-2018-20796 high CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2019-1010022 CVE-2019-1010022 critical CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2019-1010023 CVE-2019-1010023 high CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2019-1010024 CVE-2019-1010024 medium CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N no
DEBIAN-CVE-2019-1010025 CVE-2019-1010025 medium CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N no
DEBIAN-CVE-2019-9192 CVE-2019-9192 high CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-18374 CVE-2026-18374 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2026-19499 CVE-2026-19499 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H no
DEBIAN-CVE-2026-19542 CVE-2026-19542 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2026-5435 CVE-2026-5435 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2026-5450 CVE-2026-5450 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2026-5928 CVE-2026-5928 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-6238 CVE-2026-6238 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L no

Showing 50 of 100 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Grafana MCP server?

Grafana runs locally as a container image, launched with docker run --rm -i -e GRAFANA_URL -e GRAFANA_SERVICE_ACCOUNT_TOKEN -e GRAFANA_USERNAME -e GRAFANA_PASSWORD -e GRAFANA_ORG_ID -e GRAFANA_EXTRA_HEADERS -e GRAFANA_FORWARD_HEADERS docker.io/grafana/mcp-grafana:2.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/grafana/mcp-grafana

# add to Claude Code
claude mcp add grafana-mcp-grafana -- docker run --rm -i -e GRAFANA_URL -e GRAFANA_SERVICE_ACCOUNT_TOKEN -e GRAFANA_USERNAME -e GRAFANA_PASSWORD -e GRAFANA_ORG_ID -e GRAFANA_EXTRA_HEADERS -e GRAFANA_FORWARD_HEADERS docker.io/grafana/mcp-grafana:2.2.0

This image reads GRAFANA_URL, GRAFANA_SERVICE_ACCOUNT_TOKEN, GRAFANA_USERNAME, GRAFANA_PASSWORD, GRAFANA_ORG_ID, GRAFANA_EXTRA_HEADERS and GRAFANA_FORWARD_HEADERS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Grafana MCP server?

Grafana is an MCP server listed in the public MCP registry as io.github.grafana/mcp-grafana. An MCP server giving access to Grafana dashboards, data and more. This page covers its container image (docker.io/grafana/mcp-grafana).

Is the Grafana MCP server safe to use?

Grafana scores 9 out of 100 on VerifyMCP. We recorded 100 known advisories against it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Grafana MCP server still maintained?

Grafana is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Grafana MCP server under?

Grafana declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.