# Better Stack vs Honeycomb MCP

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

- Canonical: https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp
- Markdown: https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md (~5,250 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

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 & pricing. Both do observability logs.

- 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
- 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
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Better Stack (C)

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

Ahead on:
- Payments & pricing, 40 against 30

Watch for: No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying

### Honeycomb MCP (C)

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

Ahead on:
- Reliability, 70 against 50
- Schema & documentation, 57 against 46
- Security & auth, 68 against 60
- Maintenance & community, 81 against 71

Watch for: Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters


## Why the edge

### Reliability: Honeycomb MCP +20

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

### Schema & documentation: Honeycomb MCP +11

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

### Payments & pricing: Better Stack +10

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

### Maintenance & community: Honeycomb MCP +10

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

### Security & auth: Honeycomb MCP +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 (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).

## Score by category

| Category | Weight | Better Stack | Honeycomb MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 70 | Honeycomb MCP +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 46 | 57 | Honeycomb MCP +11 |
| Agent ergonomics | 13% (16.2 this run) | 55 | 53 | Better Stack +2 |
| Security & auth | 14% (17.5 this run) | 60 | 68 | Honeycomb MCP +8 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Better Stack +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 71 | 81 | Honeycomb MCP +10 |
| Transparency & trust | 7% (8.8 this run) | 69 | 70 | Honeycomb MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **54.2 · C** | **60.7 · C** | |

## Facts side by side

| Fact | Better Stack | Honeycomb MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Better Stack, Inc. | Honeycomb |
| Hosted endpoint | `https://mcp.betterstack.com` | `https://mcp.honeycomb.io/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Your plan |
| Price for observability logs | $0.10 per GB of traffic | not published |
| x402 | no | no |
| 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 |
| Tools exposed | 148 | 36 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.honeycomb/mcp` |
| Last release | 2026-11-02 | 2026-10-09 |
| Terms last updated | no date given | 2025-05-22 |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 6 stars | 27 stars |

## How the scores have moved

### Better Stack

No score change since it was listed.

### Honeycomb MCP

- +2.2 on 4 November 2026: product, correction
- +0.2 on 27 October 2026: checklist

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

## Before you call either

### Better Stack

1. Connect with `claude mcp add betterstack --transport http https://mcp.betterstack.com` and sign in, or send a team-based API token as `Authorization: Bearer`; pick Read access unless the task writes
2. Send `X-MCP-Tools-Only: monitors,monitor,incidents` or a similar list to keep the 148-tool list out of context, and `X-MCP-Tools-Except: remove_dashboard,remove_chart` to block deletes
3. Call `Get query instructions` or `Plan query windows` before `Execute query`, since long time ranges are split into windows and nothing documents a result size limit
4. No rate limit is published. Back off on a 429 and don't retry writes blindly, because there are no idempotency keys; `Upsert catalog records` is the one write documented as safe to repeat
5. Reopening an incident only works within 24 hours of its resolution, and a comment can only be edited or removed by its author or an API token

### Honeycomb MCP

1. 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
2. If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings
3. 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
4. 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`
5. For unattended runs send `Authorization: Bearer <KEY_ID>:<SECRET_KEY>` from a Management key with only Model Context Protocol and Environments scopes

## Questions

### Which is better for AI agents, Better Stack or Honeycomb MCP?

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

### Do Better Stack and Honeycomb MCP need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Better Stack and Honeycomb MCP without installing anything?

Yes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and Honeycomb MCP at https://mcp.honeycomb.io/mcp.


## For agents

- 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
- 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`
- 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

## Other comparisons with Better Stack or Honeycomb MCP

- [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md)
- [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md)
- [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md)
- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)
- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md)
- [Better Stack vs Causely MCP server](https://www.anchorterminal.com/compare/better-stack-vs-causely.md)
- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)
- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md)
- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)
- [Causely MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp.md)
- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)
- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)
- [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.md)
- [Honeycomb MCP vs Sentry MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.md)
- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp