grafana/mcp-grafana
Canonical URL: https://github.com/grafana/mcp-grafana · Fetched from: https://raw.githubusercontent.com/grafana/mcp-grafana/HEAD/README.md · Machine form: /v1/resource-scans/github-com-grafana-mcp-grafana-9e46c3d7e1 · Markdown
Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 43e42e3d03ed16c49b9ee06dfb8ba24b3090ffc9a4321557138c52ac2b787974 · 153974 bytes · scanned 2026-10-27T12:21:33.867Z · scanner resource-scan-v1 · ledger entry 1553.
Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.
Checks (latest receipt)
Outbound network references — flag
The scanned bytes reference outbound network activity to these domains: archestra.ai, docs.astral.sh, donottrack.sh, github.com, grafana.com, grafana.github.io, grafana.internal, mise.jdx.dev, modelcontextprotocol.io, myinstance.grafana.net, one.example.com, opentelemetry.io, pkg.go.dev, secure-grafana.example.com, tempo-us-central1.grafana.net, two.example.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.
Evidence: domain: archestra.ai; domain: docs.astral.sh; domain: donottrack.sh; domain: github.com; domain: grafana.com; domain: grafana.github.io; domain: grafana.internal; domain: mise.jdx.dev; domain: modelcontextprotocol.io; domain: myinstance.grafana.net; domain: one.example.com; domain: opentelemetry.io; domain: pkg.go.dev; domain: secure-grafana.example.com; domain: tempo-us-central1.grafana.net; domain: two.example.com
Credential and environment access — flag
The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); authorization headers and bearer values. The receipt names the pattern kinds only; no credential value is reproduced here.
Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); authorization headers and bearer values
Install and postinstall hooks — pass
No install or postinstall hooks were found in the scanned bytes.
Obfuscation and encoded payloads — pass
No obfuscation or encoded-payload signs were found in the scanned bytes.
Shell-outs and download-and-execute — flag
The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.
Evidence: shell command tools named in the bytes (curl, wget, powershell)
Permission declarations vs behavior — pass
The bytes show network, credentials behavior, and a permissions declaration is present in the bytes: read`, `datasources.permissions:read`, `folders.permissions:read`, `serviceaccounts.permissions:read`, `teams.permissions:read`, `users.permissions:read`
Evidence: behavior: network; behavior: credentials; declared: read`, `datasources.permissions:read`, `folders.permissions:read`, `serviceaccounts.permissions:read`, `teams.permissions:read`, `users.permissions:read`
Known-bad indicators — pass
None of the scanner's published known-bad indicator patterns matched the scanned bytes.
Provenance facts (weak signals) — pass
Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: grafana/mcp-grafana; bytes scanned: 153974; fetched from: https://raw.githubusercontent.com/grafana/mcp-grafana/HEAD/README.md.
Evidence: source host: github.com; repository: grafana/mcp-grafana; bytes scanned: 153974; fetched from: https://raw.githubusercontent.com/grafana/mcp-grafana/HEAD/README.md
History
Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.
- 2026-10-27 — 3 of 8 checks flagged · SHA-256 43e42e3d03ed16c4… · 153974 bytes · scanner resource-scan-v1 · ledger entry 1553