{ "data": { "a": { "slug": "axiom", "name": "Axiom MCP Server", "vendor": "Axiom, Inc.", "vendorUrl": "https://axiom.co", "kind": "mcp", "category": "observability", "summary": "Axiom's hosted MCP server at mcp.axiom.co lets AI agents query logs, traces, events and metrics in an Axiom organisation with APL, read and manage dashboards, monitors and notifiers, and inspect the service map, over OAuth or a token header.", "url": "https://www.anchorterminal.com/tools/axiom", "markdownUrl": "https://www.anchorterminal.com/tools/axiom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/axiom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/axiom.json", "dns": "axiom.grade.anchorterminal.com", "transports": [ "streamable-http", "sse" ], "remoteUrl": "https://mcp.axiom.co/mcp", "packages": [], "auth": "oauth", "authNotes": "Browser OAuth (recommended) creates a session the agent uses as the signed-in user; sessions are listed and revoked under Settings \u003e Profile. Agents without a browser send `Authorization: Bearer` with a personal access token and `x-axiom-org-id`, or put the organisation id in the URL as `?org-id=`. A PAT has full account rights; scoped API tokens with dataset and action permissions, expiry and dollar query-cost limits exist for the REST API and Skills. EU organisations use mcp.eu.axiom.co.", "pricing": "freemium", "pricingNotes": "Personal plan $0 with no card, with 500 GB a month of data loading compute, 10 GB-hours of query compute, 25 GB storage, 30-day retention. Axiom Cloud $25 a month platform fee plus usage, with an Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage, volume discounts and add-ons (RBAC $50, extended audit logs $50, SAML SSO $100, directory sync $100 a month). An agent can provision a temporary organisation with no account (https://axiom.co/pricing).", "priceSummary": "$25 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, API docs, pricing or terms (checked 2026-11-03). Usage is billed to the organisation; unclaimed agent-created organisations have fixed free limits for 24 hours.", "endpoints": [] }, "toolCount": 31, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://axiom.co/docs/console/intelligence/mcp-server", "llmsTxt": "https://axiom.co/llms.txt", "registryName": "co.axiom/mcp", "capabilities": [ "observability.logs", "observability.traces", "observability.metrics", "observability.incidents", "observability.errors" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "mcp-registry", "oauth", "llms-txt", "status-page", "sla", "security-txt", "bug-bounty", "soc2", "iso27001", "eu-region", "usage-priced", "closed-source" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 68.2, "grade": "B", "agentReady": false, "rank": 269, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "bestFor": "Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.", "strengths": [ "`POST /v2/orgs/provision` needs no account and returns a working token; a person claims the organisation later or it expires in 24 hours", "Query cost limits in dollars per hour and per day on tokens and roles bound what an agent can spend, with 429 past the cap", "OAuth sessions keep tokens away from the agent and are revocable per session; ISO 27001, SOC 2 Type II, a security.txt and a bug bounty policy", "99.9 per cent monthly uptime SLA with service credits, published rate-limit headers and a status page with per-component uptime", "Dated changelog with MCP entries, llms.txt, Markdown twins of every docs page and setup for 16 clients" ], "weaknesses": [ "The server is closed source and tool input schemas are only visible through an authenticated session", "The AI agents overview calls the MCP server read-only while the tools reference lists delete tools for dashboards, monitors and notifiers", "A header-based connection uses a personal access token with full account rights, since scoped API tokens aren't accepted by the MCP server per the docs", "Nine status incidents between 12 August and 30 October 2026, mostly elevated query errors, one of 70 minutes in the US", "Logs and traces come back as untrusted text with no prompt-injection guidance, and the sub-processor list renders through a script our reader couldn't run" ], "agentNotes": [ "With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed", "Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL", "Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner", "Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first", "`deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.2 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 57 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y add-mcp https://mcp.axiom.co/mcp -g", "http": "curl -X POST https://api.axiom.co/v2/orgs/provision -H 'Content-Type: application/json' -d '{\"name\":\"agent-sandbox\"}'", "claudeCode": "claude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp", "config": { "mcpServers": { "axiom": { "url": "https://mcp.axiom.co/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.logs", "tool": "https://letme.dev/axiom" }, "area": "developer", "unitPrices": [ { "item": "Axiom Cloud platform fee", "unit": "month", "usd": 25, "note": "Plus usage beyond the Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage a month" }, { "item": "Role-based access control add-on", "unit": "month", "usd": 50, "note": "Extended audit logs $50, SAML SSO $100, directory sync $100" } ], "provenance": { "legalEntity": "Axiom, Inc.", "domain": "axiom.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://axiom.co/docs/legal/terms-of-service", "privacy": "https://axiom.co/docs/legal/privacy", "statusPage": "https://status.axiom.co", "changelog": "https://axiom.co/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms of service name Axiom, Inc. under California law and carry no last-updated date in the text; the privacy policy and DPA name Axiom Inc. and privacy@axiom.co. No clause on automated reading of the website was found.", "axiom.co/robots.txt allows all crawlers, naming ClaudeBot, Claude-User and others as allowed, and disallows only /api/. trust.axiom.co renders through a script (Vanta) and its sub-processor list was not readable.", "axiom.co/.well-known/security.txt redirects to app.axiom.co, where it names security@axiom.co, a policy at axiom.co/security and an expiry of 1 April 2027.", "status.axiom.co is an incident.io page with six US and six EU components and per-component uptime for August to November 2026; feed.rss holds nine incidents back to 12 August 2026.", "RDAP for axiom.co couldn't be read (the .co registry's RDAP answered 502 and rdap.org returned nothing), so the registration date is blank. firstReleased is 5 December 2024, the v0.0.1 tag of the earlier open-source mcp-server-axiom; the hosted server's own first date isn't on a first-hand page, and its registry entry is from 30 September 2025." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/axiom.json", "live": { "slug": "axiom", "probe": { "target": "https://mcp.axiom.co/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T21:39:14.263725519Z", "lastOk": true, "lastStatus": 401, "lastMs": 72, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 177, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.axiom.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:37:46.118662306Z" }, "versions": [ { "registry": "mcp-registry", "name": "co.axiom/mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "securityTxt": { "url": "https://axiom.co/.well-known/security.txt", "state": "valid", "expires": "2027-04-01T00:01:00Z", "checkedAt": "2026-11-04T15:54:16.073085585Z" }, "updatedAt": "2026-11-04T21:39:14.263725519Z" } }, "answer": "Grafana MCP Server scores 71 (BB) on agent readiness against Axiom MCP Server's 68.2 (B), and leads in 5 of 7 scored categories. Axiom MCP Server leads on security \u0026 auth.", "b": { "slug": "grafana-mcp-server", "name": "Grafana MCP Server", "vendor": "Grafana Labs", "vendorUrl": "https://grafana.com/docs/grafana/latest/developer-resources/mcp/", "kind": "mcp", "category": "observability", "summary": "Grafana Labs' open-source MCP server for Grafana. It runs locally or self-hosted and gives agents dashboards, datasource queries (Prometheus, Loki, Tempo, Pyroscope and others), alerting, incidents and OnCall on a self-managed Grafana or Grafana Cloud.", "url": "https://www.anchorterminal.com/tools/grafana-mcp-server", "markdownUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json", "dns": "grafana-mcp-server.grade.anchorterminal.com", "repo": "https://github.com/grafana/mcp-grafana", "license": "Apache-2.0", "transports": [ "stdio", "sse", "streamable-http" ], "packages": [ { "registry": "pypi", "name": "mcp-grafana" }, { "registry": "oci", "name": "grafana/mcp-grafana" }, { "registry": "go", "name": "github.com/grafana/mcp-grafana/v2" } ], "auth": "mixed", "authNotes": "The server signs in to Grafana with a service account token (`GRAFANA_SERVICE_ACCOUNT_TOKEN`, or a file path in `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` that is re-read on each request), or with `GRAFANA_USERNAME` and `GRAFANA_PASSWORD`. An admin creates the token in Grafana, self-serve, and Grafana RBAC sets what it can do. The README lists the permissions each tool needs. Over streamable HTTP a caller can send its own token in `X-Grafana-Service-Account-Token`, and `--server-auth-token` makes callers present a bearer token to the server itself. stdio needs no caller credential.", "pricing": "free", "pricingNotes": "Free and open source under Apache-2.0, with nothing to buy for the server. It needs a Grafana instance, which can be self-managed open-source Grafana or Grafana Cloud. Grafana Cloud prices were not checked. The separate hosted Grafana Cloud MCP server counts towards Grafana Assistant usage (checked 2026-10-08).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs or the changelog (checked 2026-10-08).", "endpoints": [] }, "toolCount": 119, "popularity": { "githubStars": 3535, "npmWeekly": null, "pypiWeekly": 151923, "asOf": "2026-10-08" }, "docsUrl": "https://grafana.com/docs/grafana/latest/developer-resources/mcp/", "llmsTxt": "https://grafana.com/llms.txt", "registryName": "io.github.grafana/mcp-grafana", "capabilities": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents", "work.oncall" ], "tags": [ "official", "local", "open-source", "self-hosted", "mcp", "go", "docker", "helm", "grafana", "llms-txt", "telemetry-default-on" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 71, "grade": "BB", "agentReady": true, "rank": 154, "ranked": true, "rankOf": 1349, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 96, "payments": 60, "reliability": 91, "schema": 81, "security": 67, "transparency": 80 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -7, "negativeNotes": [ "-2: CVE-2026-15583 (high, CVSS 8.6), published by Grafana Labs on 15 July 2026. Before the fix, a URL in the then undocumented `X-Grafana-URL` request header made the server send its environment service account token to a host the caller chose, an unauthenticated exfiltration path on the HTTP transports. The changelog records the fix in 0.17.2 on 13 July, the advisory lists 0.17.1. Fixed and published, about three months old (https://grafana.com/security/security-advisories/cve-2026-15583/).", "-2: CVE-2026-19516 (critical, CVSS 9.1), published on 11 August 2026. A caller of `grafana_api_request` could still steer the server's requests through `X-Grafana-URL` to internal, loopback and link-local services, metadata endpoints included, and read the responses, since the July fix guarded only the token. Fixed in 1.1.0 on 10 August, which removed the header, and published, about two months old (https://grafana.com/security/security-advisories/cve-2026-19516/).", "-3: v2.1.0, a minor release on 20 October 2026, changed `list_users_by_org` to a paginated tool that returns `{totalCount, page, perPage, orgUsers}` instead of an array of users. The changelog labels it Breaking on the day, and no earlier notice was found (CHANGELOG.md changed only in the release commit, and the 7 October pull request changed only the tool's description). The admin tools are off by default and Grafana Labs says agents need no changes, so the floor (https://github.com/grafana/mcp-grafana/blob/main/CHANGELOG.md)." ], "verdict": "Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026.", "bestFor": "Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.", "strengths": [ "All 79 default tools in 2.0.2 build typed JSON Schema inputs from Go parameter structs and set `readOnlyHint` and `destructiveHint`, and 73 also set `idempotentHint`, read from source at tag v2.0.2", "`--disable-write`, `--disable-query`, per-category flags and Loki enforced matchers narrow what the server can do, with a per-tool table of required RBAC permissions", "16 tagged releases between 28 July and 7 October 2026, with a Keep a Changelog file that labels breaking changes", "Listed in the official MCP registry under the verified `io.github.grafana` namespace, with 2.0.2 marked latest from 10 October 2026", "Dashboard summary, JSONPath property reads, jq filtering and a 100-line Loki default keep responses small" ], "weaknesses": [ "The default set is 79 tools, and 119 with every category on, counted from the registration code in source", "Write tools and `grafana_api_request`, which can call any Grafana API path, are enabled unless the operator turns them off", "Anonymous usage statistics went from off by default in 1.5.0 (17 September 2026) to on by default in 2.0.0", "Two `X-Grafana-URL` flaws in 2026, a token leak (CVE-2026-15583, high) and an SSRF (CVE-2026-19516, critical), fixed in 0.17.2 and 1.1.0", "Minor release 2.1.0 changed `list_users_by_org` output on 20 October 2026 with no advance notice, and the repository has no SECURITY.md" ], "agentNotes": [ "Start with `--disable-write` unless the task needs writes, and add `--disable-api` to remove `grafana_api_request`", "Pass `--enabled-tools` with only the categories needed. The default list loads 79 tools", "Use `get_dashboard_summary` or `get_dashboard_property` with a JSONPath before `get_dashboard_by_uid`, which returns the whole dashboard JSON", "Set `GRAFANA_USAGE_STATS=disabled` or `DO_NOT_TRACK=1` to stop the four-hourly usage report to stats.grafana.org", "Use streamable HTTP, not SSE, when each caller needs its own token or organisation, and set `--server-auth-token` on any non-loopback address" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71 } ], "editorialScores": { "ergonomics": 74, "maintenance": 96, "payments": 60, "reliability": 91, "schema": 81, "security": 67, "transparency": 81 }, "provenanceScore": 78, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uvx mcp-grafana", "config": { "mcpServers": { "grafana": { "args": [ "mcp-grafana" ], "command": "uvx", "env": { "GRAFANA_SERVICE_ACCOUNT_TOKEN": "\u003cyour service account token\u003e", "GRAFANA_URL": "http://localhost:3000" } } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/grafana-mcp-server" }, "area": "developer", "provenance": { "legalEntity": "Raintank Inc., d/b/a Grafana Labs", "domain": "grafana.com", "domainRegistered": "2014-05-27", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://grafana.com/legal/privacy-policy/", "statusPage": "", "changelog": "https://github.com/grafana/mcp-grafana/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "No terms document governs this software beyond the Apache-2.0 licence, so `terms` is left out.", "The privacy policy (last updated 10 July 2026) names Raintank Inc., d/b/a Grafana Labs, 165 Broadway, 23rd Floor, New York, and says its open-source and commercial software may report usage statistics.", "grafana.com/.well-known/security.txt returns 404. Reports go to an Intigriti disclosure programme or security@grafana.com, with no bounties (https://grafana.com/legal/report-a-security-issue/).", "RDAP for grafana.com gives a registration date of 2014-05-27.", "The server runs on the owner's machine. Usage reports go to stats.grafana.org, a second Grafana Labs domain." ], "score": 78 }, "requirements": { "card": "no", "freeTier": true, "minutes": 10, "credential": "api-key", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/grafana-mcp-server.json", "live": { "slug": "grafana-mcp-server", "versions": [ { "registry": "github", "name": "grafana/mcp-grafana", "version": "v2.2.0", "released": "2026-11-02", "seenAt": "2026-11-04T20:20:27.77772694Z" }, { "registry": "mcp-registry", "name": "io.github.grafana/mcp-grafana", "version": "v2.2.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "pypi", "name": "mcp-grafana", "version": "2.2.0", "released": "2026-11-02", "seenAt": "2026-11-04T20:20:27.648731705Z" } ], "githubStars": 3640, "pypiWeekly": 99402, "securityTxt": { "url": "https://grafana.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:18.985935709Z" }, "llmsTxt": { "url": "https://grafana.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:23:07.728680516Z" }, "domain": { "domain": "grafana.com", "registered": "2014-05-27", "source": "https://rdap.verisign.com/com/v1/domain/grafana.com", "checkedAt": "2026-11-01T14:20:13.960632327Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/grafana/mcp-grafana/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-04T08:33:44.229180515Z", "changedAt": "2026-11-03T07:59:43.081071646Z", "fingerprint": "78c3abe924b6" }, { "url": "https://grafana.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:24:38.454854719Z", "changedAt": "2026-11-04T08:24:38.454854719Z", "fingerprint": "dec83a9810c5" } ], "github": { "repo": "grafana/mcp-grafana", "checkedAt": "2026-11-02T08:52:46.468852437Z", "stars": 3631, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T08:37:17Z", "openIssues": 55, "openPRs": 38, "issuesOpened90d": 92, "issuesClosed90d": 113, "prsMerged90d": 267, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 2, "other": 0, "latest": "success", "latestAt": "2026-11-02T08:35:00Z" }, "replies": { "sampled": 25, "unanswered": 6, "medianDays": 1.2 } }, "updatedAt": "2026-11-04T20:20:27.77772694Z" } }, "edges": [ { "by": 19, "category": "reliability", "leads": "grafana-mcp-server", "name": "Reliability", "reasons": { "a": "Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.", "b": "Scored as local software, since the owner runs it over stdio, SSE or streamable HTTP. Official PyPI package `mcp-grafana` (a wheel that carries the Go binary, Python 3.10 or later), a Docker image, release binaries and a Helm chart, with Grafana 9.0 or later stated as the requirement (20). Unit, integration and end-to-end workflows all concluded in success on main on 8 October 2026, per the 8 October check, not re-read on 1 November (25). Per the 8 October check, not re-read on 1 November, 54 open issues, none labelled bug, and 38 closed in the 30 days before that check. Three bug reports remained open from July and August (#992 `run_panel_query` 422, #1005 `grafana_api_request` 500 on plugin resources, #1049 a dropped table row in `get_panel_image`), each with replies. A stale issue and pull request workflow was added on 27 October (19 of 25). The changelog follows Keep a Changelog and semantic versioning and labels breaking changes, and 1.6.2 announced that 2.0 came next. Patch release 1.4.1 carried a breaking parameter change on the Sift tools, 2.0.0 followed 1.0.0 by two months, and minor release 2.1.0 on 20 October changed the output of `list_users_by_org`, labelled on the day (12 of 15). Version 2.1.1, the latest release on 1 November (15)." }, "scores": { "a": 72, "b": 91 } }, { "by": 19, "category": "schema", "leads": "grafana-mcp-server", "name": "Schema \u0026 documentation", "reasons": { "a": "The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use `queryMetrics` for metrics datasets instead of `queryDataset`, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.", "b": "Read from source at tag v2.0.2, without running it, and unchanged in count at v2.1.1. All 79 default tools build their JSON Schema input by reflection from a typed Go parameter struct, and `buildInputSchema` in `tools.go` sets `additionalProperties` to false. No tool sets an output schema, which issue #1278 asks for (23 of 25). grafana.com serves llms.txt and a Markdown form of every docs page, the MCP pages included (10). Descriptions state purpose and inputs. Version 2.0.2 removed model directives and references to other tools from descriptions to meet connector directory rules, so guidance on when to use a tool is thinner than it was (14 of 20). Nearly every parameter field in the source structs carries a description tag, but few declare an enum. Values such as `queryType` ('range' or 'instant') and incident `status` are named in prose, and some parameters are free-form objects (9 of 15). The docs have client configuration examples, task guides and a troubleshooting page, and empty results return hints. No catalogue of error responses was found (10 of 15). Semantic versions, tagged releases and a dated changelog (15)." }, "scores": { "a": 62, "b": 81 } }, { "by": 13, "category": "maintenance", "leads": "grafana-mcp-server", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.", "b": "v2.1.1 tagged on 20 October 2026, 12 days before the check, after v2.1.0 the same day, with commits on main to 31 October (30). 17 tagged releases from 1.1.0 on 10 August to 2.1.1 in the 90 days to 1 November (20). Per the 8 October check, not re-read on 1 November, 38 issues closed in the 30 days before that check against 54 open and 22 open pull requests, and several feature requests from March and April without a reply (21 of 25). Listed in the official MCP registry as `io.github.grafana/mcp-grafana`, a GitHub-verified namespace, with v2.1.1 published on 20 October and marked latest (15). Renovate, a Docker image scan workflow, cosign signing with SPDX SBOMs for releases from 2.1.0, and Go toolchain and dependency bumps for CVEs on 21 and 28 October (10)." }, "scores": { "a": 83, "b": 96 } }, { "by": 11, "category": "ergonomics", "leads": "grafana-mcp-server", "name": "Agent ergonomics", "reasons": { "a": "31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.", "b": "79 tools load by default and 119 with every category on, counted from the registration code in `cmd/mcp-grafana/main.go` and `tools/*.go` at tag v2.0.2, with no tool added or removed by v2.1.1. That is 5 of 25 by count, plus 9 for `--enabled-tools`, per-category `--disable-*` flags, 12 opt-in categories and `--disable-write`, which leaves 62 (14). `limit` and `page` on searches, `get_dashboard_summary`, JSONPath reads through `get_dashboard_property`, a jq filter on `grafana_api_request`, and a 100-line default on `query_loki_logs` with an optional byte and time-range guardrail (18 of 20). Unknown argument keys are rejected with the valid ones listed, empty results carry likely causes and next steps, and TraceQL errors return correction hints. No documented error list (16 of 20). In source every default tool sets `readOnlyHint` and `destructiveHint` (60 read-only, 9 marked destructive), and 73 of 79 also set `idempotentHint`. The six that leave it unset are writes, for which the protocol default is false. No idempotency keys on creates (17 of 20). Most parameters are optional in the source structs. The Go module is the only library, with a Python wrapper for install (9 of 15)." }, "scores": { "a": 63, "b": 74 } }, { "by": 10, "category": "transparency", "leads": "grafana-mcp-server", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.", "b": "Apache-2.0 (30). Local software that talks to the configured Grafana. A docs page lists every field in the usage report, the destination, and the region and network name the receiving service adds, and the Grafana Labs privacy policy (last updated 10 July 2026) covers usage statistics from its open-source software. No retention period for the reports was found (24 of 30). No deprecation policy. Notices come without dates, such as `GRAFANA_API_KEY` to be removed 'in a future version', and the Sift tools were marked deprecated before 2.0.0 removed them (10 of 20). Usage statistics are documented with three opt-outs and a `log` mode that prints the report without sending it. They arrived off by default in 1.5.0 on 17 September 2026 and were switched on by default in 2.0.0, noted in the changelog (17 of 20)." }, "scores": { "a": 70, "b": 80 } }, { "by": 5, "category": "security", "leads": "axiom", "name": "Security \u0026 auth", "reasons": { "a": "Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.", "b": "The server holds a Grafana service account token, which Grafana RBAC can scope by action and resource and which can be revoked. `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` is re-read on each request for rotation. Username and password and a deprecated API key also work. The open-source server has no OAuth, and no secret travels in a URL (25 of 30). `--disable-write`, `--disable-query`, per-category flags, Loki enforced matchers and a per-tool RBAC table support least privilege. Writes are on by default, the default set includes `grafana_api_request` for any API path, and nothing asks for confirmation (14 of 20). Log lines, dashboards and annotations reach the model as stored. No injection guidance was found in the README or docs, and issue #680 on the subject has been open since 24 March 2026 (2 of 15). OpenTelemetry traces, metrics and logs per tool call and slow-request logging, with arguments left out of spans unless `--include-args-in-spans` is set (10 of 15). Grafana Labs runs a disclosure programme on Intigriti without bounties, lists ISO 27001 and SOC 2 Type 2, and publishes advisories on grafana.com, two of them for this server (CVE-2026-15583 on 15 July and CVE-2026-19516 on 11 August 2026). The repository has no SECURITY.md and grafana.com has no security.txt (16 of 20)." }, "scores": { "a": 72, "b": 67 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Axiom, Inc.", "b": "Grafana Labs", "name": "Vendor" }, { "a": "https://mcp.axiom.co/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, SSE (legacy)", "b": "stdio, SSE (legacy), Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Apache-2.0", "name": "Licence" }, { "a": "31", "b": "119", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "co.axiom/mcp", "b": "io.github.grafana/mcp-grafana", "name": "MCP registry" }, { "a": "2026-10-29", "b": "2026-10-20", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-07-10", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3.5k stars, 152k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Grafana MCP Server scores 71 (BB) on agent readiness against Axiom MCP Server's 68.2 (B), and leads in 5 of 7 scored categories. Axiom MCP Server leads on security \u0026 auth.", "question": "Which is better for AI agents, Axiom MCP Server or Grafana MCP Server?" }, { "answer": "Axiom MCP Server uses an OAuth sign-in. Grafana MCP Server takes an API key or an OAuth sign-in.", "question": "Do Axiom MCP Server and Grafana MCP Server need an API key?" }, { "answer": "Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp. Grafana MCP Server runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Axiom MCP Server and Grafana MCP Server without installing anything?" }, { "answer": "No open-source release is listed for Axiom MCP Server. Grafana MCP Server is open source (Apache-2.0).", "question": "Are Axiom MCP Server and Grafana MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 72 against 67" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card", "No incidents deducted, where Grafana MCP Server loses 7 points for them" ], "goodFor": "Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.", "slug": "axiom", "watchFor": "The server is closed source and tool input schemas are only visible through an authenticated session" }, { "aheadOn": [ "Reliability, 91 against 72", "Schema \u0026 documentation, 81 against 62", "Agent ergonomics, 74 against 63", "Maintenance \u0026 community, 96 against 83", "Transparency \u0026 trust, 80 against 70" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Open source" ], "goodFor": "Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.", "slug": "grafana-mcp-server", "watchFor": "The default set is 79 tools, and 119 with every category on, counted from the registration code in source" } ], "history": { "axiom": null, "grafana-mcp-server": [ { "causes": [ "event" ], "date": "2026-11-01", "delta": -3, "from": 74, "fromGrade": "BB", "to": 71, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 73.9, "fromGrade": "BB", "to": 74, "toGrade": "BB" }, { "causes": [ "product", "evidence", "event" ], "date": "2026-10-17", "delta": -0.6, "from": 74.5, "fromGrade": "BB", "to": 73.9, "toGrade": "BB" } ] }, "job": { "capability": "observability.logs", "name": "Observability logs" }, "others": [ { "json": "https://www.anchorterminal.com/compare/axiom-vs-incident-io.json", "title": "Axiom MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/axiom-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.json", "title": "Axiom MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.json", "title": "Axiom MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server.json", "title": "Causely MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.json", "title": "Grafana MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp.json", "title": "Grafana MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.json", "title": "Grafana MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-better-stack.json", "title": "Axiom MCP Server vs Better Stack", "url": "https://www.anchorterminal.com/compare/axiom-vs-better-stack" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-causely.json", "title": "Axiom MCP Server vs Causely MCP server", "url": "https://www.anchorterminal.com/compare/axiom-vs-causely" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.json", "title": "Axiom MCP Server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json", "title": "Axiom MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.json", "title": "Axiom MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.json", "title": "Better Stack vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.json", "title": "Datadog MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.json", "title": "Grafana MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.json", "title": "Grafana MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.json", "title": "Axiom MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp.json", "title": "Grafana MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp" } ], "panel": null, "scores": [ { "axiom": 72, "by": 19, "edge": "grafana-mcp-server", "grafana-mcp-server": 91, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "axiom": 62, "by": 19, "edge": "grafana-mcp-server", "grafana-mcp-server": 81, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "axiom": 63, "by": 11, "edge": "grafana-mcp-server", "grafana-mcp-server": 74, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "axiom": 72, "by": 5, "edge": "axiom", "grafana-mcp-server": 67, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "axiom": 60, "by": 0, "edge": "", "grafana-mcp-server": 60, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "axiom": 83, "by": 13, "edge": "grafana-mcp-server", "grafana-mcp-server": 96, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "axiom": 70, "by": 10, "edge": "grafana-mcp-server", "grafana-mcp-server": 80, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grafana MCP Server scores 71 (BB) on agent readiness against Axiom MCP Server's 68.2 (B), and leads in 5 of 7 scored categories. Axiom MCP Server leads on security \u0026 auth. Both do observability logs.", "tasks": null, "tutorials": [], "verdicts": { "axiom": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "grafana-mcp-server": "Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server", "json": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.min.md" }, "markdown": "Grafana MCP Server scores 71 (BB) on agent readiness against Axiom MCP Server's 68.2 (B), and leads in 5 of 7 scored categories. Axiom MCP Server leads on security \u0026 auth. Both do observability logs.\n\n- Axiom MCP Server: grade B, 68.2/100, rank #269 of 1349. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.json\n- Grafana MCP Server: grade BB, 71/100, rank #154 of 1349. Markdown https://www.anchorterminal.com/tools/grafana-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Axiom MCP Server (B)\n\nGood for: Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.\n\nAhead on:\n- Security \u0026 auth, 72 against 67\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n- No incidents deducted, where Grafana MCP Server loses 7 points for them\n\nWatch for: The server is closed source and tool input schemas are only visible through an authenticated session\n\n### Grafana MCP Server (BB)\n\nGood for: Teams on Grafana, self-managed or Cloud, that want an agent to read dashboards and query Prometheus, Loki, Tempo and Pyroscope, and to work with alert rules, incidents and OnCall.\n\nAhead on:\n- Reliability, 91 against 72\n- Schema \u0026 documentation, 81 against 62\n- Agent ergonomics, 74 against 63\n- Maintenance \u0026 community, 96 against 83\n- Transparency \u0026 trust, 80 against 70\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Open source\n\nWatch for: The default set is 79 tools, and 119 with every category on, counted from the registration code in source\n\n\n## Why the edge\n\n### Reliability: Grafana MCP Server +19\n\n- Axiom MCP Server (72): Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.\n- Grafana MCP Server (91): Scored as local software, since the owner runs it over stdio, SSE or streamable HTTP. Official PyPI package `mcp-grafana` (a wheel that carries the Go binary, Python 3.10 or later), a Docker image, release binaries and a Helm chart, with Grafana 9.0 or later stated as the requirement (20). Unit, integration and end-to-end workflows all concluded in success on main on 8 October 2026, per the 8 October check, not re-read on 1 November (25). Per the 8 October check, not re-read on 1 November, 54 open issues, none labelled bug, and 38 closed in the 30 days before that check. Three bug reports remained open from July and August (#992 `run_panel_query` 422, #1005 `grafana_api_request` 500 on plugin resources, #1049 a dropped table row in `get_panel_image`), each with replies. A stale issue and pull request workflow was added on 27 October (19 of 25). The changelog follows Keep a Changelog and semantic versioning and labels breaking changes, and 1.6.2 announced that 2.0 came next. Patch release 1.4.1 carried a breaking parameter change on the Sift tools, 2.0.0 followed 1.0.0 by two months, and minor release 2.1.0 on 20 October changed the output of `list_users_by_org`, labelled on the day (12 of 15). Version 2.1.1, the latest release on 1 November (15).\n\n### Schema \u0026 documentation: Grafana MCP Server +19\n\n- Axiom MCP Server (62): The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use `queryMetrics` for metrics datasets instead of `queryDataset`, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.\n- Grafana MCP Server (81): Read from source at tag v2.0.2, without running it, and unchanged in count at v2.1.1. All 79 default tools build their JSON Schema input by reflection from a typed Go parameter struct, and `buildInputSchema` in `tools.go` sets `additionalProperties` to false. No tool sets an output schema, which issue #1278 asks for (23 of 25). grafana.com serves llms.txt and a Markdown form of every docs page, the MCP pages included (10). Descriptions state purpose and inputs. Version 2.0.2 removed model directives and references to other tools from descriptions to meet connector directory rules, so guidance on when to use a tool is thinner than it was (14 of 20). Nearly every parameter field in the source structs carries a description tag, but few declare an enum. Values such as `queryType` ('range' or 'instant') and incident `status` are named in prose, and some parameters are free-form objects (9 of 15). The docs have client configuration examples, task guides and a troubleshooting page, and empty results return hints. No catalogue of error responses was found (10 of 15). Semantic versions, tagged releases and a dated changelog (15).\n\n### Maintenance \u0026 community: Grafana MCP Server +13\n\n- Axiom MCP Server (83): Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.\n- Grafana MCP Server (96): v2.1.1 tagged on 20 October 2026, 12 days before the check, after v2.1.0 the same day, with commits on main to 31 October (30). 17 tagged releases from 1.1.0 on 10 August to 2.1.1 in the 90 days to 1 November (20). Per the 8 October check, not re-read on 1 November, 38 issues closed in the 30 days before that check against 54 open and 22 open pull requests, and several feature requests from March and April without a reply (21 of 25). Listed in the official MCP registry as `io.github.grafana/mcp-grafana`, a GitHub-verified namespace, with v2.1.1 published on 20 October and marked latest (15). Renovate, a Docker image scan workflow, cosign signing with SPDX SBOMs for releases from 2.1.0, and Go toolchain and dependency bumps for CVEs on 21 and 28 October (10).\n\n### Agent ergonomics: Grafana MCP Server +11\n\n- Axiom MCP Server (63): 31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.\n- Grafana MCP Server (74): 79 tools load by default and 119 with every category on, counted from the registration code in `cmd/mcp-grafana/main.go` and `tools/*.go` at tag v2.0.2, with no tool added or removed by v2.1.1. That is 5 of 25 by count, plus 9 for `--enabled-tools`, per-category `--disable-*` flags, 12 opt-in categories and `--disable-write`, which leaves 62 (14). `limit` and `page` on searches, `get_dashboard_summary`, JSONPath reads through `get_dashboard_property`, a jq filter on `grafana_api_request`, and a 100-line default on `query_loki_logs` with an optional byte and time-range guardrail (18 of 20). Unknown argument keys are rejected with the valid ones listed, empty results carry likely causes and next steps, and TraceQL errors return correction hints. No documented error list (16 of 20). In source every default tool sets `readOnlyHint` and `destructiveHint` (60 read-only, 9 marked destructive), and 73 of 79 also set `idempotentHint`. The six that leave it unset are writes, for which the protocol default is false. No idempotency keys on creates (17 of 20). Most parameters are optional in the source structs. The Go module is the only library, with a Python wrapper for install (9 of 15).\n\n### Transparency \u0026 trust: Grafana MCP Server +10\n\n- Axiom MCP Server (70): Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.\n- Grafana MCP Server (80): Apache-2.0 (30). Local software that talks to the configured Grafana. A docs page lists every field in the usage report, the destination, and the region and network name the receiving service adds, and the Grafana Labs privacy policy (last updated 10 July 2026) covers usage statistics from its open-source software. No retention period for the reports was found (24 of 30). No deprecation policy. Notices come without dates, such as `GRAFANA_API_KEY` to be removed 'in a future version', and the Sift tools were marked deprecated before 2.0.0 removed them (10 of 20). Usage statistics are documented with three opt-outs and a `log` mode that prints the report without sending it. They arrived off by default in 1.5.0 on 17 September 2026 and were switched on by default in 2.0.0, noted in the changelog (17 of 20).\n\n### Security \u0026 auth: Axiom MCP Server +5\n\n- Axiom MCP Server (72): Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.\n- Grafana MCP Server (67): The server holds a Grafana service account token, which Grafana RBAC can scope by action and resource and which can be revoked. `GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE` is re-read on each request for rotation. Username and password and a deprecated API key also work. The open-source server has no OAuth, and no secret travels in a URL (25 of 30). `--disable-write`, `--disable-query`, per-category flags, Loki enforced matchers and a per-tool RBAC table support least privilege. Writes are on by default, the default set includes `grafana_api_request` for any API path, and nothing asks for confirmation (14 of 20). Log lines, dashboards and annotations reach the model as stored. No injection guidance was found in the README or docs, and issue #680 on the subject has been open since 24 March 2026 (2 of 15). OpenTelemetry traces, metrics and logs per tool call and slow-request logging, with arguments left out of spans unless `--include-args-in-spans` is set (10 of 15). Grafana Labs runs a disclosure programme on Intigriti without bounties, lists ISO 27001 and SOC 2 Type 2, and publishes advisories on grafana.com, two of them for this server (CVE-2026-15583 on 15 July and CVE-2026-19516 on 11 August 2026). The repository has no SECURITY.md and grafana.com has no security.txt (16 of 20).\n\n## Score by category\n\n| Category | Weight | Axiom MCP Server | Grafana MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 91 | Grafana MCP Server +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 81 | Grafana MCP Server +19 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 74 | Grafana MCP Server +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 67 | Axiom MCP Server +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 96 | Grafana MCP Server +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 80 | Grafana MCP Server +10 |\n| Negative events | ≤15 | 0 | -7 | |\n| **Total** | | **68.2 · B** | **71 · BB** | |\n\n## Facts side by side\n\n| Fact | Axiom MCP Server | Grafana MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Axiom, Inc. | Grafana Labs |\n| Hosted endpoint | `https://mcp.axiom.co/mcp` | no (local only) |\n| Transports | Streamable HTTP, SSE (legacy) | stdio, SSE (legacy), Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | none | Apache-2.0 |\n| Tools exposed | 31 | 119 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `co.axiom/mcp` | `io.github.grafana/mcp-grafana` |\n| Last release | 2026-10-29 | 2026-10-20 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | 2026-07-10 |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | none | 3.5k stars, 152k PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Axiom MCP Server\n\nNo score change since it was listed.\n\n### Grafana MCP Server\n\n- -3.0 on 1 November 2026: negative event\n- +0.1 on 28 October 2026: checklist\n- -0.6 on 17 October 2026: product, new evidence, negative event\n\n## Verdicts\n\n**Axiom MCP Server.** An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.\n\n**Grafana MCP Server.** Every default tool declares typed inputs and read-only and destructive annotations in source, and `--disable-write` cuts the default 79 tools to 62. Writes and a general `grafana_api_request` tool are on by default, the default list is long at 79 tools, and two `X-Grafana-URL` flaws, one rated critical, were fixed in July and August 2026.\n\n## Before you call either\n\n### Axiom MCP Server\n\n1. With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed\n2. Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL\n3. Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner\n4. Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first\n5. `deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting\n\n### Grafana MCP Server\n\n1. Start with `--disable-write` unless the task needs writes, and add `--disable-api` to remove `grafana_api_request`\n2. Pass `--enabled-tools` with only the categories needed. The default list loads 79 tools\n3. Use `get_dashboard_summary` or `get_dashboard_property` with a JSONPath before `get_dashboard_by_uid`, which returns the whole dashboard JSON\n4. Set `GRAFANA_USAGE_STATS=disabled` or `DO_NOT_TRACK=1` to stop the four-hourly usage report to stats.grafana.org\n5. Use streamable HTTP, not SSE, when each caller needs its own token or organisation, and set `--server-auth-token` on any non-loopback address\n\n## Questions\n\n### Which is better for AI agents, Axiom MCP Server or Grafana MCP Server?\n\nGrafana MCP Server scores 71 (BB) on agent readiness against Axiom MCP Server's 68.2 (B), and leads in 5 of 7 scored categories. Axiom MCP Server leads on security \u0026 auth.\n\n### Do Axiom MCP Server and Grafana MCP Server need an API key?\n\nAxiom MCP Server uses an OAuth sign-in. Grafana MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call Axiom MCP Server and Grafana MCP Server without installing anything?\n\nAxiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp. Grafana MCP Server runs on your own machine, with no hosted endpoint listed.\n\n### Are Axiom MCP Server and Grafana MCP Server open source?\n\nNo open-source release is listed for Axiom MCP Server. Grafana MCP Server is open source (Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.json, and with the fewest tokens: https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"axiom\", \"b\": \"grafana-mcp-server\"}`. From a terminal: `anchor compare axiom grafana-mcp-server`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/axiom.json and https://www.anchorterminal.com/api/v1/tools/grafana-mcp-server.json\n\n## Other comparisons with Axiom MCP Server or Grafana MCP Server\n\n- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md)\n- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md)\n- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md)\n- [Causely MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/causely-vs-grafana-mcp-server.md)\n- [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md)\n- [Grafana MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp.md)\n- [Grafana MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)\n- [Axiom MCP Server vs Causely MCP server](https://www.anchorterminal.com/compare/axiom-vs-causely.md)\n- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)\n- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md)\n- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)\n- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)\n- [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md)\n- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md)\n- [Grafana MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-sentry-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Axiom MCP Server vs Grafana MCP Server", "url": "" } ], "description": "Grafana scores 71 (BB) to Axiom's 68.2 (B) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Axiom MCP Server B 68.2", "Grafana MCP Server BB 71", "scores" ], "h1": "Axiom MCP Server vs Grafana MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/axiom-vs-grafana-mcp-server", "published": "2026-10-01", "section": "tools", "title": "Axiom vs Grafana for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server" }, "tokens": { "markdown": 5750, "slim": 3880 }, "version": 1 }