{ "data": { "a": { "slug": "axiom", "name": "Axiom MCP Server", "vendor": "Axiom, Inc.", "vendorUrl": "https://axiom.co", "kind": "mcp", "category": "observability", "summary": "Axiom's hosted MCP server at mcp.axiom.co lets AI agents query logs, traces, events and metrics in an Axiom organisation with APL, read and manage dashboards, monitors and notifiers, and inspect the service map, over OAuth or a token header.", "url": "https://www.anchorterminal.com/tools/axiom", "markdownUrl": "https://www.anchorterminal.com/tools/axiom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/axiom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/axiom.json", "dns": "axiom.grade.anchorterminal.com", "transports": [ "streamable-http", "sse" ], "remoteUrl": "https://mcp.axiom.co/mcp", "packages": [], "auth": "oauth", "authNotes": "Browser OAuth (recommended) creates a session the agent uses as the signed-in user; sessions are listed and revoked under Settings \u003e Profile. Agents without a browser send `Authorization: Bearer` with a personal access token and `x-axiom-org-id`, or put the organisation id in the URL as `?org-id=`. A PAT has full account rights; scoped API tokens with dataset and action permissions, expiry and dollar query-cost limits exist for the REST API and Skills. EU organisations use mcp.eu.axiom.co.", "pricing": "freemium", "pricingNotes": "Personal plan $0 with no card, with 500 GB a month of data loading compute, 10 GB-hours of query compute, 25 GB storage, 30-day retention. Axiom Cloud $25 a month platform fee plus usage, with an Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage, volume discounts and add-ons (RBAC $50, extended audit logs $50, SAML SSO $100, directory sync $100 a month). An agent can provision a temporary organisation with no account (https://axiom.co/pricing).", "priceSummary": "$25 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, API docs, pricing or terms (checked 2026-11-03). Usage is billed to the organisation; unclaimed agent-created organisations have fixed free limits for 24 hours.", "endpoints": [] }, "toolCount": 31, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://axiom.co/docs/console/intelligence/mcp-server", "llmsTxt": "https://axiom.co/llms.txt", "registryName": "co.axiom/mcp", "capabilities": [ "observability.logs", "observability.traces", "observability.metrics", "observability.incidents", "observability.errors" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "mcp-registry", "oauth", "llms-txt", "status-page", "sla", "security-txt", "bug-bounty", "soc2", "iso27001", "eu-region", "usage-priced", "closed-source" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 68.2, "grade": "B", "agentReady": false, "rank": 269, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "bestFor": "Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.", "strengths": [ "`POST /v2/orgs/provision` needs no account and returns a working token; a person claims the organisation later or it expires in 24 hours", "Query cost limits in dollars per hour and per day on tokens and roles bound what an agent can spend, with 429 past the cap", "OAuth sessions keep tokens away from the agent and are revocable per session; ISO 27001, SOC 2 Type II, a security.txt and a bug bounty policy", "99.9 per cent monthly uptime SLA with service credits, published rate-limit headers and a status page with per-component uptime", "Dated changelog with MCP entries, llms.txt, Markdown twins of every docs page and setup for 16 clients" ], "weaknesses": [ "The server is closed source and tool input schemas are only visible through an authenticated session", "The AI agents overview calls the MCP server read-only while the tools reference lists delete tools for dashboards, monitors and notifiers", "A header-based connection uses a personal access token with full account rights, since scoped API tokens aren't accepted by the MCP server per the docs", "Nine status incidents between 12 August and 30 October 2026, mostly elevated query errors, one of 70 minutes in the US", "Logs and traces come back as untrusted text with no prompt-injection guidance, and the sub-processor list renders through a script our reader couldn't run" ], "agentNotes": [ "With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed", "Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL", "Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner", "Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first", "`deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.2 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 57 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y add-mcp https://mcp.axiom.co/mcp -g", "http": "curl -X POST https://api.axiom.co/v2/orgs/provision -H 'Content-Type: application/json' -d '{\"name\":\"agent-sandbox\"}'", "claudeCode": "claude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp", "config": { "mcpServers": { "axiom": { "url": "https://mcp.axiom.co/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.logs", "tool": "https://letme.dev/axiom" }, "area": "developer", "unitPrices": [ { "item": "Axiom Cloud platform fee", "unit": "month", "usd": 25, "note": "Plus usage beyond the Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage a month" }, { "item": "Role-based access control add-on", "unit": "month", "usd": 50, "note": "Extended audit logs $50, SAML SSO $100, directory sync $100" } ], "provenance": { "legalEntity": "Axiom, Inc.", "domain": "axiom.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://axiom.co/docs/legal/terms-of-service", "privacy": "https://axiom.co/docs/legal/privacy", "statusPage": "https://status.axiom.co", "changelog": "https://axiom.co/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms of service name Axiom, Inc. under California law and carry no last-updated date in the text; the privacy policy and DPA name Axiom Inc. and privacy@axiom.co. No clause on automated reading of the website was found.", "axiom.co/robots.txt allows all crawlers, naming ClaudeBot, Claude-User and others as allowed, and disallows only /api/. trust.axiom.co renders through a script (Vanta) and its sub-processor list was not readable.", "axiom.co/.well-known/security.txt redirects to app.axiom.co, where it names security@axiom.co, a policy at axiom.co/security and an expiry of 1 April 2027.", "status.axiom.co is an incident.io page with six US and six EU components and per-component uptime for August to November 2026; feed.rss holds nine incidents back to 12 August 2026.", "RDAP for axiom.co couldn't be read (the .co registry's RDAP answered 502 and rdap.org returned nothing), so the registration date is blank. firstReleased is 5 December 2024, the v0.0.1 tag of the earlier open-source mcp-server-axiom; the hosted server's own first date isn't on a first-hand page, and its registry entry is from 30 September 2025." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/axiom.json", "live": { "slug": "axiom", "probe": { "target": "https://mcp.axiom.co/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T21:39:14.263725519Z", "lastOk": true, "lastStatus": 401, "lastMs": 72, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 177, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.axiom.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:37:46.118662306Z" }, "versions": [ { "registry": "mcp-registry", "name": "co.axiom/mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "securityTxt": { "url": "https://axiom.co/.well-known/security.txt", "state": "valid", "expires": "2027-04-01T00:01:00Z", "checkedAt": "2026-11-04T15:54:16.073085585Z" }, "updatedAt": "2026-11-04T21:39:14.263725519Z" } }, "answer": "Axiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories.", "b": { "slug": "honeycomb-mcp", "name": "Honeycomb MCP", "vendor": "Honeycomb", "vendorUrl": "https://www.honeycomb.io", "kind": "mcp", "category": "observability", "summary": "Honeycomb's hosted MCP server lets AI agents query a team's traces, metrics and events, run BubbleUp analysis, and create or update Boards, Triggers and SLOs. It uses OAuth or a Management API key and has US and EU endpoints.", "url": "https://www.anchorterminal.com/tools/honeycomb-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json", "dns": "honeycomb-mcp.grade.anchorterminal.com", "repo": "https://github.com/honeycombio/agent-skill", "license": "Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.honeycomb.io/mcp", "packages": [], "auth": "mixed", "authNotes": "OAuth is the documented default. The server at https://mcp.honeycomb.io/mcp points clients to its protected-resource metadata, and ui.honeycomb.io is the authorisation server, with PKCE S256 and dynamic client registration. On the consent screen the owner chooses read all, read and write all, or read or write per resource (Boards, Triggers, SLOs, recipients, Service Maps, Anomaly Signals, Canvas investigations), and every connection also gets `environments:read` and `queries:read`. Connections authorised earlier keep `mcp:read` or `mcp:write`. Unattended agents can send a Management API key as `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e`, with Read or Write under Model Context Protocol and access under Environments. Only a Team Owner can create that key, and its scopes can't be changed later. Access is self-serve, but a Team Owner must first enable Honeycomb Intelligence for the team.", "pricing": "byo-plan", "pricingNotes": "No separate charge. Honeycomb MCP is in the feature list of every plan, the Free plan included (20 million events and 100 million metric data points a month). Pro starts at $150 a month for 50 million events and Enterprise is quoted. The signup page asks for an email address or a Google account, and the signup guide names no payment step, so an agent's owner can start without a contract (https://www.honeycomb.io/pricing, checked 2026-10-09).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, the pricing page or the terms (checked 2026-10-09).", "endpoints": [] }, "toolCount": 36, "popularity": { "githubStars": 27, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.honeycomb.io/integrations/mcp/", "llmsTxt": "https://docs.honeycomb.io/llms.txt", "registryName": "io.honeycomb/mcp", "capabilities": [ "observability.traces", "observability.metrics", "observability.logs" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "toolsets", "free-tier", "eu-region", "llms-txt", "mcp-registry", "status-page", "soc2" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 60.7, "grade": "C", "agentReady": false, "rank": 579, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 81, "payments": 30, "reliability": 70, "schema": 57, "security": 68, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OAuth with PKCE, dynamic client registration and per-resource scopes, such as `boards:read` or `triggers:write`, chosen on the consent screen", "Per-tool rate limits are published, from 10 calls a minute for `get_service_map` to 300 for semantic-convention lookups", "Listed in the official MCP registry as `io.honeycomb/mcp` 1.0.0, under the vendor's own domain namespace", "Included in the Free plan (20 million events a month), with separate US and EU endpoints", "The Activity Log records OAuth sessions with granted scopes and each query run with its source, MCP included" ], "weaknesses": [ "Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters", "No guidance on prompt injection was found, although trace and log content returned to the agent is untrusted text", "The status page has no MCP component. US1 queries over older data failed for 67 minutes on 10 August 2026", "No SLA was found, and the AI terms allow Honeycomb to change or end any part of Honeycomb Intelligence at any time", "A Team Owner must enable Honeycomb Intelligence first, and API key scopes can't be changed after creation" ], "agentNotes": [ "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", "If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings", "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", "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`", "For unattended runs send `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e` from a Management key with only Model Context Protocol and Environments scopes" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.7 } ], "editorialScores": { "ergonomics": 53, "maintenance": 81, "payments": 30, "reliability": 70, "schema": 57, "security": 68, "transparency": 64 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add honeycomb --transport http https://mcp.honeycomb.io/mcp", "config": { "mcpServers": { "honeycomb": { "url": "https://mcp.honeycomb.io/mcp" } } }, "headless": { "mcpServers": { "honeycomb": { "args": [ "-y", "mcp-remote", "https://mcp.honeycomb.io/mcp", "--header", "Authorization: Bearer $HONEYCOMB_API_KEY" ], "command": "npx", "env": { "HONEYCOMB_API_KEY": "\u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e" } } } } }, "letme": { "capability": "https://letme.dev/observability.traces", "tool": "https://letme.dev/honeycomb-mcp" }, "area": "developer", "unitPrices": [ { "item": "Pro plan, 50 million events", "unit": "month", "usd": 150, "note": "Starting price. MCP is also in the Free plan at no charge" } ], "provenance": { "legalEntity": "Hound Technology, Inc. d/b/a Honeycomb", "domain": "honeycomb.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.honeycomb.io/terms", "privacy": "https://www.honeycomb.io/privacy", "statusPage": "https://status.honeycomb.io", "changelog": "https://changelog.honeycomb.io/", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service (effective 22 May 2025) name Hound Technology, Inc. d/b/a Honeycomb, are governed by California law, and incorporate the Honeycomb Intelligence Supplemental Terms at honeycomb.io/ai-terms and the Data Processing Addendum at honeycomb.io/dpa.", "The Privacy Notice (last updated 24 July 2025) covers the website and the services, and says it does not apply to content customers submit under a customer account. The DPA (last updated 22 May 2025) governs that content.", "The MCP server answers at mcp.honeycomb.io and mcp.eu1.honeycomb.io, and the OAuth server at ui.honeycomb.io, all honeycomb.io subdomains.", "www.honeycomb.io/.well-known/security.txt and /security.txt return 404. Reports go to security@honeycomb.io under a bug bounty programme whose stated scope is ui.honeycomb.io and api.honeycomb.io.", "changelog.honeycomb.io and api-changelog.honeycomb.io disallow every path to unnamed crawlers in robots.txt, so neither was read.", "The .io registry has no RDAP service that answered, so the domain's registration date is not recorded." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/honeycomb-mcp.json", "live": { "slug": "honeycomb-mcp", "probe": { "target": "https://mcp.honeycomb.io/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T21:39:27.724488683Z", "lastOk": true, "lastStatus": 401, "lastMs": 336, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 387, "p95ms24h": 472, "samples24h": 247, "samples30d": 6653, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 223, "ok": 223 } ] }, "vendorStatus": { "page": "https://status.honeycomb.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:38:19.832596024Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.honeycomb/mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "githubStars": 28, "securityTxt": { "url": "https://honeycomb.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:49.534670121Z" }, "llmsTxt": { "url": "https://docs.honeycomb.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:23:11.617931168Z" }, "domain": { "domain": "honeycomb.io", "checkedAt": "2026-11-01T14:12:37.895563706Z" }, "pages": [ { "url": "https://changelog.honeycomb.io/", "kind": "changelog", "status": 0, "checkedAt": "2026-11-04T08:16:22.238769817Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true }, { "url": "https://www.honeycomb.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:41:02.167425031Z", "changedAt": "2026-11-03T08:06:55.29202553Z", "fingerprint": "cc55e59dbc8d" }, { "url": "https://www.honeycomb.io/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:41:04.630185931Z", "changedAt": "2026-11-03T08:06:57.784332085Z", "fingerprint": "51602bc012d0" }, { "url": "https://www.honeycomb.io/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:41:06.760623981Z", "changedAt": "2026-11-03T08:07:00.196017318Z", "fingerprint": "b691d7c4af5c" } ], "mcpTools": { "url": "https://mcp.honeycomb.io/mcp", "checkedAt": "2026-11-04T01:22:47.870034582Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:43.761722159Z" }, "github": { "repo": "honeycombio/agent-skill", "checkedAt": "2026-11-02T08:54:48.0222443Z", "stars": 28, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-09T22:47:47Z", "openIssues": 3, "openPRs": 1, "issuesOpened90d": 1, "issuesClosed90d": 1, "prsMerged90d": 4, "ci": { "branch": "main", "runs": 50, "success": 43, "failure": 7, "other": 0, "latest": "success", "latestAt": "2026-10-09T22:48:09Z" }, "replies": { "sampled": 9, "unanswered": 3, "medianDays": 3.7 } }, "updatedAt": "2026-11-04T21:39:27.724488683Z" } }, "edges": [ { "by": 30, "category": "payments", "leads": "axiom", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 60, "b": 30 } }, { "by": 10, "category": "ergonomics", "leads": "axiom", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 63, "b": 53 } }, { "by": 5, "category": "schema", "leads": "axiom", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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)." }, "scores": { "a": 62, "b": 57 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Axiom, Inc.", "b": "Honeycomb", "name": "Vendor" }, { "a": "https://mcp.axiom.co/mcp", "b": "https://mcp.honeycomb.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT", "name": "Licence" }, { "a": "31", "b": "36", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "co.axiom/mcp", "b": "io.honeycomb/mcp", "name": "MCP registry" }, { "a": "2026-10-29", "b": "2026-10-09", "name": "Last release" }, { "a": "no date given", "b": "2025-05-22", "name": "Terms last updated" }, { "a": "no date given", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "27 stars", "name": "Popularity" } ], "faq": [ { "answer": "Axiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Axiom MCP Server or Honeycomb MCP?" }, { "answer": "Axiom MCP Server uses an OAuth sign-in. Honeycomb MCP takes an API key or an OAuth sign-in.", "question": "Do Axiom MCP Server and Honeycomb MCP need an API key?" }, { "answer": "Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Honeycomb MCP at https://mcp.honeycomb.io/mcp.", "question": "Can an agent call Axiom MCP Server and Honeycomb MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 62 against 57", "Agent ergonomics, 63 against 53", "Payments \u0026 pricing, 60 against 30" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.", "slug": "axiom", "watchFor": "The server is closed source and tool input schemas are only visible through an authenticated session" }, { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "honeycomb-mcp", "watchFor": "Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters" } ], "history": { "axiom": null, "honeycomb-mcp": [ { "causes": [ "product", "correction" ], "date": "2026-11-04", "delta": 2.2, "from": 58.5, "fromGrade": "C", "to": 60.7, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 58.3, "fromGrade": "C", "to": 58.5, "toGrade": "C" } ] }, "job": { "capability": "observability.logs", "name": "Observability logs" }, "others": [ { "json": "https://www.anchorterminal.com/compare/axiom-vs-incident-io.json", "title": "Axiom MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/axiom-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.json", "title": "Axiom MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.json", "title": "Axiom MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-better-stack.json", "title": "Axiom MCP Server vs Better Stack", "url": "https://www.anchorterminal.com/compare/axiom-vs-better-stack" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-causely.json", "title": "Axiom MCP Server vs Causely MCP server", "url": "https://www.anchorterminal.com/compare/axiom-vs-causely" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.json", "title": "Axiom MCP Server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.json", "title": "Axiom MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.json", "title": "Axiom MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.json", "title": "Better Stack vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp.json", "title": "Causely MCP server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.json", "title": "Datadog MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.json", "title": "Grafana MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.json", "title": "Axiom MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.json", "title": "Honeycomb MCP vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.json", "title": "Honeycomb MCP vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic" } ], "panel": null, "scores": [ { "axiom": 72, "by": 2, "edge": "axiom", "honeycomb-mcp": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "axiom": 62, "by": 5, "edge": "axiom", "honeycomb-mcp": 57, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "axiom": 63, "by": 10, "edge": "axiom", "honeycomb-mcp": 53, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "axiom": 72, "by": 4, "edge": "axiom", "honeycomb-mcp": 68, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "axiom": 60, "by": 30, "edge": "axiom", "honeycomb-mcp": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "axiom": 83, "by": 2, "edge": "axiom", "honeycomb-mcp": 81, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "axiom": 70, "by": 0, "edge": "", "honeycomb-mcp": 70, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Axiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories. Both do observability logs.", "tasks": null, "tutorials": [], "verdicts": { "axiom": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp", "json": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.min.md" }, "markdown": "Axiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories. Both do observability logs.\n\n- Axiom MCP Server: grade B, 68.2/100, rank #269 of 1349. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.json\n- 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\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Axiom MCP Server (B)\n\nGood for: Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person.\n\nAhead on:\n- Schema \u0026 documentation, 62 against 57\n- Agent ergonomics, 63 against 53\n- Payments \u0026 pricing, 60 against 30\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The server is closed source and tool input schemas are only visible through an authenticated session\n\n### Honeycomb MCP (C)\n\nGood 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.\n\nWatch for: Tool input schemas and annotations are visible only through `tools/list` after sign-in. The public reference gives descriptions, not parameters\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Axiom MCP Server +30\n\n- 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.\n- 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).\n\n### Agent ergonomics: Axiom MCP Server +10\n\n- 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.\n- 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).\n\n### Schema \u0026 documentation: Axiom MCP Server +5\n\n- 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.\n- 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).\n\n## Score by category\n\n| Category | Weight | Axiom MCP Server | Honeycomb MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 70 | Axiom MCP Server +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 57 | Axiom MCP Server +5 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 53 | Axiom MCP Server +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 68 | Axiom MCP Server +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 30 | Axiom MCP Server +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 81 | Axiom MCP Server +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 70 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.2 · B** | **60.7 · C** | |\n\n## Facts side by side\n\n| Fact | Axiom MCP Server | Honeycomb MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Axiom, Inc. | Honeycomb |\n| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.honeycomb.io/mcp` |\n| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service under Honeycomb's Terms of Service and Honeycomb Intelligence Supplemental Terms. The companion plugin in honeycombio/agent-skill is MIT |\n| Tools exposed | 31 | 36 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `co.axiom/mcp` | `io.honeycomb/mcp` |\n| Last release | 2026-10-29 | 2026-10-09 |\n| Terms last updated | no date given | 2025-05-22 |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 27 stars |\n\n## How the scores have moved\n\n### Axiom MCP Server\n\nNo score change since it was listed.\n\n### Honeycomb MCP\n\n- +2.2 on 4 November 2026: product, correction\n- +0.2 on 27 October 2026: checklist\n\n## Verdicts\n\n**Axiom MCP Server.** An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.\n\n**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.\n\n## Before you call either\n\n### Axiom MCP Server\n\n1. With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed\n2. Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL\n3. Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner\n4. Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first\n5. `deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting\n\n### Honeycomb MCP\n\n1. 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\n2. If no tools appear after sign-in, ask a Team Owner to enable Honeycomb Intelligence in team settings\n3. 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\n4. 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`\n5. For unattended runs send `Authorization: Bearer \u003cKEY_ID\u003e:\u003cSECRET_KEY\u003e` from a Management key with only Model Context Protocol and Environments scopes\n\n## Questions\n\n### Which is better for AI agents, Axiom MCP Server or Honeycomb MCP?\n\nAxiom MCP Server scores 68.2 (B) on agent readiness against Honeycomb MCP's 60.7 (C), and leads in 6 of 7 scored categories.\n\n### Do Axiom MCP Server and Honeycomb MCP need an API key?\n\nAxiom MCP Server uses an OAuth sign-in. Honeycomb MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Axiom MCP Server and Honeycomb MCP without installing anything?\n\nYes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Honeycomb MCP at https://mcp.honeycomb.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"axiom\", \"b\": \"honeycomb-mcp\"}`. From a terminal: `anchor compare axiom honeycomb-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/axiom.json and https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json\n\n## Other comparisons with Axiom MCP Server or Honeycomb MCP\n\n- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md)\n- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md)\n- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)\n- [Axiom MCP Server vs Causely MCP server](https://www.anchorterminal.com/compare/axiom-vs-causely.md)\n- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)\n- [Axiom MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs Honeycomb MCP](https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.md)\n- [Causely MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/causely-vs-honeycomb-mcp.md)\n- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)\n- [Grafana MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-honeycomb-mcp.md)\n- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md)\n- [Honeycomb MCP vs Sentry MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-sentry-mcp.md)\n- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Axiom MCP Server vs Honeycomb MCP", "url": "" } ], "description": "Axiom scores 68.2 (B) to Honeycomb MCP's 60.7 (C) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Axiom MCP Server B 68.2", "Honeycomb MCP C 60.7", "scores" ], "h1": "Axiom MCP Server vs Honeycomb MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/axiom-vs-honeycomb-mcp", "published": "2026-10-01", "section": "tools", "title": "Axiom vs Honeycomb MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp" }, "tokens": { "markdown": 3550, "slim": 1780 }, "version": 1 }