{ "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": 811, "ranked": true, "rankOf": 1349, "categoryRank": 7, "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-04T20:46:35.119337454Z", "lastOk": true, "lastStatus": 401, "lastMs": 90, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 195, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://status.betterstack.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:31:22.214208643Z" }, "githubStars": 6, "securityTxt": { "url": "https://betterstack.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:41.12669976Z" }, "updatedAt": "2026-11-04T20:46:35.119337454Z" } }, "answer": "Honeycomb MCP scores 60.7 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 5 of 7 scored categories. Better Stack leads on payments \u0026 pricing.", "b": { "slug": "honeycomb-mcp", "name": "Honeycomb MCP", "vendor": "Honeycomb", "vendorUrl": "https://www.honeycomb.io", "kind": "mcp", "category": "observability", "summary": "Honeycomb's hosted MCP server lets AI agents query a team's traces, metrics and events, run BubbleUp analysis, and create or update Boards, Triggers and SLOs. It uses OAuth or a Management API key and has US and EU endpoints.", "url": "https://www.anchorterminal.com/tools/honeycomb-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json", "dns": "honeycomb-mcp.grade.anchorterminal.com", "repo": "https://github.com/honeycombio/agent-skill", "license": "Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.honeycomb.io/mcp", "packages": [], "auth": "mixed", "authNotes": "OAuth is the documented default. The server at https://mcp.honeycomb.io/mcp points clients to its protected-resource metadata, and ui.honeycomb.io is the authorisation server, with PKCE S256 and dynamic client registration. On the consent screen the owner chooses read all, read and write all, or read or write per resource (Boards, Triggers, SLOs, recipients, Service Maps, Anomaly Signals, Canvas investigations), and every connection also gets `environments:read` and `queries:read`. Connections authorised earlier keep `mcp:read` or `mcp:write`. Unattended agents can send a Management API key as `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e`, with Read or Write under Model Context Protocol and access under Environments. Only a Team Owner can create that key, and its scopes can't be changed later. Access is self-serve, but a Team Owner must first enable Honeycomb Intelligence for the team.", "pricing": "byo-plan", "pricingNotes": "No separate charge. Honeycomb MCP is in the feature list of every plan, the Free plan included (20 million events and 100 million metric data points a month). Pro starts at $150 a month for 50 million events and Enterprise is quoted. The signup page asks for an email address or a Google account, and the signup guide names no payment step, so an agent's owner can start without a contract (https://www.honeycomb.io/pricing, checked 2026-10-09).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, the pricing page or the terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 36, "popularity": { "githubStars": 27, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.honeycomb.io/integrations/mcp/", "llmsTxt": "https://docs.honeycomb.io/llms.txt", "registryName": "io.honeycomb/mcp", "capabilities": [ "observability.traces", "observability.metrics", "observability.logs" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "toolsets", "free-tier", "eu-region", "llms-txt", "mcp-registry", "status-page", "soc2" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 60.7, "grade": "C", "agentReady": false, "rank": 579, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 81, "payments": 30, "reliability": 70, "schema": 57, "security": 68, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "OAuth now lets an owner grant read or write per resource, so an agent can be held to queries and reads across the 36 tools, and per-tool rate limits are published. Tool input schemas are visible only after sign-in, no injection guidance was found for telemetry content, and the product changelogs disallow unnamed crawlers.", "bestFor": "Agents that investigate latency and error spikes in a team already sending traces and events to Honeycomb, and that record findings as Boards, Triggers or SLOs.", "strengths": [ "OAuth with PKCE, dynamic client registration and per-resource scopes, such as `boards:read` or `triggers:write`, chosen on the consent screen", "Per-tool rate limits are published, from 10 calls a minute for `get_service_map` to 300 for semantic-convention lookups", "Listed in the official MCP registry as `io.honeycomb/mcp` 1.0.0, under the vendor's own domain namespace", "Included in the Free plan (20 million events a month), with separate US and EU endpoints", "The Activity Log records OAuth sessions with granted scopes and each query run with its source, MCP included" ], "weaknesses": [ "Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters", "No guidance on prompt injection was found, although trace and log content returned to the agent is untrusted text", "The status page has no MCP component. US1 queries over older data failed for 67 minutes on 10 August 2026", "No SLA was found, and the AI terms allow Honeycomb to change or end any part of Honeycomb Intelligence at any time", "A Team Owner must enable Honeycomb Intelligence first, and API key scopes can't be changed after creation" ], "agentNotes": [ "Use https://mcp.honeycomb.io/mcp for US teams and https://mcp.eu1.honeycomb.io/mcp for EU teams. A team's data lives in one region only", "If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings", "Ask the owner to choose Customize on the consent screen and grant only the resources the task needs. The agent sees only the tools its scopes allow", "Send `X-MCP-Toolset: query` or `canvas` to load a subset of the 36 tools. Call `get_workspace_context` first, then `find_columns`, before `run_query`", "For unattended runs send `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e` from a Management key with only Model Context Protocol and Environments scopes" ], "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": 60.7 } ], "editorialScores": { "ergonomics": 53, "maintenance": 81, "payments": 30, "reliability": 70, "schema": 57, "security": 68, "transparency": 64 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcp", "config": { "mcpServers": { "honeycomb": { "url": "https://mcp.honeycomb.io/mcp" } } }, "headless": { "mcpServers": { "honeycomb": { "args": [ "-y", "mcp-remote", "https://mcp.honeycomb.io/mcp", "--header", "Authorization: Bearer $HONEYCOMB_API_KEY" ], "command": "npx", "env": { "HONEYCOMB_API_KEY": "\u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e" } } } } }, "letme": { "capability": "https://letme.dev/observability.traces", "tool": "https://letme.dev/honeycomb-mcp" }, "area": "developer", "unitPrices": [ { "item": "Pro plan, 50 million events", "unit": "month", "usd": 150, "note": "Starting price. MCP is also in the Free plan at no charge" } ], "provenance": { "legalEntity": "Hound Technology, Inc. d/b/a Honeycomb", "domain": "honeycomb.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.honeycomb.io/terms", "privacy": "https://www.honeycomb.io/privacy", "statusPage": "https://status.honeycomb.io", "changelog": "https://changelog.honeycomb.io/", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service (effective 22 May 2025) name Hound Technology, Inc. d/b/a Honeycomb, are governed by California law, and incorporate the Honeycomb Intelligence Supplemental Terms at honeycomb.io/ai-terms and the Data Processing Addendum at honeycomb.io/dpa.", "The Privacy Notice (last updated 24 July 2025) covers the website and the services, and says it does not apply to content customers submit under a customer account. The DPA (last updated 22 May 2025) governs that content.", "The MCP server answers at mcp.honeycomb.io and mcp.eu1.honeycomb.io, and the OAuth server at ui.honeycomb.io, all honeycomb.io subdomains.", "www.honeycomb.io/.well-known/security.txt and /security.txt return 404. Reports go to security@honeycomb.io under a bug bounty programme whose stated scope is ui.honeycomb.io and api.honeycomb.io.", "changelog.honeycomb.io and api-changelog.honeycomb.io disallow every path to unnamed crawlers in robots.txt, so neither was read.", "The .io registry has no RDAP service that answered, so the domain's registration date is not recorded." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.json", "live": { "slug": "honeycomb-mcp", "probe": { "target": "https://mcp.honeycomb.io/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T20:46:51.103674148Z", "lastOk": true, "lastStatus": 401, "lastMs": 519, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 388, "p95ms24h": 502, "samples24h": 246, "samples30d": 6644, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 214, "ok": 214 } ] }, "vendorStatus": { "page": "https://status.honeycomb.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:17.637457546Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.honeycomb/mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "githubStars": 28, "securityTxt": { "url": "https://honeycomb.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:49.534670121Z" }, "llmsTxt": { "url": "https://docs.honeycomb.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:23:11.617931168Z" }, "domain": { "domain": "honeycomb.io", "checkedAt": "2026-11-01T14:12:37.895563706Z" }, "pages": [ { "url": "https://changelog.honeycomb.io/", "kind": "changelog", "status": 0, "checkedAt": "2026-11-04T08:16:22.238769817Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true }, { "url": "https://www.honeycomb.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:41:02.167425031Z", "changedAt": "2026-11-03T08:06:55.29202553Z", "fingerprint": "cc55e59dbc8d" }, { "url": "https://www.honeycomb.io/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:41:04.630185931Z", "changedAt": "2026-11-03T08:06:57.784332085Z", "fingerprint": "51602bc012d0" }, { "url": "https://www.honeycomb.io/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:41:06.760623981Z", "changedAt": "2026-11-03T08:07:00.196017318Z", "fingerprint": "b691d7c4af5c" } ], "mcpTools": { "url": "https://mcp.honeycomb.io/mcp", "checkedAt": "2026-11-04T01:22:47.870034582Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:43.761722159Z" }, "github": { "repo": "honeycombio/agent-skill", "checkedAt": "2026-11-02T08:54:48.0222443Z", "stars": 28, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-09T22:47:47Z", "openIssues": 3, "openPRs": 1, "issuesOpened90d": 1, "issuesClosed90d": 1, "prsMerged90d": 4, "ci": { "branch": "main", "runs": 50, "success": 43, "failure": 7, "other": 0, "latest": "success", "latestAt": "2026-10-09T22:48:09Z" }, "replies": { "sampled": 9, "unanswered": 3, "medianDays": 3.7 } }, "updatedAt": "2026-11-04T20:46:51.103674148Z" } }, "edges": [ { "by": 20, "category": "reliability", "leads": "honeycomb-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": "Scored as a hosted MCP server. status.honeycomb.io is an Atlassian Statuspage with components for US1, EU1, the website and the sandbox. It has no MCP component, though MCP incidents are posted there, which takes 15 as sentry-mcp and slack-mcp take for a vendor page with no MCP component (15). history.atom lists five incidents from 6 August to 4 November 2026, each limited to one region, one product or a subset of requests. US1 queries over older data erroring for 67 minutes on 10 August, Canvas not loading for 38 minutes on 21 August, degraded US event ingest for 12 minutes on 20 October, slower query execution and SLO processing in the US from 07:04 to 09:26 PDT on 20 October, and SLO, Trigger and anomaly emails failing for 15 minutes on 22 October. None took the query path down for everyone, so minor only (20). Per-tool limits are published with numbers (15). Rate-limit errors carry the time to retry after, which counts as Retry-After alone. No backoff guidance or idempotency keys for the nine write tools were found (10). No SLA found in the terms, and honeycomb.io/sla returned 404 on 9 October (0). The docs still list MCP among betas graduated to general availability (10). 15+20+15+10+0+10 = 70." }, "scores": { "a": 50, "b": 70 } }, { "by": 11, "category": "schema", "leads": "honeycomb-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": "The server is closed source and `tools/list` needs sign-in, so we could not read the input schemas. Partial credit for a contract that exists but is not public (12). docs.honeycomb.io publishes llms.txt and a Markdown twin of every page (10). The tools reference says what each of the 36 tools returns and when an agent reaches for it, for example calling `get_workspace_context` first and `list_memories` before `read_memory`. These are docs, not the definitions the model sees (14). Parameters are mentioned only in passing, with no types, enums or required fields published (4). A use-cases page and a troubleshooting page document the Unauthorized, rate-limit, permission and not-found errors with causes and fixes (9). The registry entry carries version 1.0.0 and Honeycomb links a UI changelog and an API changelog, but changelog.honeycomb.io still disallows unnamed crawlers, so we could not confirm MCP entries (8)." }, "scores": { "a": 46, "b": 57 } }, { "by": 10, "category": "payments", "leads": "better-stack", "name": "Payments \u0026 pricing", "reasons": { "a": "Read with the hosted rubric. No x402, MPP or L402 (0). Per-unit prices are public without login, by GB and region for telemetry, per responder, per status page and per phone number (20). The Free plan has 10 monitors, a status page and 3 GB of logs, the signup page says Sign up for free and names no card, and we did not run the signup flow (20). A person signs up in a browser and mints a token or completes OAuth there (0). 0 + 20 + 20 + 0 = 40.", "b": "No x402, MPP or L402 (0). Plan prices are public, Free and Pro from $150 a month for 50 million events, and MCP is in every plan with no per-call price (10). The Free plan is described as free forever and the signup guide asks for an email address or Google account with no payment step (20). A person signs up in a browser, a Team Owner enables Honeycomb Intelligence, and then OAuth consent or a Team Owner's API key is needed (0)." }, "scores": { "a": 40, "b": 30 } }, { "by": 10, "category": "maintenance", "leads": "honeycomb-mcp", "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": "Every dated source of the vendor's own was counted. The product changelogs at changelog.honeycomb.io and api-changelog.honeycomb.io still disallow unnamed crawlers (the docs' changelog links redirect there), so they weren't read. The companion plugin in honeycombio/agent-skill carries its own version in its plugin manifests. 1.2.3 on 9 October 2026 trimmed the skill descriptions, 26 days before this check (30). In the 90 days from 6 August it moved through 1.2.0 (19 August), 1.2.1 (26 August, Rust setup skill), 1.2.2 (20 September, a GenAI instrumentation fix) and 1.2.3 (9 October), three or more releases that change skill content (20). A support site, a community Slack and a `feedback` tool reach the team, and the plugin repository merged an outside contributor's fix on 17 July, per the 9 October check. GitHub's issue pages weren't readable on 4 November (10). `io.honeycomb/mcp` 1.0.0 is in the official MCP registry under the vendor's domain namespace, published 29 April 2026 (15). The plugin repository runs structural and scenario test workflows. The server itself is closed (6)." }, "scores": { "a": 71, "b": 81 } }, { "by": 8, "category": "security", "leads": "honeycomb-mcp", "name": "Security \u0026 auth", "reasons": { "a": "OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.", "b": "OAuth authorisation code with PKCE S256, dynamic client registration, client ID metadata documents and refresh tokens. Since the 9 October check the consent screen lets the owner choose read all, read and write all, or a custom choice per resource, with scopes such as `boards:read`, `triggers:write` and `investigations:write` beside `environments:read` and `queries:read`. Connections made earlier keep `mcp:read` or `mcp:write`. The alternative is a Management API key whose scopes are fixed at creation and which can be disabled or deleted (28). Tools are read-only unless a write scope is granted, members with a read-only role can choose only read scopes, API keys are limited to chosen environments, and there is no delete tool. No confirmation step for writes was found (15). Trace, log and span content is untrusted text, and no injection guidance was found in the MCP docs (2). The Activity Log records OAuth sessions with requested and granted scopes and one event per query run with its source, MCP included. The compliance page describes activity logging as for enterprise customers (11). SOC 2 Type II each year with penetration tests by an independent firm, HIPAA BAAs and an email disclosure route under a bug bounty page whose rewards are all at Honeycomb's discretion, so the bounty isn't counted. No security.txt, no stated acknowledgement time, and the scope names ui.honeycomb.io and api.honeycomb.io, not the MCP hosts. ISO 27001 is claimed only for the cloud hosts. One certification and a disclosure route, set between mailersend's 8 (disclosure route, discretionary bounty, no certification) and daytona's 15 (disclosure route, SOC 2 and ISO 27001, discretionary reward not counted) (12)." }, "scores": { "a": 60, "b": 68 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Better Stack, Inc.", "b": "Honeycomb", "name": "Vendor" }, { "a": "https://mcp.betterstack.com", "b": "https://mcp.honeycomb.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Your plan", "name": "Pricing" }, { "a": "$0.10 per GB of traffic", "b": "not published", "name": "Price for observability logs" }, { "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": "Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT", "name": "Licence" }, { "a": "148", "b": "36", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.honeycomb/mcp", "name": "MCP registry" }, { "a": "2026-11-02", "b": "2026-10-09", "name": "Last release" }, { "a": "no date given", "b": "2025-05-22", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "6 stars", "b": "27 stars", "name": "Popularity" } ], "faq": [ { "answer": "Honeycomb MCP scores 60.7 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 5 of 7 scored categories. Better Stack leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Better Stack or Honeycomb MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Better Stack and Honeycomb MCP need an API key?" }, { "answer": "Yes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and Honeycomb MCP at https://mcp.honeycomb.io/mcp.", "question": "Can an agent call Better Stack and Honeycomb MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "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, 70 against 50", "Schema \u0026 documentation, 57 against 46", "Security \u0026 auth, 68 against 60", "Maintenance \u0026 community, 81 against 71" ], "also": null, "goodFor": "Agents that investigate latency and error spikes in a team already sending traces and events to Honeycomb, and that record findings as Boards, Triggers or SLOs.", "slug": "honeycomb-mcp", "watchFor": "Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters" } ], "history": { "better-stack": null, "honeycomb-mcp": [ { "causes": [ "product", "correction" ], "date": "2026-11-04", "delta": 2.2, "from": 58.5, "fromGrade": "C", "to": 60.7, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 58.3, "fromGrade": "C", "to": 58.5, "toGrade": "C" } ] }, "job": { "capability": "observability.logs", "name": "Observability logs" }, "others": [ { "json": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io.json", "title": "Better Stack vs incident.io API", "url": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.json", "title": "Better Stack vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.json", "title": "Better Stack vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-better-stack.json", "title": "Axiom MCP Server vs Better Stack", "url": "https://www.anchorterminal.com/compare/axiom-vs-better-stack" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json", "title": "Axiom MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/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-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/causely-vs-honeycomb-mcp.json", "title": "Causely MCP server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.json", "title": "Datadog MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.json", "title": "Grafana MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.json", "title": "Better Stack vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.json", "title": "Honeycomb MCP vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.json", "title": "Honeycomb MCP vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic" } ], "panel": null, "scores": [ { "better-stack": 50, "by": 20, "edge": "honeycomb-mcp", "honeycomb-mcp": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "better-stack": 46, "by": 11, "edge": "honeycomb-mcp", "honeycomb-mcp": 57, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "better-stack": 55, "by": 2, "edge": "better-stack", "honeycomb-mcp": 53, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "better-stack": 60, "by": 8, "edge": "honeycomb-mcp", "honeycomb-mcp": 68, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "better-stack": 40, "by": 10, "edge": "better-stack", "honeycomb-mcp": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "better-stack": 71, "by": 10, "edge": "honeycomb-mcp", "honeycomb-mcp": 81, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "better-stack": 69, "by": 1, "edge": "honeycomb-mcp", "honeycomb-mcp": 70, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Honeycomb MCP scores 60.7 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 5 of 7 scored categories. Better Stack leads on payments \u0026 pricing. Both do observability logs.", "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.", "honeycomb-mcp": "OAuth now lets an owner grant read or write per resource, so an agent can be held to queries and reads across the 36 tools, and per-tool rate limits are published. Tool input schemas are visible only after sign-in, no injection guidance was found for telemetry content, and the product changelogs disallow unnamed crawlers." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp", "json": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.min.md" }, "markdown": "Honeycomb MCP scores 60.7 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 5 of 7 scored categories. Better Stack leads on payments \u0026 pricing. Both do observability logs.\n\n- Better Stack: grade C, 54.2/100, rank #811 of 1349. Markdown https://www.anchorterminal.com/tools/better-stack.md · JSON https://www.anchorterminal.com/api/v1/tools/better-stack.json\n- Honeycomb MCP: grade C, 60.7/100, rank #579 of 1349. Markdown https://www.anchorterminal.com/tools/honeycomb-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### 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- Payments \u0026 pricing, 40 against 30\n\nWatch for: No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying\n\n### Honeycomb MCP (C)\n\nGood for: Agents that investigate latency and error spikes in a team already sending traces and events to Honeycomb, and that record findings as Boards, Triggers or SLOs.\n\nAhead on:\n- Reliability, 70 against 50\n- Schema \u0026 documentation, 57 against 46\n- Security \u0026 auth, 68 against 60\n- Maintenance \u0026 community, 81 against 71\n\nWatch for: Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters\n\n\n## Why the edge\n\n### Reliability: Honeycomb MCP +20\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- Honeycomb MCP (70): Scored as a hosted MCP server. status.honeycomb.io is an Atlassian Statuspage with components for US1, EU1, the website and the sandbox. It has no MCP component, though MCP incidents are posted there, which takes 15 as sentry-mcp and slack-mcp take for a vendor page with no MCP component (15). history.atom lists five incidents from 6 August to 4 November 2026, each limited to one region, one product or a subset of requests. US1 queries over older data erroring for 67 minutes on 10 August, Canvas not loading for 38 minutes on 21 August, degraded US event ingest for 12 minutes on 20 October, slower query execution and SLO processing in the US from 07:04 to 09:26 PDT on 20 October, and SLO, Trigger and anomaly emails failing for 15 minutes on 22 October. None took the query path down for everyone, so minor only (20). Per-tool limits are published with numbers (15). Rate-limit errors carry the time to retry after, which counts as Retry-After alone. No backoff guidance or idempotency keys for the nine write tools were found (10). No SLA found in the terms, and honeycomb.io/sla returned 404 on 9 October (0). The docs still list MCP among betas graduated to general availability (10). 15+20+15+10+0+10 = 70.\n\n### Schema \u0026 documentation: Honeycomb MCP +11\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- Honeycomb MCP (57): The server is closed source and `tools/list` needs sign-in, so we could not read the input schemas. Partial credit for a contract that exists but is not public (12). docs.honeycomb.io publishes llms.txt and a Markdown twin of every page (10). The tools reference says what each of the 36 tools returns and when an agent reaches for it, for example calling `get_workspace_context` first and `list_memories` before `read_memory`. These are docs, not the definitions the model sees (14). Parameters are mentioned only in passing, with no types, enums or required fields published (4). A use-cases page and a troubleshooting page document the Unauthorized, rate-limit, permission and not-found errors with causes and fixes (9). The registry entry carries version 1.0.0 and Honeycomb links a UI changelog and an API changelog, but changelog.honeycomb.io still disallows unnamed crawlers, so we could not confirm MCP entries (8).\n\n### Payments \u0026 pricing: Better Stack +10\n\n- Better Stack (40): 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.\n- Honeycomb MCP (30): No x402, MPP or L402 (0). Plan prices are public, Free and Pro from $150 a month for 50 million events, and MCP is in every plan with no per-call price (10). The Free plan is described as free forever and the signup guide asks for an email address or Google account with no payment step (20). A person signs up in a browser, a Team Owner enables Honeycomb Intelligence, and then OAuth consent or a Team Owner's API key is needed (0).\n\n### Maintenance \u0026 community: Honeycomb MCP +10\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- Honeycomb MCP (81): Every dated source of the vendor's own was counted. The product changelogs at changelog.honeycomb.io and api-changelog.honeycomb.io still disallow unnamed crawlers (the docs' changelog links redirect there), so they weren't read. The companion plugin in honeycombio/agent-skill carries its own version in its plugin manifests. 1.2.3 on 9 October 2026 trimmed the skill descriptions, 26 days before this check (30). In the 90 days from 6 August it moved through 1.2.0 (19 August), 1.2.1 (26 August, Rust setup skill), 1.2.2 (20 September, a GenAI instrumentation fix) and 1.2.3 (9 October), three or more releases that change skill content (20). A support site, a community Slack and a `feedback` tool reach the team, and the plugin repository merged an outside contributor's fix on 17 July, per the 9 October check. GitHub's issue pages weren't readable on 4 November (10). `io.honeycomb/mcp` 1.0.0 is in the official MCP registry under the vendor's domain namespace, published 29 April 2026 (15). The plugin repository runs structural and scenario test workflows. The server itself is closed (6).\n\n### Security \u0026 auth: Honeycomb MCP +8\n\n- Better Stack (60): OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.\n- Honeycomb MCP (68): OAuth authorisation code with PKCE S256, dynamic client registration, client ID metadata documents and refresh tokens. Since the 9 October check the consent screen lets the owner choose read all, read and write all, or a custom choice per resource, with scopes such as `boards:read`, `triggers:write` and `investigations:write` beside `environments:read` and `queries:read`. Connections made earlier keep `mcp:read` or `mcp:write`. The alternative is a Management API key whose scopes are fixed at creation and which can be disabled or deleted (28). Tools are read-only unless a write scope is granted, members with a read-only role can choose only read scopes, API keys are limited to chosen environments, and there is no delete tool. No confirmation step for writes was found (15). Trace, log and span content is untrusted text, and no injection guidance was found in the MCP docs (2). The Activity Log records OAuth sessions with requested and granted scopes and one event per query run with its source, MCP included. The compliance page describes activity logging as for enterprise customers (11). SOC 2 Type II each year with penetration tests by an independent firm, HIPAA BAAs and an email disclosure route under a bug bounty page whose rewards are all at Honeycomb's discretion, so the bounty isn't counted. No security.txt, no stated acknowledgement time, and the scope names ui.honeycomb.io and api.honeycomb.io, not the MCP hosts. ISO 27001 is claimed only for the cloud hosts. One certification and a disclosure route, set between mailersend's 8 (disclosure route, discretionary bounty, no certification) and daytona's 15 (disclosure route, SOC 2 and ISO 27001, discretionary reward not counted) (12).\n\n## Score by category\n\n| Category | Weight | Better Stack | Honeycomb MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 70 | Honeycomb MCP +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 46 | 57 | Honeycomb MCP +11 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 53 | Better Stack +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 68 | Honeycomb MCP +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Better Stack +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 81 | Honeycomb MCP +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 70 | Honeycomb MCP +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.2 · C** | **60.7 · C** | |\n\n## Facts side by side\n\n| Fact | Better Stack | Honeycomb MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Better Stack, Inc. | Honeycomb |\n| Hosted endpoint | `https://mcp.betterstack.com` | `https://mcp.honeycomb.io/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Your plan |\n| Price for observability logs | $0.10 per GB of traffic | not published |\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 | Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT |\n| Tools exposed | 148 | 36 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.honeycomb/mcp` |\n| Last release | 2026-11-02 | 2026-10-09 |\n| Terms last updated | no date given | 2025-05-22 |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 6 stars | 27 stars |\n\n## How the scores have moved\n\n### Better Stack\n\nNo score change since it was listed.\n\n### Honeycomb MCP\n\n- +2.2 on 4 November 2026: product, correction\n- +0.2 on 27 October 2026: checklist\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**Honeycomb MCP.** OAuth now lets an owner grant read or write per resource, so an agent can be held to queries and reads across the 36 tools, and per-tool rate limits are published. Tool input schemas are visible only after sign-in, no injection guidance was found for telemetry content, and the product changelogs disallow unnamed crawlers.\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### Honeycomb MCP\n\n1. Use https://mcp.honeycomb.io/mcp for US teams and https://mcp.eu1.honeycomb.io/mcp for EU teams. A team's data lives in one region only\n2. If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings\n3. Ask the owner to choose Customize on the consent screen and grant only the resources the task needs. The agent sees only the tools its scopes allow\n4. Send `X-MCP-Toolset: query` or `canvas` to load a subset of the 36 tools. Call `get_workspace_context` first, then `find_columns`, before `run_query`\n5. For unattended runs send `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e` from a Management key with only Model Context Protocol and Environments scopes\n\n## Questions\n\n### Which is better for AI agents, Better Stack or Honeycomb MCP?\n\nHoneycomb MCP scores 60.7 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 5 of 7 scored categories. Better Stack leads on payments \u0026 pricing.\n\n### Do Better Stack and Honeycomb MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Better Stack and Honeycomb MCP without installing anything?\n\nYes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and Honeycomb MCP at https://mcp.honeycomb.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"better-stack\", \"b\": \"honeycomb-mcp\"}`. From a terminal: `anchor compare better-stack honeycomb-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/better-stack.json and https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json\n\n## Other comparisons with Better Stack or Honeycomb MCP\n\n- [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md)\n- [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md)\n- [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)\n- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.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 New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)\n- [Causely MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp.md)\n- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)\n- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)\n- [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.md)\n- [Honeycomb MCP vs Sentry MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.md)\n- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Better Stack vs Honeycomb MCP", "url": "" } ], "description": "Honeycomb MCP scores 60.7 (C) to Better Stack's 54.2 (C) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Better Stack C 54.2", "Honeycomb MCP C 60.7", "scores" ], "h1": "Better Stack vs Honeycomb MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/better-stack-vs-honeycomb-mcp", "published": "2026-10-01", "section": "tools", "title": "Better Stack vs Honeycomb MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp" }, "tokens": { "markdown": 5250, "slim": 3380 }, "version": 1 }