{
  "listings": [
    {
      "slug": "axiom",
      "name": "Axiom MCP Server",
      "company": "Axiom, Inc.",
      "grade": "BB",
      "fit": "yes",
      "why": "queryDataset takes APL and queryMetrics takes MPL directly; getMonitorHistory and services-getChanges give the alert and what changed; query cost limits return a 429 naming the limit. Accounts acc-15 and acc-16 describe agents finding traces and alerts this way.",
      "source": "https://axiom.co/docs/console/intelligence/mcp-server/tools",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/axiom"
    },
    {
      "slug": "better-stack",
      "name": "Better Stack",
      "company": "Better Stack, Inc.",
      "grade": "C",
      "fit": "yes",
      "why": "Execute query runs ClickHouse SQL over logs, spans, metrics and exceptions; incident details and timeline give the alert; Plan query windows splits long ranges; a Read token keeps it to reads. acc-14 uses it daily to resolve reported errors.",
      "source": "https://betterstack.com/docs/getting-started/integrations/mcp/",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/better-stack"
    },
    {
      "slug": "causely",
      "name": "Causely MCP server",
      "company": "Causely, Inc.",
      "grade": "E",
      "fit": "yes",
      "why": "get_alerts, investigate_alert, get_issues and get_diagnosis_details return the inferred cause with causal chain, blast radius, logs, exceptions and events, and get_diagnoses takes a start and end window; all reads.",
      "source": "https://docs.causely.ai/agent-integration/mcp-server/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/causely"
    },
    {
      "slug": "datadog-mcp",
      "name": "Datadog MCP Server",
      "company": "Datadog, Inc.",
      "grade": "D",
      "fit": "yes",
      "why": "Core toolset searches logs, spans, metrics, monitors and events with Datadog query syntax, analyze_datadog_logs takes SQL, and get_datadog_trace follows a trace. Accounts acc-05, acc-06 and acc-07 describe agents debugging production this way.",
      "source": "https://docs.datadoghq.com/bits_ai/mcp_server/tools/",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/datadog-mcp"
    },
    {
      "slug": "grafana-mcp-server",
      "name": "Grafana MCP Server",
      "company": "Raintank Inc., d/b/a Grafana Labs",
      "grade": "BB",
      "fit": "yes",
      "why": "PromQL, LogQL and TraceQL tools take native queries, alerting_rules_read and OnCall alert groups give the alert, get_tempo_trace follows a trace id, and --disable-write keeps it to reads. acc-08, acc-11 and acc-12 run incident work this way.",
      "source": "https://github.com/grafana/mcp-grafana",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/grafana-mcp-server"
    },
    {
      "slug": "honeycomb-mcp",
      "name": "Honeycomb MCP",
      "company": "Hound Technology, Inc. d/b/a Honeycomb",
      "grade": "B",
      "fit": "yes",
      "why": "run_query takes a Honeycomb query spec, get_triggers gives the alert, get_trace follows a trace id and run_bubbleup isolates what differs, all read tools. acc-09 and acc-10 describe alert and regression investigations that return a full report.",
      "source": "https://docs.honeycomb.io/integrations/mcp/tools",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/honeycomb-mcp"
    },
    {
      "slug": "new-relic",
      "name": "New Relic MCP Server",
      "company": "New Relic, Inc.",
      "grade": "B",
      "fit": "yes",
      "why": "execute_nrql_query takes NRQL directly; search_incident, list_recent_issues and list_change_events give the alert and what changed; search_errors takes a trace id and get_distributed_trace_details follows it. The server is read-only by scope.",
      "source": "https://docs.newrelic.com/docs/agentic-ai/mcp/tool-reference/",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/new-relic"
    },
    {
      "slug": "sentry-mcp",
      "name": "Sentry MCP",
      "company": "Functional Software, Inc. d/b/a Sentry",
      "grade": "B",
      "fit": "yes",
      "why": "search_errors, search_traces and search_logs, get_trace_details and get_sentry_resource with an issue or trace URL give errors, traces and logs with ids; find_metric_monitors gives the alert. acc-05 and acc-16 use it for incidents and inbound alerts.",
      "source": "https://github.com/getsentry/sentry-mcp/tree/main/packages/mcp-core/src/tools/catalog",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/sentry-mcp"
    },
    {
      "slug": "cronitor-mcp",
      "name": "Cronitor MCP server",
      "company": "Cronitor",
      "grade": "C",
      "fit": "caveat",
      "why": "get_status, list_issues and get_metrics show which job, heartbeat or check failed and its latest event, but there are no logs or traces, so causes outside the monitored job are out of reach.",
      "source": "https://cronitor.io/docs/mcp-server",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/cronitor-mcp"
    },
    {
      "slug": "incident-io",
      "name": "incident.io API",
      "company": "Pineapple Technology Ltd.",
      "grade": "B",
      "fit": "caveat",
      "why": "alert_show, incident_show and investigation_sync give the alert, linked incidents and findings, but telemetry is reached only through ask_telemetry, a natural-language agent that needs the Investigations product, so queries and series are not the agent's own.",
      "source": "https://docs.incident.io/ai/remote-mcp.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/incident-io"
    },
    {
      "slug": "pagerduty-mcp",
      "name": "PagerDuty MCP Server",
      "company": "PagerDuty, Inc.",
      "grade": "E",
      "fit": "caveat",
      "why": "browse_incidents lists alerts, notes, change events and related or past incidents, but PagerDuty holds no metrics, logs or traces, so the cause needs another server.",
      "source": "https://docs.pagerduty.com/ai-automation/advance/pagerduty-mcp-server.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/pagerduty-mcp"
    },
    {
      "slug": "rootly-mcp",
      "name": "Rootly MCP Server",
      "company": "Rootly Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "core and alerts toolsets read incidents and alerts, and an observability toolset reads Rootly Observability logs and patterns; there are no metrics or traces, and logs exist only for teams on Rootly Observability.",
      "source": "https://docs.rootly.com/integrations/mcp-server",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/rootly-mcp"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "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-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "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"
  },
  "useCase": {
    "accounts": 13,
    "after": [
      "code.open-pr",
      "observability.oncall-and-incident-records",
      "messaging.post-summary"
    ],
    "area": "developer",
    "asks": [
      "why did this alert fire",
      "why is the app slow",
      "debug this incident",
      "what changed before latency went up"
    ],
    "before": [
      "notifications.alert-received",
      "messaging.slack-thread",
      "observability.oncall-and-incident-records"
    ],
    "blockers": [
      "the relevant signal was never collected",
      "agent misreads which layer an alert belongs to",
      "query-cost or rate cap reached mid-investigation",
      "tool list fills the context before the first query"
    ],
    "capabilities": [
      "observability.metrics",
      "observability.logs",
      "observability.traces",
      "observability.incidents"
    ],
    "category": "observability",
    "categoryName": "Observability \u0026 incidents",
    "checked": "2026-11-15",
    "companies": {
      "fit": 8,
      "fitWithLimit": 4,
      "tagged": 15
    },
    "competition": "crowded",
    "fits": [
      "axiom",
      "better-stack",
      "causely",
      "datadog-mcp",
      "grafana-mcp-server",
      "honeycomb-mcp",
      "new-relic",
      "sentry-mcp"
    ],
    "fitsWithLimit": [
      "cronitor-mcp",
      "incident-io",
      "pagerduty-mcp",
      "rootly-mcp"
    ],
    "id": "observability.investigate-alert",
    "listings": {
      "caveat": 4,
      "no": 0,
      "notRead": 0,
      "tagged": 15,
      "unchecked": 0,
      "yes": 8
    },
    "name": "Find the cause of an alert or incident across metrics, logs and traces",
    "status": "draft",
    "success": "A short report naming the likely cause, the queries or evidence behind it (series, log lines or trace ids with timestamps) and the time window, built only from read calls. Measured: report within 15 minutes and 30 tool calls.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/observability.investigate-alert.json",
    "weight": 26,
    "weightBasis": "13 of 42 accounts (about 26 per cent of the 50 account-to-use-case links); the job most often described in the Ask HN MCP-in-production thread and the SRE threads"
  }
}
