# Honeycomb MCP vs Neat Pulse MCP

> Honeycomb MCP scores 62.6 (B) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp
- Markdown: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md (~5,000 tokens)
- Slim: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.min.md (~1,030 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <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-18

Honeycomb MCP scores 62.6 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security & auth. Both do metrics and monitoring.

- Honeycomb MCP: grade B, 62.6/100, rank #673 of 1557. Markdown https://www.anchorterminal.com/tools/honeycomb-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json
- Neat Pulse MCP: grade E, 45.8/100, rank #1268 of 1557. Markdown https://www.anchorterminal.com/tools/neat-pulse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Honeycomb MCP (B)

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 35
- Schema & documentation, 57 against 49
- Agent ergonomics, 53 against 43
- Payments & pricing, 45 against 0
- Maintenance & community, 81 against 59
- Transparency & trust, 70 against 56

Also in its favour:
- A hosted endpoint, with nothing to install

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

### Neat Pulse MCP (E)

Good for: IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.

Ahead on:
- Security & auth, 79 against 68

Also in its favour:
- Runs on your own machine

Watch for: Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent


## Why the edge

### Payments & pricing: Honeycomb MCP +45

- Honeycomb MCP (45): 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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
- Neat Pulse MCP (0): No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0.

### Reliability: Honeycomb MCP +35

- 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.
- Neat Pulse MCP (35): Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.

### Maintenance & community: Honeycomb MCP +22

- 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).
- Neat Pulse MCP (59): 1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59.

### Transparency & trust: Honeycomb MCP +14

- Honeycomb MCP (70): The hosted server is closed, under published Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin is MIT (17). The privacy notice, the DPA and an AI policy page dated 21 September 2026 are public. The AI page says MCP's model provider is whichever the client uses, and that Honeycomb uses no provider that trains foundation models on input. Telemetry is deleted after the retention window, 60 days for most customers. The terms also let Honeycomb use customer data to improve its services, and the AI page says Honeycomb may fine-tune pre-trained models (22). The self-hosted server carries a deprecation notice dated 21 August 2025. No deprecation policy was found, the AI terms allow any part of Honeycomb Intelligence to be changed or ended at any time with commercially reasonable efforts at notice, and the docs say rate limits may change (6). The subprocessor list is public with purposes and countries, the DPA promises 30 days' notice of new subprocessors, and customers choose a US or EU data location (19).
- Neat Pulse MCP (56): Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47.

### Security & auth: Neat Pulse MCP +11

- 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).
- Neat Pulse MCP (79): Scoped, revocable Pulse API tokens with a rotation endpoint, created only by organisation Owners and passed in an environment variable. The scopes are coarse, Read or everything (27). A Read-only token blocks every change per the setup guide, and the reference flags irreversible tools, but confirmation is left to the assistant (14). Room notes and device names are text people enter, and no prompt-injection guidance was found (5). Pulse audit logs record every MCP action under the token's name, and an MCP tool reads them (15). security.txt valid to August 2027, a vulnerability reporting policy, public advisories through November 2026, and a support article stating ISO 27001 certification. No bug bounty found (18). 27 + 14 + 5 + 15 + 18 = 79.

### Agent ergonomics: Honeycomb MCP +10

- Honeycomb MCP (53): 36 tools is above the 30 line (5). The `X-MCP-Toolset` header loads `query` or `canvas` subsets, and the docs don't say how many tools each holds (add 8, so 13). Size controls are described per tool, such as up to 100 datasets or 100 columns a call, subtree zoom on `get_trace` and query limits. Pagination parameters aren't documented (10). Errors are documented with causes and fixes, and the rate-limit message names the retry time. No error code list was found (12). The reference labels each tool read or write and `update_slo` keeps omitted fields. No idempotency keys were found, and we couldn't confirm readOnlyHint or destructiveHint annotations (8). `get_workspace_context` takes no parameters, relative time is the default, and setup is one command or link in nine documented clients. SDKs don't apply (10).
- Neat Pulse MCP (43): 30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43.

## Score by category

| Category | Weight | Honeycomb MCP | Neat Pulse MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 70 | 35 | Honeycomb MCP +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 49 | Honeycomb MCP +8 |
| Agent ergonomics | 13% | 53 | 43 | Honeycomb MCP +10 |
| Security & auth | 14% | 68 | 79 | Neat Pulse MCP +11 |
| Payments & pricing | 10% | 45 | 0 | Honeycomb MCP +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 59 | Honeycomb MCP +22 |
| Transparency & trust | 7% | 70 | 56 | Honeycomb MCP +14 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.6 · B** | **45.8 · E** | |

## Facts side by side

| Fact | Honeycomb MCP | Neat Pulse MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Honeycomb | Neat |
| Hosted endpoint | `https://mcp.honeycomb.io/mcp` | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | API key |
| Pricing | Your plan | Your plan |
| x402 | no | no |
| Licence | Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT | none |
| Tools exposed | 36 | 30 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `io.honeycomb/mcp` | not listed |
| Last release | 2026-10-09 | 2026-11-17 |
| Terms last updated | 2025-05-22 | 2025-03-26 |
| Privacy policy last updated | no date given | 2026-07-13 |
| 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 | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 27 stars | none |

## How the scores have moved

### Honeycomb MCP

- +1.9 on 13 November 2026 (C to B): checklist
- +2.2 on 4 November 2026: product, correction
- +0.2 on 27 October 2026: checklist

### Neat Pulse MCP

No score change since it was listed.

## Verdicts

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

**Neat Pulse MCP.** Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.

## Before you call either

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

### Neat Pulse MCP

1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices
2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room
3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy
4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`
5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`

## Questions

### Which is better for AI agents, Honeycomb MCP or Neat Pulse MCP?

Honeycomb MCP scores 62.6 (B) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security & auth.

### Do Honeycomb MCP and Neat Pulse MCP need an API key?

Honeycomb MCP takes an API key or an OAuth sign-in. Neat Pulse MCP needs an API key.

### Can an agent call Honeycomb MCP and Neat Pulse MCP without installing anything?

Honeycomb MCP has a hosted endpoint at https://mcp.honeycomb.io/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "honeycomb-mcp", "b": "neat-pulse-mcp"}`. From a terminal: `anchor compare honeycomb-mcp neat-pulse-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json

## Other comparisons with Honeycomb MCP or Neat Pulse MCP

- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)
- [Better Stack vs Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)
- [Causely MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp.md)
- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)
- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)
- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md)
- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)
- [Datadog MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md)
- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)
- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)
- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)
- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md)
- [Better Stack vs Honeycomb MCP](https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md)
- [Honeycomb MCP vs Sentry MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.md)
- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-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
