Honeycomb MCP (official, remote)

65/100

Capped at 65: vendor-hosted, source not published. The tests add up to 65.

Last tested 2026-11-11 (Fresh: tested within 30 days) Needs credentialsNo tool call tested yet OAuth

Advisories: not checked (remote-only)

Security review: not tested

Test points add up to 65; the score is capped at 65 (vendor-hosted, source not published). Not a quality or security rating. Capped listings are not promoted in our rankings or on the homepage. Why scores are capped

Test points before the cap (65/100)

  • Install20/20
  • Handshake5/30
  • Maintenance25/25
  • Docs15/15
  • License0/10

Vendor-hosted
What we probed (2026-11-11, no credentials): an MCP initialize POST to https://mcp.honeycomb.io/mcp returned HTTP 401 with an OAuth challenge (authorization server https://ui.honeycomb.io). We did not sign in or use a key, so no tools were listed or called. Honeycomb's docs state this endpoint (and an EU one), with OAuth consent or a Honeycomb API key, and scopes that can be read-only. Vendor-hosted, no public source: 65 cap, not source-audited, core tools not tested.
Honeycomb-hosted endpoint. Initialize returned HTTP 401 with an OAuth challenge (resource metadata lists https://ui.honeycomb.io as the authorization server). We did not sign in or use a key, so no tools were listed or called. Source isn't public: vendor-hosted 65 cap (Our review, Nov 11, 2026).
Maintenance date 2026-11-03: date from page metadata (JSON-LD WebPage dateModified 2026-11-03T17:28:41.835Z) of https://docs.honeycomb.io/integrations/mcp/configuration-guide, fetched 2026-11-11T07:33Z. Not a changelog entry.
Sources: https://docs.honeycomb.io/integrations/mcp/configuration-guide · https://registry.modelcontextprotocol.io/v0/servers?search=io.honeycomb/mcp

Transport: Streamable HTTP · not tested

Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.

Permissions: tool permissions pending · Auth: OAuth · Rate limit: unknown · Pricing unit: unknown

Auth: OAuth. Rate limit: unknown. Pricing unit: unknown.

HTTP 401, WWW-Authenticate resource_metadata https://mcp.honeycomb.io/.well-known/oauth-protected-resource, OAuth metadata lists authorization server https://ui.honeycomb.io

Score 65/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-11 · Server version not reported · Remote endpoint https://mcp.honeycomb.io/mcp (streamable-http)

Summary: Honeycomb MCP (official, remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
0
Context cost
Pending The token cost figure is pending. ranking
Login
Needs OAuth sign-in
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20Endpoint https://mcp.honeycomb.io/mcp reachable over streamable-http (HTTP 401) in 0.4s; no install step for remote servers.
handshakeauth-gated5Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.honeycomb.io/.well-known/oauth-protected-resource; metadata lists authorization server https://ui.honeycomb.io). We do not sign in; not counted as working until a credentialed test exists.
maintenancepass25Vendor-hosted rule: scored from vendor docs page 2026-11-03, date from page metadata (JSON-LD WebPage dateModified 2026-11-03T17:28:41.835Z, fetched 2026-11-11T07:33Z) (https://docs.honeycomb.io/integrations/mcp/configuration-guide), 8 days before test. Registry (corroboration only, not scored): io.honeycomb/mcp 1.0.0 published 2026-04-29.
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://docs.honeycomb.io/integrations/mcp/configuration-guide).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Not tested

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-11-11

  • We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details: initialize POST answered 401; tools/list not sent)
  • Auth response: HTTP 401, WWW-Authenticate resource_metadata https://mcp.honeycomb.io/.well-known/oauth-protected-resource, OAuth metadata lists authorization server https://ui.honeycomb.io. Login is an OAuth sign-in; we did not sign in
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: dated vendor source, vendor docs page (date from page metadata) 2026-11-03 (25/25)
  • License: a hosted service has no license to cite (0/10)
  • Token cost (estimate)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "honeycomb-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-11-11",
  "tools_count": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.honeycomb.io/mcp reachable over streamable-http (HTTP 401) in 0.4s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.honeycomb.io/.well-known/oauth-protected-resource; metadata lists authorization server https://ui.honeycomb.io). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from vendor docs page 2026-11-03, date from page metadata (JSON-LD WebPage dateModified 2026-11-03T17:28:41.835Z, fetched 2026-11-11T07:33Z) (https://docs.honeycomb.io/integrations/mcp/configuration-guide), 8 days before test. Registry (corroboration only, not scored): io.honeycomb/mcp 1.0.0 published 2026-04-29."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://docs.honeycomb.io/integrations/mcp/configuration-guide)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://mcp.honeycomb.io/mcp

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "honeycomb-mcp-remote": {
      "type": "http",
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.honeycomb.io/.well-known/oauth-protected-resource; metadata lists authorization server https://ui.honeycomb.io). We do not sign in; not counted as working until a credentialed test exists.

  1. Install. No install step: it is a remote server at https://mcp.honeycomb.io/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "honeycomb-mcp-remote": {
      "type": "http",
      "url": "https://mcp.honeycomb.io/mcp"
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

Follow this server (RSS) · Monthly changelog

Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an OAuth sign-in · How to protect AI API keys

FAQ

Is Honeycomb MCP deprecated?

No. honeycomb-remote was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Honeycomb MCP?

Nothing; Honeycomb MCP (official, remote) is not deprecated as of 2026-11-11.

Does Honeycomb MCP need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

TestedMCP: 65/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue