{ "data": { "a": { "slug": "better-stack", "name": "Better Stack", "vendor": "Better Stack, Inc.", "vendorUrl": "https://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": 54.2, "grade": "C", "agentReady": false, "rank": 917, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 71, "payments": 40, "reliability": 50, "schema": 46, "security": 60, "transparency": 69 }, "pending": [ "performance", "tasks" ], "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": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.2 } ], "editorialScores": { "ergonomics": 55, "maintenance": 71, "payments": 40, "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", "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-08T01:01:21.536641631Z", "lastOk": true, "lastStatus": 401, "lastMs": 99, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 124, "samples24h": 244, "samples30d": 767, "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": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.betterstack.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:30:45.523454958Z" }, "githubStars": 6, "securityTxt": { "url": "https://betterstack.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:26.002943776Z" }, "pages": [ { "url": "https://betterstack.com/tag/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:00:08.934294993Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1f20ca3dcacc" }, { "url": "https://betterstack.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:00:04.815977959Z", "changedAt": "2026-11-06T13:22:49.376519607Z", "fingerprint": "4423e6668f57" }, { "url": "https://betterstack.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:00:06.843019606Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0f5678b89d3a" }, { "url": "https://betterstack.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:00:10.999509656Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f78bcc7d4cc3" } ], "mcpTools": { "url": "https://mcp.betterstack.com", "checkedAt": "2026-11-07T01:42:51.239864Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-05T01:29:02.104349366Z" }, "updatedAt": "2026-11-08T01:01:21.536641631Z" } }, "answer": "Cronitor MCP server scores 59.1 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 3 of 7 scored categories. Better Stack leads on maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "cronitor-mcp", "name": "Cronitor MCP server", "vendor": "Cronitor", "vendorUrl": "https://cronitor.io", "kind": "mcp", "category": "observability", "summary": "Cronitor's hosted MCP server lets an agent create and manage cron job, heartbeat and uptime monitors, issues, status pages, alert integrations and metrics in a Cronitor account, over OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/cronitor-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json", "dns": "cronitor-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://cronitor.io/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth through protected-resource metadata, with sign-in and consent in a browser; the token carries the user's role, capped at the SDK Integration key's permissions, with no scope selection. An API key in a header works for headless clients, with the key's granular read or write scopes.", "pricing": "freemium", "pricingNotes": "Free forever for 5 monitors. Business is $2 a monitor and $5 a user a month after a 14-day trial (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 71, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://cronitor.io/docs/mcp-server", "llmsTxt": "https://cronitor.io/llms.txt", "registryName": "io.cronitor/cronitor", "capabilities": [ "observability.incidents", "observability.metrics", "events.schedule", "agent.tools" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "api-key", "freemium", "free-tier", "status-page", "llms-txt", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 59.1, "grade": "C", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.", "bestFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "strengths": [ "Strict input schemas (additionalProperties false) with enums and required combinations", "Summary modes with paging keep list output small", "JSON-RPC error codes with retry_after_seconds and required_scope", "Clear guidance on secrets in event messages and output", "Free plan for 5 monitors" ], "weaknesses": [ "71 tools, a heavy context load", "No public changelog", "Terms and privacy closed to crawlers, so unread", "No audit log of agent calls found" ], "agentNotes": [ "Start with list_monitors and list_issues in summary mode", "Ask the user before expanding event messages, command output or request bodies", "On a rate-limit error, wait retry_after_seconds", "Over the plan's monitor limit, new monitors are saved but disabled" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.1 } ], "editorialScores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 25 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add cronitor --transport http https://cronitor.io/mcp", "config": { "mcpServers": { "cronitor": { "url": "https://cronitor.io/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/cronitor-mcp" }, "area": "developer", "provenance": { "legalEntity": "Cronitor", "domain": "cronitor.io", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.cronitor.io", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "robots.txt disallows the terms and privacy pages, so the legal entity wasn't read.", "security.txt answered 404." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.json", "live": { "slug": "cronitor-mcp", "probe": { "target": "https://cronitor.io/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T01:01:26.14186466Z", "lastOk": true, "lastStatus": 401, "lastMs": 584, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 627, "p95ms24h": 717, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.cronitor.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:31:11.053343459Z" }, "updatedAt": "2026-11-08T01:01:26.14186466Z" } }, "edges": [ { "by": 34, "category": "schema", "leads": "cronitor-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80." }, "scores": { "a": 46, "b": 80 } }, { "by": 32, "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": "robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25." }, "scores": { "a": 69, "b": 37 } }, { "by": 18, "category": "ergonomics", "leads": "cronitor-mcp", "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": "71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73." }, "scores": { "a": 55, "b": 73 } }, { "by": 16, "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": "Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API." }, "scores": { "a": 71, "b": 55 } }, { "by": 5, "category": "reliability", "leads": "cronitor-mcp", "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": "Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55." }, "scores": { "a": 50, "b": 55 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Better Stack, Inc.", "b": "Cronitor", "name": "Vendor" }, { "a": "https://mcp.betterstack.com", "b": "https://cronitor.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "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": "71", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.cronitor/cronitor", "name": "MCP registry" }, { "a": "2026-11-02", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "6 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Cronitor MCP server scores 59.1 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 3 of 7 scored categories. Better Stack leads on maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Better Stack or Cronitor MCP server?" }, { "answer": "Better Stack takes an API key or an OAuth sign-in. Cronitor MCP server uses an OAuth sign-in.", "question": "Do Better Stack and Cronitor MCP server need an API key?" }, { "answer": "Yes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and Cronitor MCP server at https://cronitor.io/mcp.", "question": "Can an agent call Better Stack and Cronitor MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Maintenance \u0026 community, 71 against 55", "Transparency \u0026 trust, 69 against 37" ], "also": null, "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": [ "Reliability, 55 against 50", "Schema \u0026 documentation, 80 against 46", "Agent ergonomics, 73 against 55" ], "also": null, "goodFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "slug": "cronitor-mcp", "watchFor": "71 tools, a heavy context load" } ], "history": null, "job": { "capability": "observability.incidents", "name": "Incidents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.json", "title": "Axiom MCP Server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/axiom-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/causely-vs-cronitor-mcp.json", "title": "Causely MCP server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json", "title": "Cronitor MCP server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.json", "title": "Cronitor MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json", "title": "Cronitor MCP server vs incident.io API", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json", "title": "Cronitor MCP server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.json", "title": "Cronitor MCP server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json", "title": "Cronitor MCP server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-better-stack.json", "title": "Axiom MCP Server vs Better Stack", "url": "https://www.anchorterminal.com/compare/axiom-vs-better-stack" }, { "json": "https://www.anchorterminal.com/compare/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/cronitor-mcp-vs-honeycomb-mcp.json", "title": "Cronitor MCP server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-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": 5, "cronitor-mcp": 55, "edge": "cronitor-mcp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "better-stack": 46, "by": 34, "cronitor-mcp": 80, "edge": "cronitor-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "better-stack": 55, "by": 18, "cronitor-mcp": 73, "edge": "cronitor-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "better-stack": 60, "by": 2, "cronitor-mcp": 58, "edge": "better-stack", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "better-stack": 40, "by": 0, "cronitor-mcp": 40, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "better-stack": 71, "by": 16, "cronitor-mcp": 55, "edge": "better-stack", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "better-stack": 69, "by": 32, "cronitor-mcp": 37, "edge": "better-stack", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Cronitor MCP server scores 59.1 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 3 of 7 scored categories. Better Stack leads on maintenance \u0026 community and transparency \u0026 trust. Both do incidents.", "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.", "cronitor-mcp": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp", "json": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.min.md" }, "markdown": "Cronitor MCP server scores 59.1 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 3 of 7 scored categories. Better Stack leads on maintenance \u0026 community and transparency \u0026 trust. Both do incidents.\n\n- Better Stack: grade C, 54.2/100, rank #917 of 1510. Markdown https://www.anchorterminal.com/tools/better-stack.md · JSON https://www.anchorterminal.com/api/v1/tools/better-stack.json\n- Cronitor MCP server: grade C, 59.1/100, rank #718 of 1510. Markdown https://www.anchorterminal.com/tools/cronitor-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 59 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- Maintenance \u0026 community, 71 against 55\n- Transparency \u0026 trust, 69 against 37\n\nWatch for: No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying\n\n### Cronitor MCP server (C)\n\nGood for: Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.\n\nAhead on:\n- Reliability, 55 against 50\n- Schema \u0026 documentation, 80 against 46\n- Agent ergonomics, 73 against 55\n\nWatch for: 71 tools, a heavy context load\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Cronitor MCP server +34\n\n- Better Stack (46): 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.\n- Cronitor MCP server (80): Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.\n\n### Transparency \u0026 trust: Better Stack +32\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- Cronitor MCP server (37): robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.\n\n### Agent ergonomics: Cronitor MCP server +18\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- Cronitor MCP server (73): 71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73.\n\n### Maintenance \u0026 community: Better Stack +16\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- Cronitor MCP server (55): Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.\n\n### Reliability: Cronitor MCP server +5\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- Cronitor MCP server (55): Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.\n\n## Score by category\n\n| Category | Weight | Better Stack | Cronitor MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 55 | Cronitor MCP server +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 46 | 80 | Cronitor MCP server +34 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 73 | Cronitor MCP server +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 58 | Better Stack +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 55 | Better Stack +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 37 | Better Stack +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.2 · C** | **59.1 · C** | |\n\n## Facts side by side\n\n| Fact | Better Stack | Cronitor MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Better Stack, Inc. | Cronitor |\n| Hosted endpoint | `https://mcp.betterstack.com` | `https://cronitor.io/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Freemium |\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 | 71 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.cronitor/cronitor` |\n| Last release | 2026-11-02 | none |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 6 stars | none |\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**Cronitor MCP server.** Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.\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### Cronitor MCP server\n\n1. Start with list_monitors and list_issues in summary mode\n2. Ask the user before expanding event messages, command output or request bodies\n3. On a rate-limit error, wait retry_after_seconds\n4. Over the plan's monitor limit, new monitors are saved but disabled\n\n## Questions\n\n### Which is better for AI agents, Better Stack or Cronitor MCP server?\n\nCronitor MCP server scores 59.1 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 3 of 7 scored categories. Better Stack leads on maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Better Stack and Cronitor MCP server need an API key?\n\nBetter Stack takes an API key or an OAuth sign-in. Cronitor MCP server uses an OAuth sign-in.\n\n### Can an agent call Better Stack and Cronitor MCP server without installing anything?\n\nYes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and Cronitor MCP server at https://cronitor.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"better-stack\", \"b\": \"cronitor-mcp\"}`. From a terminal: `anchor compare better-stack cronitor-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/better-stack.json and https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json\n\n## Other comparisons with Better Stack or Cronitor MCP server\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-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- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md)\n- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)\n- [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md)\n- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.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- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-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-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Better Stack vs Cronitor MCP server", "url": "" } ], "description": "Cronitor scores 59.1 (C) to Better Stack's 54.2 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Better Stack C 54.2", "Cronitor MCP server C 59.1", "scores" ], "h1": "Better Stack vs Cronitor MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/better-stack-vs-cronitor-mcp", "published": "2026-10-01", "section": "tools", "title": "Better Stack vs Cronitor for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp" }, "tokens": { "markdown": 4450, "slim": 2780 }, "version": 1 }