Is Grafana MCP Server safe to use?

Grafana MCP Server has an HVTrust score of 67.8/100 (Grade B), ranked #412 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Grafana MCP Server?

Grafana MCP Server scores 67.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.5k GitHub stars and is categorized under MCP Servers.

Grafana MCP Server

Repository

MCP server for Grafana

MCP Servers Go Listed Apache-2.0

Is Grafana MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.3 / 10

Provenance None

Signed commits 100%

Last push 2d ago

Compare Grafana MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Grafana MCP Server scores 67.8/100 (Grade B), ranked #412 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.3/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Grafana MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 7.3 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Signed-Releases 0 +3.5 → 71.3 B · #193 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Grafana MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/grafana/mcp-grafana, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Strong

OpenSSF Scorecard rates the repository's practices 7.3/10 (scanned Sep 30, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies10
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 7
Published packages None

No registry package. Grafana MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Grafana MCP Server.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Grafana MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Grafana MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Grafana MCP Server’s 67.8.

Where the 67.8 comes from

HVTrust dimensions vs the MCP Servers average

67.8 / 100 · 100.0% confidence

Grafana MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.1 / 25

3.7 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.7 below avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

14.7 / 17

2.5 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.5 / 20

7.3 above avg 12.2

AdoptionLog-scaled stars · package downloads

8.5 / 20

1.1 above avg 7.4

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-11

Rank Moved

Rank dropped 12 spots (#400 → #412)

2026-10-01

Rank Moved

Rank rose 22 spots (#408 → #386)

2026-09-30

Rank Moved

Rank rose 10 spots (#418 → #408)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Grafana MCP Server View MCP Servers Report missing data

82.4

Activity sub-score · out of 100

#245

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars

3.5k

Forks

461

Last Push

2026-10-09

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼12

was #400

Analysis

Activity Inputs

82.4 / 100

StarsRepository reach

21.3 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

24.0 / 25

CommunityFork signal

12.4 / 20

Common questions about Grafana MCP Server

Grafana MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Grafana MCP Server publish package provenance?

No published build provenance is currently detected for Grafana MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Grafana MCP Server have an OpenSSF Scorecard?

Grafana MCP Server has an OpenSSF Scorecard score of 7.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Grafana MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

What license does Grafana MCP Server use?

Grafana MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Grafana MCP Server's commits signed?

100% of the last 100 commits to Grafana MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Grafana MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Grafana MCP Server?

For maintainers

HVTrust scores Grafana MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-11

Rank Moved

Rank dropped 12 spots (#400 → #412)

2026-10-01

Rank Moved

Rank rose 22 spots (#408 → #386)

2026-09-30

Rank Moved

Rank rose 10 spots (#418 → #408)

2026-09-23

Rank Moved

Rank dropped 258 spots (#158 → #416)

2026-09-21

Rank Moved

Rank rose 255 spots (#414 → #159)

2026-09-19

Rank Moved

Rank dropped 11 spots (#399 → #410)

2026-09-11

Rank Moved

Rank dropped 12 spots (#395 → #407)

2026-09-07

Rank Moved

Rank dropped 16 spots (#368 → #384)

2026-09-06

Rank Moved

Rank dropped 10 spots (#358 → #368)

2026-09-05

Rank Moved

Rank dropped 63 spots (#295 → #358)

2026-09-04

Rank Moved

Rank dropped 12 spots (#283 → #295)

2026-09-03

Rank Moved

Rank dropped 12 spots (#271 → #283)

2026-08-31

Rank Moved

Rank dropped 27 spots (#241 → #268)

2026-08-29

Rank Moved

Rank dropped 10 spots (#239 → #249)

2026-08-26

Rank Moved

Rank dropped 17 spots (#211 → #228)

2026-08-24

Rank Moved

Rank dropped 12 spots (#205 → #217)

2026-08-22

Rank Moved

Rank rose 14 spots (#220 → #206)

2026-08-19

Rank Moved

Rank dropped 10 spots (#212 → #222)

2026-08-17

Rank Moved

Rank rose 19 spots (#235 → #216)

2026-08-13

Rank Moved

Rank dropped 16 spots (#214 → #230)

2026-08-12

Rank Moved

Rank rose 13 spots (#227 → #214)

2026-08-10

Rank Moved

Rank dropped 10 spots (#220 → #230)

2026-08-08

Rank Moved

Rank dropped 42 spots (#176 → #218)

2026-08-04

Grade Changed

Trust grade C → B

2026-08-01

Grade Changed

Trust grade B → C

2026-07-31

Grade Changed

Trust grade C → B

2026-07-29

Rank Moved

Rank rose 10 spots (#166 → #156)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/grafana-mcp-server.svg)](https://hvtracker.net/agents/grafana-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/grafana-mcp-server"><img src="https://hvtracker.net/badge/grafana-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Grafana MCP Server

How Grafana MCP Server could raise its score

Chain of custody

Source Signed

Review and release Strong

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Grafana MCP Server compares in MCP Servers

Where the 67.8 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Grafana MCP Server

AI agent surface

Maintain Grafana MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers