{
  "data": {
    "a": {
      "slug": "better-stack",
      "name": "Better Stack",
      "vendor": "Better Stack, Inc.",
      "vendorUrl": "https://betterstack.com",
      "company": "betterstack.com",
      "kind": "mcp",
      "category": "observability",
      "summary": "Better Stack is a hosted observability and incident management service from Better Stack, Inc. with uptime monitors, on-call, status pages, logs, metrics, traces and error tracking, reached through REST APIs and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/better-stack",
      "markdownUrl": "https://www.anchorterminal.com/tools/better-stack.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/better-stack.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/better-stack.json",
      "dns": "better-stack.grade.anchorterminal.com",
      "repo": "https://github.com/BetterStackHQ/claude-plugin",
      "license": "Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://mcp.betterstack.com",
      "packages": [],
      "auth": "mixed",
      "authNotes": "OAuth sign-in in the browser is the documented default for the MCP server, with a Full access level chosen at consent for writes. Unattended agents send an API token as a Bearer header. Tokens are minted in the web app under API tokens, either global (every team) or team-based (Incidents API or Telemetry API tokens), with Read \u0026 write or read access per the MCP docs. No scopes finer than that and no key expiry were found. Access is self-serve after a browser signup.",
      "pricing": "freemium",
      "pricingNotes": "The MCP server and APIs carry no separate charge. The Free plan has 10 monitors and heartbeats, one status page, 3 GB of logs and traces kept 3 days, 30 GB of metrics and 100,000 errors a month, with no card mentioned on the signup page. Responders cost $34 a month ($29 yearly), telemetry is priced per GB by region ($0.10 ingestion and $0.05 retention per GB in Europe, $0.15 and $0.08 in the US, $0.35 and $0.18 in Singapore) or in bundles from $30 a month, and audit logs are a $250 a month add-on (https://betterstack.com/pricing, checked 2026-11-03).",
      "priceSummary": "$34 / seat-mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the pricing page, the API docs or the MCP docs (checked 2026-11-03). Plans are paid by card through the web app.",
        "endpoints": []
      },
      "toolCount": 148,
      "popularity": {
        "githubStars": 6,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://betterstack.com/docs/getting-started/integrations/mcp/",
      "capabilities": [
        "observability.logs",
        "observability.incidents",
        "work.oncall",
        "observability.metrics",
        "observability.traces",
        "observability.errors"
      ],
      "tags": [
        "official",
        "hosted",
        "closed-source",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "toolsets",
        "free-tier",
        "freemium",
        "eu-hosted",
        "status-page",
        "audit-log",
        "soc2",
        "webhooks"
      ],
      "lastRelease": "2026-11-02",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 56.7,
        "grade": "C",
        "agentReady": false,
        "rank": 918,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 55,
          "maintenance": 71,
          "payments": 60,
          "reliability": 50,
          "schema": 46,
          "security": 60,
          "transparency": 69
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.",
        "bestFor": "An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.",
        "strengths": [
          "148 tools across incidents, on-call, monitors, heartbeats, status pages, catalogue, telemetry queries, dashboards, alerts, errors and team members, on one remote endpoint",
          "X-MCP-Tools-Only and X-MCP-Tools-Except headers give a read-only or task-sized subset, and OAuth consent or a token can be read-level",
          "Audit logs record API token requests with the token's name and the actor type, and can be streamed to a source or any URL",
          "Free plan with 10 monitors, a status page and 3 GB of logs, and per-GB prices published by region",
          "Dated changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026, and a plugin release on 2 November 2026"
        ],
        "weaknesses": [
          "No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying",
          "The MCP tool schemas are not published, the REST API has no OpenAPI file and the docs have no llms.txt",
          "No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature",
          "Delayed Telemetry data processing in the Europe region ran from 3 to 6 September 2026 in entries of 6 hours to 1 day",
          "Audit logs cost $250 a month, and no security.txt, bug bounty or disclosure policy was found"
        ],
        "agentNotes": [
          "Connect with `claude mcp add betterstack --transport http https://mcp.betterstack.com` and sign in, or send a team-based API token as `Authorization: Bearer`; pick Read access unless the task writes",
          "Send `X-MCP-Tools-Only: monitors,monitor,incidents` or a similar list to keep the 148-tool list out of context, and `X-MCP-Tools-Except: remove_dashboard,remove_chart` to block deletes",
          "Call `Get query instructions` or `Plan query windows` before `Execute query`, since long time ranges are split into windows and nothing documents a result size limit",
          "No rate limit is published. Back off on a 429 and don't retry writes blindly, because there are no idempotency keys; `Upsert catalog records` is the one write documented as safe to repeat",
          "Reopening an incident only works within 24 hours of its resolution, and a comment can only be edited or removed by its author or an API token"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 56.7
          }
        ],
        "editorialScores": {
          "ergonomics": 55,
          "maintenance": 71,
          "payments": 60,
          "reliability": 50,
          "schema": 46,
          "security": 60,
          "transparency": 48
        },
        "provenanceScore": 89,
        "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",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-03",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -H \"Authorization: Bearer $BETTERSTACK_API_TOKEN\" https://incidents.betterstack.com/api/v2/monitors",
        "claudeCode": "claude mcp add betterstack --transport http https://mcp.betterstack.com",
        "config": {
          "mcpServers": {
            "betterstack": {
              "type": "http",
              "url": "https://mcp.betterstack.com"
            }
          }
        },
        "headless": {
          "mcpServers": {
            "betterstack": {
              "headers": {
                "Authorization": "Bearer $TOKEN"
              },
              "type": "http",
              "url": "https://mcp.betterstack.com"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.logs",
        "tool": "https://letme.dev/better-stack"
      },
      "area": "developer",
      "unitPrices": [
        {
          "item": "Responder seat",
          "unit": "seat-month",
          "usd": 34,
          "note": "$29 a month billed yearly; team members without incident access are free"
        },
        {
          "item": "Logs and traces ingestion, Europe",
          "unit": "gb",
          "usd": 0.1,
          "note": "$0.15 in the US and $0.35 in Singapore, plus retention from $0.05 per GB a month"
        },
        {
          "item": "Telemetry Nano bundle, Europe",
          "unit": "month",
          "usd": 30,
          "note": "40 GB each of logs, traces and metrics with 30-day retention; $45 in the US"
        },
        {
          "item": "Additional status page",
          "unit": "month",
          "usd": 15,
          "note": "one page included; $12 billed yearly"
        },
        {
          "item": "Audit logs add-on",
          "unit": "month",
          "usd": 250,
          "note": "$208 billed yearly"
        }
      ],
      "provenance": {
        "legalEntity": "Better Stack, Inc.",
        "domain": "betterstack.com",
        "domainRegistered": "2013-02-08",
        "endpointOnVendorDomain": true,
        "terms": "https://betterstack.com/terms",
        "privacy": "https://betterstack.com/privacy",
        "statusPage": "https://status.betterstack.com/",
        "changelog": "https://betterstack.com/tag/changelog",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "The Terms of Use (last updated 14 February 2025) and the privacy policy (25 November 2022) name Better Stack, Inc., a Delaware corporation, under New York law. The DPA (25 February 2025) and its schedules (14 February 2025) list nine subprocessors.",
          "The terms contain no clause on automated access to the site or the API. They forbid monitoring systems the user doesn't own and allow Better Stack to impose quotas and time limits.",
          "betterstack.com/robots.txt disallows nothing and carries Content-Signal search=yes, ai-input=yes, ai-train=yes. status.betterstack.com/robots.txt is empty.",
          "The MCP server answers at mcp.betterstack.com and the APIs at incidents.betterstack.com, telemetry.betterstack.com and betterstack.com, all vendor subdomains. The ClickHouse query endpoint is on betterstackdata.com.",
          "betterstack.com/.well-known/security.txt returns 404. The security page gives security@betterstack.com and names no bug bounty or disclosure policy.",
          "RDAP gives betterstack.com a registration date of 8 February 2013, before the company's 2021 founding per its careers page, so the domain was acquired."
        ],
        "score": 89
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/better-stack.json",
      "live": {
        "slug": "better-stack",
        "probe": {
          "target": "https://mcp.betterstack.com",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:13:11.074095213Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 105,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 57,
          "p95ms24h": 225,
          "samples24h": 241,
          "samples30d": 3418,
          "days": [
            {
              "date": "2026-11-04",
              "probes": 87,
              "ok": 87
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 233,
              "ok": 233
            }
          ],
          "since": "2026-11-04T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.betterstack.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:51:54.371133379Z"
        },
        "githubStars": 6,
        "securityTxt": {
          "url": "https://betterstack.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:32:00.981669913Z"
        },
        "domain": {
          "domain": "betterstack.com",
          "registered": "2013-02-08",
          "source": "https://rdap.verisign.com/com/v1/domain/betterstack.com",
          "checkedAt": "2026-11-15T15:25:27.770837813Z"
        },
        "pages": [
          {
            "url": "https://betterstack.com/tag/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:54.582662867Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "1f20ca3dcacc"
          },
          {
            "url": "https://betterstack.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-18T21:33:50.407134785Z",
            "changedAt": "2026-11-06T13:22:49.376519607Z",
            "fingerprint": "4423e6668f57"
          },
          {
            "url": "https://betterstack.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:52.54394793Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "0f5678b89d3a"
          },
          {
            "url": "https://betterstack.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:56.606567747Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "f78bcc7d4cc3"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.betterstack.com",
          "checkedAt": "2026-11-18T04:22:06.163240869Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-05T01:29:02.104349366Z"
        },
        "github": {
          "repo": "betterstackhq/claude-plugin",
          "checkedAt": "2026-11-16T11:18:37.580999415Z",
          "stars": 6,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-16T10:48:36Z",
          "openIssues": 0,
          "openPRs": 1,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 21
        },
        "updatedAt": "2026-11-18T23:13:11.074095213Z"
      },
      "streak": {
        "days": 14,
        "from": "2026-11-04",
        "sinceWatching": true,
        "best": 14
      }
    },
    "answer": "Better Stack scores 56.7 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
    "b": {
      "slug": "neat-pulse-mcp",
      "name": "Neat Pulse MCP",
      "vendor": "Neat",
      "vendorUrl": "https://neat.no",
      "company": "neat.no",
      "kind": "mcp",
      "category": "observability",
      "summary": "Neat Pulse MCP is Neat's local MCP server for Neat Pulse, the cloud service that manages Neat's meeting-room video devices. Agents list devices and rooms, read sensor data, reboot devices and change room set-up, for paid Pulse customers.",
      "url": "https://www.anchorterminal.com/tools/neat-pulse-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json",
      "dns": "neat-pulse-mcp.grade.anchorterminal.com",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@neat-no/pulse-mcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Neat Pulse API token in `PULSE_API_TOKEN`, with the organisation ID in `PULSE_ORG_ID`. Only an Owner of the Pulse organisation can create tokens, in the portal under Settings \u003e API Keys. A token takes either the Read scope or all scopes, is shown once, can be revoked, and the Pulse API has a key-rotation endpoint. The token's name appears in Pulse's audit logs.",
      "pricing": "byo-plan",
      "pricingNotes": "Included at no extra cost with a paid Neat Pulse Plus or Pro plan, and every device in the organisation must be on a paid plan. Plus and Pro are sold through resellers, with no public price. The free Pulse Starter plan doesn't include MCP or API access.",
      "priceSummary": "Your plan",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on neat.no, support.neat.no or the Pulse API reference, read on 2026-11-18. Pulse plans are bought through resellers.",
        "endpoints": []
      },
      "toolCount": 30,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://support.neat.no/article/neat-pulse-mcp-server/",
      "capabilities": [
        "observability.metrics"
      ],
      "tags": [
        "mcp",
        "stdio",
        "npm",
        "node",
        "api-key",
        "audit-log",
        "read-only-mode",
        "hardware",
        "meeting-rooms",
        "paid-plan",
        "iso-27001"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 45.8,
        "grade": "E",
        "agentReady": false,
        "rank": 1268,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 56
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.",
        "bestFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "strengths": [
          "A Pulse API token can be limited to the Read scope, which the docs say stops the server rebooting, deleting, creating or updating anything",
          "Every action taken through the MCP server is recorded in Pulse's audit logs under the token's name, and `list_audit_logs` reads them",
          "security.txt, a vulnerability reporting policy, public security advisories through 2026 and an ISO 27001 statement on Neat's support site",
          "Version 1.1.0 on 17 November 2026, four releases since 17 September 2026, and setup steps for seven MCP clients",
          "A data model guide served as an MCP resource and a tool, with IDs, hierarchy and which actions can't be undone"
        ],
        "weaknesses": [
          "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent",
          "No public source repository, licence, changelog or status page found",
          "Irreversible tools (delete room, delete device, reboot, reset enrolment code) rely on the assistant asking first. No server-side confirmation was found",
          "No rate limits or 429 handling documented for the server or the Pulse API",
          "Runs only in clients that can start local programs, and needs Node.js 20 or later"
        ],
        "agentNotes": [
          "Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices",
          "Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room",
          "Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy",
          "If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`",
          "If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 45.8
          }
        ],
        "editorialScores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 47
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx -y @neat-no/pulse-mcp@latest   # needs PULSE_API_TOKEN and PULSE_ORG_ID in the environment",
        "claudeCode": "claude mcp add neat-pulse -s user -e PULSE_API_TOKEN=YOUR_PULSE_TOKEN -e PULSE_ORG_ID=YOUR_ORG_ID -- npx -y @neat-no/pulse-mcp@latest",
        "config": {
          "mcpServers": {
            "neat-pulse": {
              "args": [
                "-y",
                "@neat-no/pulse-mcp@latest"
              ],
              "command": "npx",
              "env": {
                "PULSE_API_TOKEN": "YOUR_PULSE_TOKEN",
                "PULSE_ORG_ID": "YOUR_ORG_ID"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/neat-pulse-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Neatframe Limited",
        "domain": "neat.no",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://neat.no/neat-pulse-terms-and-conditions/",
        "privacy": "https://neat.no/privacy-policy/",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Neat Pulse Agreement (last updated 26 March 2025) is between Neatframe Ltd. and the customer, and the privacy notice (13 July 2026) is Neatframe Limited's. The company page says Neat is based in Oslo.",
          "neat.no/robots.txt allows ClaudeBot and anthropic-ai outside account, cart, checkout and admin paths, with a crawl delay of 10 seconds. support.neat.no, api.pulse.neat.no and registry.npmjs.org allow all agents.",
          "neat.no/.well-known/security.txt gives security@neat.no, expires 7 August 2027 and links the vulnerability reporting policy on support.neat.no.",
          "No status page for Neat Pulse was linked from any page read. The MCP server calls the Pulse API at api.pulse.neat.no."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.json"
    },
    "edges": [
      {
        "by": 60,
        "category": "payments",
        "leads": "better-stack",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "Read with the hosted rubric. No x402, MPP or L402 (0). Per-unit prices are public without login, by GB and region for telemetry, per responder, per status page and per phone number (20). The Free plan has 10 monitors, a status page and 3 GB of logs, the signup page says Sign up for free and names no card, and we did not run the signup flow (20). A person signs up in a browser and mints a token or completes OAuth there (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.",
          "b": "No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0."
        },
        "scores": {
          "a": 60,
          "b": 0
        }
      },
      {
        "by": 19,
        "category": "security",
        "leads": "neat-pulse-mcp",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.",
          "b": "Scoped, revocable Pulse API tokens with a rotation endpoint, created only by organisation Owners and passed in an environment variable. The scopes are coarse, Read or everything (27). A Read-only token blocks every change per the setup guide, and the reference flags irreversible tools, but confirmation is left to the assistant (14). Room notes and device names are text people enter, and no prompt-injection guidance was found (5). Pulse audit logs record every MCP action under the token's name, and an MCP tool reads them (15). security.txt valid to August 2027, a vulnerability reporting policy, public advisories through November 2026, and a support article stating ISO 27001 certification. No bug bounty found (18). 27 + 14 + 5 + 15 + 18 = 79."
        },
        "scores": {
          "a": 60,
          "b": 79
        }
      },
      {
        "by": 15,
        "category": "reliability",
        "leads": "better-stack",
        "name": "Reliability",
        "reasons": {
          "a": "Read with the hosted lines and scored on the remote MCP server at mcp.betterstack.com, which fronts the same service as the Incidents and Telemetry APIs. status.betterstack.com runs on Better Stack's own status page product with three components and a 90-day history (20). Between 5 August and 3 November 2026 it records delayed Telemetry data processing in the Europe region from 3 to 6 September in entries of 6 hours 19 minutes, 10 hours 10 minutes, 19 hours 13 minutes, 21 hours 45 minutes and 1 day, a 9-minute Telemetry degradation on 20 August, 39 minutes of wrong downtime notifications on 21 October and 8 minutes of dashboard unavailability on 2 November, every one labelled degraded, plus two migrations labelled maintenance (11 hours 13 minutes on 9 August and 17 hours). About four days of delayed log processing in one region is more than trivial and less than an outage of the API, so between minor-only and one major (15). No rate limit numbers were found in the API or MCP docs (0). The Usage API documents a 429 with the instruction to wait before retrying, with no Retry-After, no backoff guidance and no idempotency keys. `Upsert catalog records` is documented as not creating duplicates when repeated (5 of 15). No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature (0). The MCP server was announced on 15 September 2025 and carries no beta label (10). 20 + 15 + 0 + 5 + 0 + 10 = 50.",
          "b": "Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35."
        },
        "scores": {
          "a": 50,
          "b": 35
        }
      },
      {
        "by": 13,
        "category": "transparency",
        "leads": "better-stack",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service under Terms of Use (14 February 2025) that name Better Stack, Inc., a Delaware corporation, under New York law. The plugins and Terraform providers are MIT (15 of 30). The privacy policy (25 November 2022) gives no retention periods and says data is processed primarily in the EU, while the DPA (25 February 2025) names the United States and other locations and promises return or destruction on termination. Telemetry retention is a plan term (3 days free, 30 days in bundles). OpenAI is a subprocessor and nothing says whether customer data is used for model training (14 of 30). No deprecation policy. The terms allow changes at Better Stack's discretion with continued use as acceptance, and the changelog carries no deprecation notices (3 of 20). Schedule A of the DPA lists nine subprocessors with locations, the security page says data is stored in EU regions by default with custom locations for enterprise, and no notice period for new subprocessors is given (16 of 20). 15 + 14 + 3 + 16 = 48.",
          "b": "Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47."
        },
        "scores": {
          "a": 69,
          "b": 56
        }
      },
      {
        "by": 12,
        "category": "ergonomics",
        "leads": "better-stack",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "148 tools are named on the docs page, more than 30 (5). X-MCP-Tools-Only and X-MCP-Tools-Except narrow the list to a subset or a read-only set, documented for that purpose, and the server has no default toolset (add 10, so 15). REST lists take page and per_page up to 250 with first, last, prev and next links, and filters by url, pronounceable_name and team_name. Plan query windows splits a long telemetry query into windows, and Execute query takes SQL with its own LIMIT. No field selection (16 of 20). 422 bodies name the field that failed and 401 gives a message, but no error code list exists and MCP errors are not documented (10 of 20). No idempotency keys. `Upsert catalog records` avoids duplicates, Reopen incident is limited to 24 hours, and the annotations on the tools couldn't be read (6 of 20). Get workspace style defaults are not described. Two Terraform providers and logging clients exist, but no official API SDK in any language, and the Claude plugin's 16 skills carry the query recipes (8 of 15). 15 + 16 + 10 + 6 + 8 = 55.",
          "b": "30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43."
        },
        "scores": {
          "a": 55,
          "b": 43
        }
      },
      {
        "by": 12,
        "category": "maintenance",
        "leads": "better-stack",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Read as a closed service. The Claude plugin reached 1.3.12 on 2 November 2026 and the changelog's newest entry is 29 October 2026 (30). Changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026 (20). Public changelog, hello@betterstack.com with a stated reply within a few hours, and a community site. GitHub issues on the plugin repositories were not read (10 of 15). The MCP server is not in the official MCP registry under a verified namespace, the only entries matching the name being third-party scrapers, and there is no official API SDK. The Claude, Cursor, Codex and Antigravity plugins and two Terraform providers are current (5 of 15). The Claude plugin repository is MIT with 12 commit days since June 2026, and we didn't read its CI (6 of 10). 30 + 20 + 10 + 5 + 6 = 71.",
          "b": "1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59."
        },
        "scores": {
          "a": 71,
          "b": 59
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Better Stack, Inc.",
        "b": "Neat",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.betterstack.com",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "148",
        "b": "30",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-02",
        "b": "2026-11-17",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "2025-03-26",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-07-13",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "6 stars",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Better Stack scores 56.7 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
        "question": "Which is better for AI agents, Better Stack or Neat Pulse MCP?"
      },
      {
        "answer": "Better Stack takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.",
        "question": "Do Better Stack and Neat Pulse MCP need an API key?"
      },
      {
        "answer": "Better Stack has a hosted endpoint at https://mcp.betterstack.com. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Better Stack and Neat Pulse MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 50 against 35",
          "Agent ergonomics, 55 against 43",
          "Payments \u0026 pricing, 60 against 0",
          "Maintenance \u0026 community, 71 against 59",
          "Transparency \u0026 trust, 69 against 56"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.",
        "slug": "better-stack",
        "watchFor": "No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying"
      },
      {
        "aheadOn": [
          "Security \u0026 auth, 79 against 60"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "slug": "neat-pulse-mcp",
        "watchFor": "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent"
      }
    ],
    "history": {
      "better-stack": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 54.2,
          "fromGrade": "C",
          "to": 56.7,
          "toGrade": "C"
        }
      ],
      "neat-pulse-mcp": null
    },
    "job": {
      "capability": "observability.metrics",
      "name": "Metrics and monitoring"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.json",
        "title": "Better Stack vs Cronitor MCP server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io.json",
        "title": "Better Stack vs incident.io API",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.json",
        "title": "Better Stack vs PagerDuty MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.json",
        "title": "Better Stack vs Rootly MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.json",
        "title": "Axiom MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.json",
        "title": "Causely MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json",
        "title": "Cronitor MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json",
        "title": "Datadog MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.json",
        "title": "Grafana MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.json",
        "title": "Honeycomb MCP vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json",
        "title": "Neat Pulse MCP vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic"
      },
      {
        "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/better-stack-vs-causely.json",
        "title": "Better Stack vs Causely MCP server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-causely"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.json",
        "title": "Better Stack vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp"
      },
      {
        "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/better-stack-vs-honeycomb-mcp.json",
        "title": "Better Stack vs Honeycomb MCP",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.json",
        "title": "Better Stack vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.json",
        "title": "Neat Pulse MCP vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.json",
        "title": "Better Stack vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp"
      }
    ],
    "panel": null,
    "scores": [
      {
        "better-stack": 50,
        "by": 15,
        "edge": "better-stack",
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "better-stack": 46,
        "by": 3,
        "edge": "neat-pulse-mcp",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "weight": 13
      },
      {
        "better-stack": 55,
        "by": 12,
        "edge": "better-stack",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "weight": 13
      },
      {
        "better-stack": 60,
        "by": 19,
        "edge": "neat-pulse-mcp",
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "weight": 14
      },
      {
        "better-stack": 60,
        "by": 60,
        "edge": "better-stack",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "better-stack": 71,
        "by": 12,
        "edge": "better-stack",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "weight": 7
      },
      {
        "better-stack": 69,
        "by": 13,
        "edge": "better-stack",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "weight": 7
      }
    ],
    "summary": "Better Stack scores 56.7 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth. Both do metrics and monitoring.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "better-stack": "One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.",
      "neat-pulse-mcp": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp",
    "json": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.min.md"
  },
  "markdown": "Better Stack scores 56.7 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth. Both do metrics and monitoring.\n\n- Better Stack: grade C, 56.7/100, rank #918 of 1557. Markdown https://www.anchorterminal.com/tools/better-stack.md · JSON https://www.anchorterminal.com/api/v1/tools/better-stack.json\n- Neat Pulse MCP: grade E, 45.8/100, rank #1268 of 1557. Markdown https://www.anchorterminal.com/tools/neat-pulse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Better Stack (C)\n\nGood for: An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.\n\nAhead on:\n- Reliability, 50 against 35\n- Agent ergonomics, 55 against 43\n- Payments \u0026 pricing, 60 against 0\n- Maintenance \u0026 community, 71 against 59\n- Transparency \u0026 trust, 69 against 56\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying\n\n### Neat Pulse MCP (E)\n\nGood for: IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.\n\nAhead on:\n- Security \u0026 auth, 79 against 60\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Better Stack +60\n\n- Better Stack (60): Read with the hosted rubric. No x402, MPP or L402 (0). Per-unit prices are public without login, by GB and region for telemetry, per responder, per status page and per phone number (20). The Free plan has 10 monitors, a status page and 3 GB of logs, the signup page says Sign up for free and names no card, and we did not run the signup flow (20). A person signs up in a browser and mints a token or completes OAuth there (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n- Neat Pulse MCP (0): No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0.\n\n### Security \u0026 auth: Neat Pulse MCP +19\n\n- Better Stack (60): OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.\n- Neat Pulse MCP (79): Scoped, revocable Pulse API tokens with a rotation endpoint, created only by organisation Owners and passed in an environment variable. The scopes are coarse, Read or everything (27). A Read-only token blocks every change per the setup guide, and the reference flags irreversible tools, but confirmation is left to the assistant (14). Room notes and device names are text people enter, and no prompt-injection guidance was found (5). Pulse audit logs record every MCP action under the token's name, and an MCP tool reads them (15). security.txt valid to August 2027, a vulnerability reporting policy, public advisories through November 2026, and a support article stating ISO 27001 certification. No bug bounty found (18). 27 + 14 + 5 + 15 + 18 = 79.\n\n### Reliability: Better Stack +15\n\n- Better Stack (50): Read with the hosted lines and scored on the remote MCP server at mcp.betterstack.com, which fronts the same service as the Incidents and Telemetry APIs. status.betterstack.com runs on Better Stack's own status page product with three components and a 90-day history (20). Between 5 August and 3 November 2026 it records delayed Telemetry data processing in the Europe region from 3 to 6 September in entries of 6 hours 19 minutes, 10 hours 10 minutes, 19 hours 13 minutes, 21 hours 45 minutes and 1 day, a 9-minute Telemetry degradation on 20 August, 39 minutes of wrong downtime notifications on 21 October and 8 minutes of dashboard unavailability on 2 November, every one labelled degraded, plus two migrations labelled maintenance (11 hours 13 minutes on 9 August and 17 hours). About four days of delayed log processing in one region is more than trivial and less than an outage of the API, so between minor-only and one major (15). No rate limit numbers were found in the API or MCP docs (0). The Usage API documents a 429 with the instruction to wait before retrying, with no Retry-After, no backoff guidance and no idempotency keys. `Upsert catalog records` is documented as not creating duplicates when repeated (5 of 15). No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature (0). The MCP server was announced on 15 September 2025 and carries no beta label (10). 20 + 15 + 0 + 5 + 0 + 10 = 50.\n- Neat Pulse MCP (35): Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.\n\n### Transparency \u0026 trust: Better Stack +13\n\n- Better Stack (69): Closed service under Terms of Use (14 February 2025) that name Better Stack, Inc., a Delaware corporation, under New York law. The plugins and Terraform providers are MIT (15 of 30). The privacy policy (25 November 2022) gives no retention periods and says data is processed primarily in the EU, while the DPA (25 February 2025) names the United States and other locations and promises return or destruction on termination. Telemetry retention is a plan term (3 days free, 30 days in bundles). OpenAI is a subprocessor and nothing says whether customer data is used for model training (14 of 30). No deprecation policy. The terms allow changes at Better Stack's discretion with continued use as acceptance, and the changelog carries no deprecation notices (3 of 20). Schedule A of the DPA lists nine subprocessors with locations, the security page says data is stored in EU regions by default with custom locations for enterprise, and no notice period for new subprocessors is given (16 of 20). 15 + 14 + 3 + 16 = 48.\n- Neat Pulse MCP (56): Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47.\n\n### Agent ergonomics: Better Stack +12\n\n- Better Stack (55): 148 tools are named on the docs page, more than 30 (5). X-MCP-Tools-Only and X-MCP-Tools-Except narrow the list to a subset or a read-only set, documented for that purpose, and the server has no default toolset (add 10, so 15). REST lists take page and per_page up to 250 with first, last, prev and next links, and filters by url, pronounceable_name and team_name. Plan query windows splits a long telemetry query into windows, and Execute query takes SQL with its own LIMIT. No field selection (16 of 20). 422 bodies name the field that failed and 401 gives a message, but no error code list exists and MCP errors are not documented (10 of 20). No idempotency keys. `Upsert catalog records` avoids duplicates, Reopen incident is limited to 24 hours, and the annotations on the tools couldn't be read (6 of 20). Get workspace style defaults are not described. Two Terraform providers and logging clients exist, but no official API SDK in any language, and the Claude plugin's 16 skills carry the query recipes (8 of 15). 15 + 16 + 10 + 6 + 8 = 55.\n- Neat Pulse MCP (43): 30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43.\n\n### Maintenance \u0026 community: Better Stack +12\n\n- Better Stack (71): Read as a closed service. The Claude plugin reached 1.3.12 on 2 November 2026 and the changelog's newest entry is 29 October 2026 (30). Changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026 (20). Public changelog, hello@betterstack.com with a stated reply within a few hours, and a community site. GitHub issues on the plugin repositories were not read (10 of 15). The MCP server is not in the official MCP registry under a verified namespace, the only entries matching the name being third-party scrapers, and there is no official API SDK. The Claude, Cursor, Codex and Antigravity plugins and two Terraform providers are current (5 of 15). The Claude plugin repository is MIT with 12 commit days since June 2026, and we didn't read its CI (6 of 10). 30 + 20 + 10 + 5 + 6 = 71.\n- Neat Pulse MCP (59): 1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59.\n\n## Score by category\n\n| Category | Weight | Better Stack | Neat Pulse MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 50 | 35 | Better Stack +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 46 | 49 | Neat Pulse MCP +3 |\n| Agent ergonomics | 13% | 55 | 43 | Better Stack +12 |\n| Security \u0026 auth | 14% | 60 | 79 | Neat Pulse MCP +19 |\n| Payments \u0026 pricing | 10% | 60 | 0 | Better Stack +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 71 | 59 | Better Stack +12 |\n| Transparency \u0026 trust | 7% | 69 | 56 | Better Stack +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.7 · C** | **45.8 · E** | |\n\n## Facts side by side\n\n| Fact | Better Stack | Neat Pulse MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Better Stack, Inc. | Neat |\n| Hosted endpoint | `https://mcp.betterstack.com` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Licence | Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT | none |\n| Tools exposed | 148 | 30 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | no |\n| Last release | 2026-11-02 | 2026-11-17 |\n| Terms last updated | no date given | 2025-03-26 |\n| Privacy policy last updated | no date given | 2026-07-13 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 6 stars | none |\n\n## How the scores have moved\n\n### Better Stack\n\n- +2.5 on 13 November 2026: checklist\n\n### Neat Pulse MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Better Stack.** One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.\n\n**Neat Pulse MCP.** Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.\n\n## Before you call either\n\n### Better Stack\n\n1. Connect with `claude mcp add betterstack --transport http https://mcp.betterstack.com` and sign in, or send a team-based API token as `Authorization: Bearer`; pick Read access unless the task writes\n2. Send `X-MCP-Tools-Only: monitors,monitor,incidents` or a similar list to keep the 148-tool list out of context, and `X-MCP-Tools-Except: remove_dashboard,remove_chart` to block deletes\n3. Call `Get query instructions` or `Plan query windows` before `Execute query`, since long time ranges are split into windows and nothing documents a result size limit\n4. No rate limit is published. Back off on a 429 and don't retry writes blindly, because there are no idempotency keys; `Upsert catalog records` is the one write documented as safe to repeat\n5. Reopening an incident only works within 24 hours of its resolution, and a comment can only be edited or removed by its author or an API token\n\n### Neat Pulse MCP\n\n1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices\n2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room\n3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy\n4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`\n5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`\n\n## Questions\n\n### Which is better for AI agents, Better Stack or Neat Pulse MCP?\n\nBetter Stack scores 56.7 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 5 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.\n\n### Do Better Stack and Neat Pulse MCP need an API key?\n\nBetter Stack takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.\n\n### Can an agent call Better Stack and Neat Pulse MCP without installing anything?\n\nBetter Stack has a hosted endpoint at https://mcp.betterstack.com. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"better-stack\", \"b\": \"neat-pulse-mcp\"}`. From a terminal: `anchor compare better-stack neat-pulse-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/better-stack.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n\n## Other comparisons with Better Stack or Neat Pulse MCP\n\n- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)\n- [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md)\n- [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md)\n- [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)\n- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)\n- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md)\n- [Datadog MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md)\n- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)\n- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)\n- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)\n- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)\n- [Better Stack vs Causely MCP server](https://www.anchorterminal.com/compare/better-stack-vs-causely.md)\n- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)\n- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md)\n- [Better Stack vs Honeycomb MCP](https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md)\n- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)\n- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.md)\n- [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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": "Better Stack vs Neat Pulse MCP",
        "url": ""
      }
    ],
    "description": "Better Stack scores 56.7 (C) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Better Stack C 56.7",
      "Neat Pulse MCP E 45.8",
      "scores"
    ],
    "h1": "Better Stack vs Neat Pulse MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/better-stack-vs-neat-pulse-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Better Stack vs Neat Pulse MCP for AI agents (2026) | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp"
  },
  "tokens": {
    "markdown": 5000,
    "slim": 1030
  },
  "version": 1
}
