Better Stack vs Honeycomb MCP

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.

Honeycomb MCP 65

Scored as a hosted MCP server. status.honeycomb.io is an Atlassian Statuspage with 14 components for US1, EU1, the website and the sandbox. It has no MCP component, though MCP incidents are posted there (17). Four incidents in the 90 days to 9 October 2026, all marked minor. Querying failures for about 30 minutes on 31 July, with a postmortem. Triggers failing intermittently in the EU on 27 and 28 July. US1 queries over older data erroring for 67 minutes on 10 August. Canvas not loading for 38 minutes on 21 August. The 10 August outage hit the query path the server depends on for over an hour, so we score between minor-only and one major (15). Per-tool limits are published with numbers (15). Rate-limit errors carry the time to retry after. No backoff guidance or idempotency keys for the nine write tools were found (8). No SLA found in the terms, and honeycomb.io/sla returns 404 (0). The docs list MCP as graduated to general availability (10).

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.

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 34 tools returns and when an agent reaches for it, for example calling get_workspace_context first and list_boards before update_board. These are docs, not the definitions the model sees (14). Parameters are mentioned only in passing, such as metric_name and usage_mode, 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 both hosts disallow unnamed crawlers, so we could not confirm MCP entries (8).

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 & 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.

Honeycomb MCP 71

OAuth authorisation code with PKCE S256, dynamic client registration, client ID metadata documents, refresh tokens and the scopes mcp:read and mcp:write, with the token accepted in the header only. Sessions are listed on the account's Integrations tab. 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 until mcp:write is granted at consent or on the key, API keys are limited to chosen environments, the Activity Log environment is shown through MCP only to Team Owners, 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, annual third-party penetration tests, HIPAA BAAs and a bug bounty by email with discretionary rewards. No security.txt, the trust centre is open only to Pro and Enterprise customers, and the bounty scope names ui.honeycomb.io and api.honeycomb.io, not the MCP hosts (15).

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.

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).

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.

Honeycomb MCP 61

The product changelogs at changelog.honeycomb.io and api-changelog.honeycomb.io disallow unnamed crawlers, so we didn't read them and scored from what else is dated. The docs sitemap gives 29 September 2026 for the tools reference, the companion plugin reached 1.2.2 on 20 September, and the AI policy page was updated on 21 September. Docs dates are weaker evidence than a release note (20). The plugin repository has 14 commits since 11 July, with fixes released on 21 August, 26 August and 20 September, and one explicit version bump. Half credit without the changelog (10). 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 and has five open issues (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).