{ "data": { "a": { "slug": "cronitor-mcp", "name": "Cronitor MCP server", "vendor": "Cronitor", "vendorUrl": "https://cronitor.io", "kind": "mcp", "category": "observability", "summary": "Cronitor's hosted MCP server lets an agent create and manage cron job, heartbeat and uptime monitors, issues, status pages, alert integrations and metrics in a Cronitor account, over OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/cronitor-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json", "dns": "cronitor-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://cronitor.io/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth through protected-resource metadata, with sign-in and consent in a browser; the token carries the user's role, capped at the SDK Integration key's permissions, with no scope selection. An API key in a header works for headless clients, with the key's granular read or write scopes.", "pricing": "freemium", "pricingNotes": "Free forever for 5 monitors. Business is $2 a monitor and $5 a user a month after a 14-day trial (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 71, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://cronitor.io/docs/mcp-server", "llmsTxt": "https://cronitor.io/llms.txt", "registryName": "io.cronitor/cronitor", "capabilities": [ "observability.incidents", "observability.metrics", "events.schedule", "agent.tools" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "api-key", "freemium", "free-tier", "status-page", "llms-txt", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 59.1, "grade": "C", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.", "bestFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "strengths": [ "Strict input schemas (additionalProperties false) with enums and required combinations", "Summary modes with paging keep list output small", "JSON-RPC error codes with retry_after_seconds and required_scope", "Clear guidance on secrets in event messages and output", "Free plan for 5 monitors" ], "weaknesses": [ "71 tools, a heavy context load", "No public changelog", "Terms and privacy closed to crawlers, so unread", "No audit log of agent calls found" ], "agentNotes": [ "Start with list_monitors and list_issues in summary mode", "Ask the user before expanding event messages, command output or request bodies", "On a rate-limit error, wait retry_after_seconds", "Over the plan's monitor limit, new monitors are saved but disabled" ], "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": 59.1 } ], "editorialScores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 25 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add cronitor --transport http https://cronitor.io/mcp", "config": { "mcpServers": { "cronitor": { "url": "https://cronitor.io/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/cronitor-mcp" }, "area": "developer", "provenance": { "legalEntity": "Cronitor", "domain": "cronitor.io", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.cronitor.io", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "robots.txt disallows the terms and privacy pages, so the legal entity wasn't read.", "security.txt answered 404." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.json", "live": { "slug": "cronitor-mcp", "probe": { "target": "https://cronitor.io/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T01:01:26.14186466Z", "lastOk": true, "lastStatus": 401, "lastMs": 584, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 627, "p95ms24h": 717, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.cronitor.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:31:11.053343459Z" }, "updatedAt": "2026-11-08T01:01:26.14186466Z" } }, "answer": "Honeycomb MCP scores 60.7 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "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": 644, "ranked": true, "rankOf": 1510, "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-08T00:55:44.59824732Z", "lastOk": true, "lastStatus": 401, "lastMs": 389, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 376, "p95ms24h": 479, "samples24h": 244, "samples30d": 7355, "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": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.honeycomb.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:54:51.739678412Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.honeycomb/mcp", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 28, "securityTxt": { "url": "https://honeycomb.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:22.150171087Z" }, "llmsTxt": { "url": "https://docs.honeycomb.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:42.260774497Z" }, "domain": { "domain": "honeycomb.io", "checkedAt": "2026-11-01T14:12:37.895563706Z" }, "pages": [ { "url": "https://changelog.honeycomb.io/", "kind": "changelog", "status": 0, "checkedAt": "2026-11-07T14:00:56.511833691Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true }, { "url": "https://www.honeycomb.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:29:48.745555769Z", "changedAt": "2026-11-07T14:29:48.745555769Z", "fingerprint": "b26a491912ad" }, { "url": "https://www.honeycomb.io/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:51.32320893Z", "changedAt": "2026-11-07T14:29:51.32320893Z", "fingerprint": "572d8853b2d8" }, { "url": "https://www.honeycomb.io/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:53.650946574Z", "changedAt": "2026-11-07T14:29:53.650946574Z", "fingerprint": "3a8edadefa1b" } ], "mcpTools": { "url": "https://mcp.honeycomb.io/mcp", "checkedAt": "2026-11-07T01:45:19.833429454Z", "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-08T00:55:44.59824732Z" } }, "edges": [ { "by": 33, "category": "transparency", "leads": "honeycomb-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.", "b": "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)." }, "scores": { "a": 37, "b": 70 } }, { "by": 26, "category": "maintenance", "leads": "honeycomb-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.", "b": "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)." }, "scores": { "a": 55, "b": 81 } }, { "by": 23, "category": "schema", "leads": "cronitor-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.", "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": 80, "b": 57 } }, { "by": 20, "category": "ergonomics", "leads": "cronitor-mcp", "name": "Agent ergonomics", "reasons": { "a": "71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73.", "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": 73, "b": 53 } }, { "by": 15, "category": "reliability", "leads": "honeycomb-mcp", "name": "Reliability", "reasons": { "a": "Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.", "b": "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." }, "scores": { "a": 55, "b": 70 } }, { "by": 10, "category": "security", "leads": "honeycomb-mcp", "name": "Security \u0026 auth", "reasons": { "a": "OAuth bounded by role with no scope choice, or scoped API keys (22 of 30). Read-only users get only read tools; write tools follow the role (14 of 20). The docs warn that event messages, command output and request bodies can hold customer data or secrets, and tell the agent to ask before expanding them; secrets are redacted (12 of 15). No audit log of MCP calls found (0). The security page covers encryption and relies on AWS's certifications; no security.txt (404) and no disclosure policy found (10 of 20). 22 + 14 + 12 + 0 + 10 = 58.", "b": "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)." }, "scores": { "a": 58, "b": 68 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Cronitor", "b": "Honeycomb", "name": "Vendor" }, { "a": "https://cronitor.io/mcp", "b": "https://mcp.honeycomb.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "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": "71", "b": "36", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.cronitor/cronitor", "b": "io.honeycomb/mcp", "name": "MCP registry" }, { "a": "none", "b": "2026-10-09", "name": "Last release" }, { "a": "no document linked", "b": "2025-05-22", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "27 stars", "name": "Popularity" } ], "faq": [ { "answer": "Honeycomb MCP scores 60.7 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Cronitor MCP server or Honeycomb MCP?" }, { "answer": "Cronitor MCP server uses an OAuth sign-in. Honeycomb MCP takes an API key or an OAuth sign-in.", "question": "Do Cronitor MCP server and Honeycomb MCP need an API key?" }, { "answer": "Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and Honeycomb MCP at https://mcp.honeycomb.io/mcp.", "question": "Can an agent call Cronitor MCP server and Honeycomb MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 80 against 57", "Agent ergonomics, 73 against 53", "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "slug": "cronitor-mcp", "watchFor": "71 tools, a heavy context load" }, { "aheadOn": [ "Reliability, 70 against 55", "Security \u0026 auth, 68 against 58", "Maintenance \u0026 community, 81 against 55", "Transparency \u0026 trust, 70 against 37" ], "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": { "cronitor-mcp": 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.metrics", "name": "Metrics and monitoring" }, "others": [ { "json": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.json", "title": "Axiom MCP Server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.json", "title": "Better Stack vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.json", "title": "Causely MCP server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json", "title": "Cronitor MCP server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.json", "title": "Cronitor MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json", "title": "Cronitor MCP server vs incident.io API", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json", "title": "Cronitor MCP server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.json", "title": "Cronitor MCP server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json", "title": "Cronitor MCP server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json", "title": "Axiom MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp" }, { "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/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": [ { "by": 15, "cronitor-mcp": 55, "edge": "honeycomb-mcp", "honeycomb-mcp": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 23, "cronitor-mcp": 80, "edge": "cronitor-mcp", "honeycomb-mcp": 57, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 20, "cronitor-mcp": 73, "edge": "cronitor-mcp", "honeycomb-mcp": 53, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 10, "cronitor-mcp": 58, "edge": "honeycomb-mcp", "honeycomb-mcp": 68, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "cronitor-mcp": 40, "edge": "cronitor-mcp", "honeycomb-mcp": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "cronitor-mcp": 55, "edge": "honeycomb-mcp", "honeycomb-mcp": 81, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 33, "cronitor-mcp": 37, "edge": "honeycomb-mcp", "honeycomb-mcp": 70, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Honeycomb MCP scores 60.7 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do metrics and monitoring.", "tasks": null, "tutorials": [], "verdicts": { "cronitor-mcp": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.", "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/cronitor-mcp-vs-honeycomb-mcp", "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.min.md" }, "markdown": "Honeycomb MCP scores 60.7 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do metrics and monitoring.\n\n- Cronitor MCP server: grade C, 59.1/100, rank #718 of 1510. Markdown https://www.anchorterminal.com/tools/cronitor-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json\n- Honeycomb MCP: grade C, 60.7/100, rank #644 of 1510. 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 59 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Cronitor MCP server (C)\n\nGood for: Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.\n\nAhead on:\n- Schema \u0026 documentation, 80 against 57\n- Agent ergonomics, 73 against 53\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: 71 tools, a heavy context load\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\nAhead on:\n- Reliability, 70 against 55\n- Security \u0026 auth, 68 against 58\n- Maintenance \u0026 community, 81 against 55\n- Transparency \u0026 trust, 70 against 37\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### Transparency \u0026 trust: Honeycomb MCP +33\n\n- Cronitor MCP server (37): robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.\n- 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).\n\n### Maintenance \u0026 community: Honeycomb MCP +26\n\n- Cronitor MCP server (55): Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.\n- 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).\n\n### Schema \u0026 documentation: Cronitor MCP server +23\n\n- Cronitor MCP server (80): Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.\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### Agent ergonomics: Cronitor MCP server +20\n\n- Cronitor MCP server (73): 71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73.\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### Reliability: Honeycomb MCP +15\n\n- Cronitor MCP server (55): Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.\n- 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.\n\n### Security \u0026 auth: Honeycomb MCP +10\n\n- Cronitor MCP server (58): OAuth bounded by role with no scope choice, or scoped API keys (22 of 30). Read-only users get only read tools; write tools follow the role (14 of 20). The docs warn that event messages, command output and request bodies can hold customer data or secrets, and tell the agent to ask before expanding them; secrets are redacted (12 of 15). No audit log of MCP calls found (0). The security page covers encryption and relies on AWS's certifications; no security.txt (404) and no disclosure policy found (10 of 20). 22 + 14 + 12 + 0 + 10 = 58.\n- 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).\n\n## Score by category\n\n| Category | Weight | Cronitor MCP server | Honeycomb MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 70 | Honeycomb MCP +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 57 | Cronitor MCP server +23 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 53 | Cronitor MCP server +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 68 | Honeycomb MCP +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Cronitor MCP server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 55 | 81 | Honeycomb MCP +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 70 | Honeycomb MCP +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.1 · C** | **60.7 · C** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | Honeycomb MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Cronitor | Honeycomb |\n| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.honeycomb.io/mcp` |\n| Transports | Streamable HTTP | 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 | 71 | 36 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.cronitor/cronitor` | `io.honeycomb/mcp` |\n| Last release | none | 2026-10-09 |\n| Terms last updated | no document linked | 2025-05-22 |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 27 stars |\n\n## How the scores have moved\n\n### Cronitor 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**Cronitor MCP server.** Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.\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### Cronitor MCP server\n\n1. Start with list_monitors and list_issues in summary mode\n2. Ask the user before expanding event messages, command output or request bodies\n3. On a rate-limit error, wait retry_after_seconds\n4. Over the plan's monitor limit, new monitors are saved but disabled\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, Cronitor MCP server or Honeycomb MCP?\n\nHoneycomb MCP scores 60.7 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.\n\n### Do Cronitor MCP server and Honeycomb MCP need an API key?\n\nCronitor MCP server uses an OAuth sign-in. Honeycomb MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Cronitor MCP server and Honeycomb MCP without installing anything?\n\nYes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/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/cronitor-mcp-vs-honeycomb-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cronitor-mcp\", \"b\": \"honeycomb-mcp\"}`. From a terminal: `anchor compare cronitor-mcp honeycomb-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/honeycomb-mcp.json\n\n## Other comparisons with Cronitor MCP server or Honeycomb MCP\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)\n- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)\n- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md)\n- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)\n- [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md)\n- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.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- [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-08", "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": "Cronitor MCP server vs Honeycomb MCP", "url": "" } ], "description": "Honeycomb MCP scores 60.7 (C) to Cronitor's 59.1 (C) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cronitor MCP server C 59.1", "Honeycomb MCP C 60.7", "scores" ], "h1": "Cronitor MCP server vs Honeycomb MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cronitor-mcp-vs-honeycomb-mcp", "published": "2026-10-01", "section": "tools", "title": "Cronitor vs Honeycomb MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp" }, "tokens": { "markdown": 4950, "slim": 3280 }, "version": 1 }