Axiom MCP Server vs Honeycomb MCP

Axiom MCP Server 60

No x402, MPP or L402 (0). The pricing page states the platform fee, the free allowances, add-on prices and that usage carries volume discounts, with a calculator rather than a printed per-unit rate (20). The Personal plan is free with no card (20). POST /v2/orgs/provision needs no authentication and returns a working token, so an agent can start without a person, though a person must claim the organisation within 24 hours for it to persist (20). 0 + 20 + 20 + 20 = 60.

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

Axiom MCP Server 63

31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a sendFeedback tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.

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

Axiom MCP Server 62

The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use queryMetrics for metrics datasets instead of queryDataset, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.

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