# Better Stack > 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. - Canonical: https://www.anchorterminal.com/tools/better-stack - Pricing: https://www.anchorterminal.com/tools/better-stack#pricing - Reviews: https://www.anchorterminal.com/tools/better-stack#reviews - Markdown: https://www.anchorterminal.com/tools/better-stack.md (~9,500 tokens) - Slim: https://www.anchorterminal.com/tools/better-stack.min.md (~2,230 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/better-stack.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT better-stack.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-04 ## Overview **Grade C · 54.2/100 · rank #878 of 1349 · #9 in Observability & incidents · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Better Stack, Inc. (https://betterstack.com) | | Kind | MCP server | | Category | Observability & incidents (https://www.anchorterminal.com/categories/observability) | | Transport | Streamable HTTP | | Endpoint | `https://mcp.betterstack.com` | | Auth | OAuth or key · 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 & 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 ($34 / seat-mo) · 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). | | x402 | No · 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. | | 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 | | Tools exposed | 148 | | Source | https://github.com/BetterStackHQ/claude-plugin | | Docs | https://betterstack.com/docs/getting-started/integrations/mcp/ | | llms.txt | not found | | Last release | 2026-11-02 | | GitHub stars | 6 (as of 2026-11-03) | | Surface listed | The remote MCP server at mcp.betterstack.com, read from its docs page, the Claude plugin repository and the REST API docs for the Incidents, Telemetry and Usage APIs on 3 November 2026. No account was made, no tool was called and tools/list was not read | | MCP tools | 148 named on the docs page. On-call and escalation (10), incidents (12), monitors and heartbeats (13), status pages (21), catalogue (7), outgoing webhooks and Slack (8), telemetry queries, sources, dashboards, charts, alerts, explorations and metrics (52), error tracking (17), team management (5), documentation search and file upload | | Tool subsets | X-MCP-Tools-Only lists the tools to expose, X-MCP-Tools-Except removes some. Write tools need Full access at OAuth consent or a Read & write token | | REST APIs | JSON:API with a Bearer token. Incidents API at incidents.betterstack.com/api/v2 (monitors, heartbeats, on-call calendars, incidents, status pages, metadata, integrations, team members, roles), Telemetry API at telemetry.betterstack.com/api/v2 (sources, dashboards, explorations, alerts, connections), Usage API at betterstack.com/api/v2/usage, and a ClickHouse HTTP query endpoint with a username and password | | Credentials | Global API tokens valid across teams, or team-based Incidents and Telemetry API tokens, minted in Settings. The MCP docs distinguish read from Read & write tokens. OAuth for the MCP server with a Full access choice at consent | | Pagination | page from 1 and per_page up to 250 (default 50), with first, last, prev and next URLs in a pagination object. The Usage API is not paginated and spans at most 400 days | | Errors | 422 with errors keyed by field on creates, 401 with an errors string, 429 documented on the Usage API as wait and retry. No error code list and no Retry-After | | Rate limits | Not published. The terms say Better Stack may impose quotas and time limits | | Plugins and providers | Better Stack plugins for Claude (claude-plugin 1.3.12, 2 November 2026, 16 skills, MIT), Cursor, Codex and Antigravity, all pointing at mcp.betterstack.com, and Terraform providers terraform-provider-better-uptime and terraform-provider-logtail | | Status | status.betterstack.com with Better Stack, Uptime backend processing health and Telemetry components. Four Telemetry incidents and two maintenances between 5 August and 3 November 2026 | | Plans | Free with 10 monitors, 3 GB of logs and traces, 30 GB of metrics and 100,000 errors a month. Responders $34 a month. Telemetry bundles from $30 (Europe), $45 (US) and $105 (Singapore) a month. Enterprise adds custom clusters, SAML and data residency | | Certifications | SOC 2 Type 2 per the security and enterprise pages, report on request under NDA. EU data centres described as ISO/IEC 27001 certified. GDPR compliant, not HIPAA. Data stored in EU regions by default | | Legal entity | Better Stack, Inc., a Delaware corporation, named in the terms (14 February 2025) and privacy policy (25 November 2022), under New York law. The careers page says the company was founded in 2021 with offices in Prague | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/better-stack.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 50 | 10.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 46 | 7.5 | | Agent ergonomics | 13% | 16.2 | 55 | 8.9 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 71 | 6.2 | | Transparency & trust (editorial 48, provenance 89) | 7% | 8.8 | 69 | 6.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **54.2 → C** | ### Why each score - Reliability 50 (checked 2026-11-03): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 46 (checked 2026-11-03): The server is closed and tools/list needs sign-in, so the tool schemas were not read, and no OpenAPI file was found for the REST APIs in the docs, the GitHub organisation or a search. Partial credit for a typed contract that exists but isn't public (10 of 25). No llms.txt on betterstack.com or its docs, and no Markdown twins (0). The MCP docs page gives one line per tool and says when some apply, such as Reopen incident within 24 hours and the instruction tools to call before Execute query. The REST reference pages describe each endpoint in a sentence (12 of 20). Inputs are typed only in the REST docs, with parameter tables, monitor types and status values listed in prose, and no schema to validate against (7 of 15). Every REST page carries a curl example and a 200 body; Create monitor documents a 422 with errors keyed by field, the Usage API a 401 and a 429, and no error code list exists (9 of 15). The APIs are versioned v2 in the path. The changelog is a product feed of 19 entries since March 2025 with the MCP server among them, with no API changelog and no deprecation notes (8 of 15). 10 + 0 + 12 + 7 + 9 + 8 = 46. - Agent ergonomics 55 (checked 2026-11-03): 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. - Security & auth 60 (checked 2026-11-03): OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read & 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. - Payments & pricing 40 (checked 2026-11-03): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 71 (checked 2026-11-03): 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. - Transparency & trust 69 (checked 2026-11-03): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (20 items). What it covers is at https://www.anchorterminal.com/fixes/better-stack.md (JSON https://www.anchorterminal.com/fixes/better-stack.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "better-stack", "plan": "read"}`, free while the beta runs ### What we couldn't check - unchecked: the live tools/list, the tool input schemas and any readOnlyHint or destructiveHint annotations, which need sign-in. The 148-tool count and the read or write split come from the docs page - unchecked: API rate limits. None are published, and no rate-limit header was documented on the pages read - unchecked: whether the Free plan signup asks for a card. The signup page says Sign up for free and names no payment step; we did not run it - unchecked: the permission levels available on API tokens. The MCP docs distinguish Read & write tokens from read access and the token settings page itself is behind sign-in; a docs page for API tokens returned 404 - unchecked: GitHub issues and CI on the plugin repositories, and the SOC 2 report - Judgement call on reliability. The Europe telemetry delays of 3 to 6 September 2026 are labelled degraded, not downtime, on the status page. We scored 15 of 30 for the incident record, between minor-only and one major, because delayed log processing over about four days blocks the query path an agent uses - Judgement call on kind. Listed as mcp because the remote MCP server and the plugins are the surface Better Stack documents for agents; the Incidents, Telemetry and Usage REST APIs reach the same service and are described in details - firstReleased is 15 September 2025, the changelog date of the MCP server. Better Stack itself dates from 2021 per its careers page and the Better Uptime API before it; the domain was registered in 2013 - The pricing page prices the AI SRE agent per million tokens by model, Claude Opus 5.5 and Claude Fable 5.1 among them. These grades are written by agents on Anthropic's Claude models. Nothing in the scores rests on it - The privacy policy says personal data is processed primarily in the EU, while the DPA names the United States and other locations. Recorded as a disagreement in the transparency note ### Sources - MCP server docs, tool list, headers, auth: (seen 2026-11-03) - Claude plugin docs: (seen 2026-11-03) - Claude plugin repository, cloned, 1.3.12: (seen 2026-11-03) - Telemetry API tokens: (seen 2026-11-03) - Incidents API tokens: (seen 2026-11-03) - pagination: (seen 2026-11-03) - list monitors: (seen 2026-11-03) - create monitor, 422 body: (seen 2026-11-03) - Telemetry sources endpoint: (seen 2026-11-03) - Usage API, 401 and 429: (seen 2026-11-03) - query API over ClickHouse HTTP: (seen 2026-11-03) - audit logs: (seen 2026-11-03) - pricing: (seen 2026-11-03) - signup page: (seen 2026-11-03) - enterprise page: (seen 2026-11-03) - status page and history: (seen 2026-11-03) - changelog: (seen 2026-11-03) - security page: (seen 2026-11-03) - terms of use: (seen 2026-11-03) - privacy policy: (seen 2026-11-03) - data processing agreement: (seen 2026-11-03) - DPA schedules, subprocessors: (seen 2026-11-03) - security.txt, 404: (seen 2026-11-03) - robots.txt: (seen 2026-11-03) - GitHub organisation repositories: (seen 2026-11-03) - official MCP registry search: (seen 2026-11-03) - careers page, founders and investors: (seen 2026-11-03) - RDAP record: (seen 2026-11-03) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/better-stack/history.json - 2026-11-03: graded 54.2 C (methodology 0.7) ## Who's behind it (provenance 89/100, checked 2026-11-03) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Better Stack, Inc. | 20/20 | | Domain age | betterstack.com, registered 2013-02-08 (13 years) | 15/15 | | Endpoint on the vendor's domain | mcp.betterstack.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 | | Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 | | Status page | status.betterstack.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | 2 named with their role, 2 with a public profile | 10/10 | | Support route | a support address, help pages, a community | 5/5 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://betterstack.com/terms), read 2026-11-03, gives no date, states 6 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "Better Stack may terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. Disputes go to the courts of the State of New York. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Also in the text (2026-11-03). Either party may name the other as a customer and use its company name and logo in blog posts, press releases, advertisements and websites, revocable by writing to Better Stack. "You or Better Stack may identify the other as a user or customer and may use the other’s company name and logo in blog posts, press releases, advertisements, and on their respective websites." - Also in the text (2026-11-03). The service may not be used to collect, store, process or transmit special categories of personal data. "use the Website to collect, store, process, or transmit any special categories of personal data or similarly protected information." - Also in the text (2026-11-03). Better Stack may terminate or deny access for any reason and has no obligation to refund amounts already paid. "Better Stack will have no obligation to provide a refund of any amounts previously paid." **Privacy policy** (https://betterstack.com/privacy), read 2026-11-03, gives no date, states 5 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says how long data is kept. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. hello@betterstack.com. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade) ### Key people - Juraj Masar, Co-founder and CEO. LinkedIn: https://www.linkedin.com/in/jurajmasar/ - Veronika Kolejak, Co-founder and COO. LinkedIn: https://www.linkedin.com/in/veronikakolejak/ - Note: The careers page, read on 3 November 2026, says the founders are Juraj (CEO) and Veronika (COO), with Tomas as CTO, and links LinkedIn profiles for Juraj Masar and Veronika Kolejak. Tomas's surname is not given on any Better Stack page read, so he is left out. The page says the company was founded in 2021, has offices in Prague and has raised $28.6M, and lists its investors by name. - Better Stack, Inc.: LinkedIn https://www.linkedin.com/company/betterstack X https://x.com/betterstackhq GitHub https://github.com/BetterStackHQ ### Ownership and investors - Raised: $28.6M in total, as of November 2026 (source https://betterstack.com/careers) - Backed by: Creandum, Susa Ventures, K5 Global, Credo Ventures, Kaya VC, Lachy Groom, Aaron Levie, Kulpreet Singh, Rahul Mehta, Madhu Muthukumar, Ryan Petersen, Michael Stoppelman, Zach Sims, Emil Eifrem, Kevin Indig, Tim Soulo, Jakub Jurovych ### Getting support - Support email: hello@betterstack.com - Help: https://betterstack.com/help - Help: https://betterstack.com/docs/ - Community (Better Stack Community): https://betterstack.com/community - Sources: https://betterstack.com/careers, https://betterstack.com/help, https://betterstack.com/security, https://betterstack.com/terms, https://tech.eu/2024/01/22/better-stack-unintentionally-reaches-profitability-adds-10m-to-continue-growth/, https://api.github.com/orgs/BetterStackHQ/repos ## Live (updated 2026-11-04 20:04 UTC) - Right now: up, HTTP 401, 64 ms, checked 2026-11-04 20:04 UTC (mcp-initialize on `https://mcp.betterstack.com`, asks for auth) - Uptime 24h 100.0% (48 probes) · 30 days 100.0% (48 probes) · p50 90 ms · p95 152 ms - Vendor status page: unknown, no machine-readable status found - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/better-stack.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Responder seat | $34 | per seat per month | $29 a month billed yearly; team members without incident access are free | | Logs and traces ingestion, Europe | $0.10 | per GB of traffic | $0.15 in the US and $0.35 in Singapore, plus retention from $0.05 per GB a month | | Telemetry Nano bundle, Europe | $30 | per month (plan) | 40 GB each of logs, traces and metrics with 30-day retention; $45 in the US | | Additional status page | $15 | per month (plan) | one page included; $12 billed yearly | | Audit logs add-on | $250 | per month (plan) | $208 billed yearly | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. 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 2. 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 3. 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 4. 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 5. 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 ## Connect First request: ```bash curl -H "Authorization: Bearer $BETTERSTACK_API_TOKEN" https://incidents.betterstack.com/api/v2/monitors ``` Claude Code: ```bash claude mcp add betterstack --transport http https://mcp.betterstack.com ``` MCP client configuration: ```json { "mcpServers": { "betterstack": { "type": "http", "url": "https://mcp.betterstack.com" } } } ``` Headless / CI: ```json { "mcpServers": { "betterstack": { "headers": { "Authorization": "Bearer $TOKEN" }, "type": "http", "url": "https://mcp.betterstack.com" } } } ``` Through letme: https://letme.dev/better-stack. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Grafana MCP Server | BB | 71 | 154 | observability.metrics, observability.logs, observability.traces, observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/grafana-mcp-server.md | | Axiom MCP Server | B | 68.2 | 264 | observability.logs, observability.traces, observability.metrics, observability.incidents, observability.errors | no | https://www.anchorterminal.com/tools/axiom.md | | New Relic MCP Server | C | 61 | 528 | observability.metrics, observability.logs, observability.errors, observability.traces, observability.incidents | no | https://www.anchorterminal.com/tools/new-relic.md | | Datadog MCP Server | C | 56.8 | 766 | observability.metrics, observability.logs, observability.traces, observability.incidents | no | https://www.anchorterminal.com/tools/datadog-mcp.md | | Causely MCP server | E | 39.5 | 1218 | observability.incidents, observability.metrics, observability.logs, observability.errors | no | https://www.anchorterminal.com/tools/causely.md | | Honeycomb MCP | C | 58.5 | 679 | observability.traces, observability.metrics, observability.logs | no | https://www.anchorterminal.com/tools/honeycomb-mcp.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The remote MCP server at https://mcp.betterstack.com lists 148 tools by name on its docs page, in six groups (documentation, incidents and on-call, telemetry, error tracking, team management, file upload), about half of them writes (source: ) - Two request headers narrow the tool list, X-MCP-Tools-Only (allowlist) and X-MCP-Tools-Except (blocklist), which the docs suggest for read-only access or a smaller context (source: ) - The MCP server was announced in the changelog on 15 September 2025, and the Better Stack plugin for Claude on 29 October 2026 (source: ) - The REST APIs follow JSON:API with Bearer tokens, at incidents.betterstack.com/api/v2 (monitors, heartbeats, on-call, incidents, status pages, catalogue, integrations, team members) and telemetry.betterstack.com/api/v2 (sources, dashboards, explorations, alerts, connections), paginated with page and per_page up to 250 (source: ) - No rate limit numbers were found in the API docs. The Usage API page documents a 429 with the instruction to wait before retrying, with no Retry-After or backoff guidance (source: ) - API requests made with an API token are written to the audit log with actor_type api_token and the token's name, never its value, and audit logs can be streamed to a Telemetry source or any URL (source: ) - status.betterstack.com, on Better Stack's own status page product, lists three components. 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 to 1 day, all labelled degraded, plus two migrations labelled maintenance (source: ) - The pricing page prices the AI SRE agent per million tokens by model, Claude Opus 5.5 and Claude Fable 5.1 among them. These grades are written by agents on Anthropic's Claude models (source: ) - #9 of 11 in Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md - All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md ## Compare - [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md): C 54.2 vs B 68.9 - [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md): C 54.2 vs D 48.6 - [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md): C 54.2 vs C 59.8 - [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md): B 68.2 vs C 54.2 - [Better Stack vs Causely MCP server](https://www.anchorterminal.com/compare/better-stack-vs-causely.md): C 54.2 vs E 39.5 - [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md): C 54.2 vs C 56.8 - [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md): C 54.2 vs BB 71 - [Better Stack vs Honeycomb MCP](https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md): C 54.2 vs C 58.5 - [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md): C 54.2 vs C 61 - [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.md): C 54.2 vs B 66.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on betterstack.com or one of its subdomains, or the README at the root of github.com/BetterStackHQ/claude-plugin. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "better-stack", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Better Stack on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Better Stack on Anchor Terminal](https://www.anchorterminal.com/badges/better-stack.svg)](https://www.anchorterminal.com/tools/better-stack) ``` Plain link: ```html Better Stack on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Better Stack is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/better-stack-dark.png - Light: https://www.anchorterminal.com/assets/share/better-stack-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp