Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Honeycomb MCPShortlist candidate | MCP Server for Splunk platformMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Honeycomb · Publisher source ↗ | First-party MCP ecosystem:splunk-platform · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| Shared repository stars | 0 Shared repository stars (not MCP-specific) · checked 2026-10-20 | Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | OAuth to Honeycomb's current hosted MCP service. | Splunk documents encrypted token handling and platform authentication for the managed MCP Server for Splunk Platform 2.0. No public-repository metric is required for this managed-service identity. |
| Cost | No separate MCP fee is documented. Honeycomb has a free tier plus paid Pro/Enterprise observability plans; queries and telemetry usage remain subject to the underlying account limits/plan. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | The hosted MCP operates within the authenticated Honeycomb account/tenant permissions. The current hosted service is distinct from Honeycomb's older archived open-source MCP repository. | Splunk roles, capabilities, and tool-level configuration constrain searches and platform access. |
| Data handling | Not documented in the reviewed sources. The reviewed current Honeycomb hosted-MCP material does not provide a specific MCP retention or training statement. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive monitoring & observability information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can expose observability data that may include production telemetry, service names, query results, traces and operational context. Some current capabilities may change service configuration or derived resources depending on the hosted tool set. | Search results may expose sensitive security and operational events; broad search roles should not be used. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-09-05 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →