{ "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": 294, "ranked": true, "rankOf": 1510, "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-08T01:01:20.288165271Z", "lastOk": true, "lastStatus": 401, "lastMs": 43, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 53, "p95ms24h": 153, "samples24h": 244, "samples30d": 767, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "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": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.axiom.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:54:11.61161783Z" }, "versions": [ { "registry": "mcp-registry", "name": "co.axiom/mcp", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "securityTxt": { "url": "https://axiom.co/.well-known/security.txt", "state": "valid", "expires": "2027-04-01T00:01:00Z", "checkedAt": "2026-11-07T15:59:51.290401784Z" }, "llmsTxt": { "url": "https://axiom.co/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:40.181283252Z" }, "pages": [ { "url": "https://axiom.co/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T13:59:50.943364783Z", "changedAt": "2026-11-07T13:59:50.943364783Z", "fingerprint": "deeef5c9a467" }, { "url": "https://axiom.co/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T13:59:57.154897639Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "66349829a205" }, { "url": "https://axiom.co/docs/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T13:59:53.80957364Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "206045ccff71" }, { "url": "https://axiom.co/docs/legal/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T13:59:55.276425803Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "17f8065c72c8" } ], "mcpTools": { "url": "https://mcp.axiom.co/mcp", "checkedAt": "2026-11-07T01:42:33.424632095Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-05T01:28:59.877690188Z" }, "updatedAt": "2026-11-08T01:01:20.288165271Z" } }, "answer": "Axiom MCP Server scores 68.2 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 5 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation and agent ergonomics.", "b": { "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" } }, "edges": [ { "by": 33, "category": "transparency", "leads": "axiom", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.", "b": "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." }, "scores": { "a": 70, "b": 37 } }, { "by": 28, "category": "maintenance", "leads": "axiom", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.", "b": "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." }, "scores": { "a": 83, "b": 55 } }, { "by": 20, "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 machine payment protocol (0). Per-monitor and per-user prices public (20). Free plan for 5 monitors, no card mentioned (20). A person signs up or signs in through a browser (0). 0 + 20 + 20 + 0 = 40." }, "scores": { "a": 60, "b": 40 } }, { "by": 18, "category": "schema", "leads": "cronitor-mcp", "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": "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." }, "scores": { "a": 62, "b": 80 } }, { "by": 17, "category": "reliability", "leads": "axiom", "name": "Reliability", "reasons": { "a": "Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.", "b": "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." }, "scores": { "a": 72, "b": 55 } }, { "by": 14, "category": "security", "leads": "axiom", "name": "Security \u0026 auth", "reasons": { "a": "Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.", "b": "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." }, "scores": { "a": 72, "b": 58 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Axiom, Inc.", "b": "Cronitor", "name": "Vendor" }, { "a": "https://mcp.axiom.co/mcp", "b": "https://cronitor.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "31", "b": "71", "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.cronitor/cronitor", "name": "MCP registry" }, { "a": "2026-10-29", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "no date given", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Axiom MCP Server scores 68.2 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 5 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation and agent ergonomics.", "question": "Which is better for AI agents, Axiom MCP Server or Cronitor MCP server?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Axiom MCP Server and Cronitor MCP server need an API key?" }, { "answer": "Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Cronitor MCP server at https://cronitor.io/mcp.", "question": "Can an agent call Axiom MCP Server and Cronitor MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 55", "Security \u0026 auth, 72 against 58", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 83 against 55", "Transparency \u0026 trust, 70 against 37" ], "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": [ "Schema \u0026 documentation, 80 against 62", "Agent ergonomics, 73 against 63" ], "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" } ], "history": null, "job": { "capability": "observability.incidents", "name": "Incidents" }, "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/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-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-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/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/cronitor-mcp-vs-honeycomb-mcp.json", "title": "Cronitor MCP server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-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" } ], "panel": null, "scores": [ { "axiom": 72, "by": 17, "cronitor-mcp": 55, "edge": "axiom", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "axiom": 62, "by": 18, "cronitor-mcp": 80, "edge": "cronitor-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "axiom": 63, "by": 10, "cronitor-mcp": 73, "edge": "cronitor-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "axiom": 72, "by": 14, "cronitor-mcp": 58, "edge": "axiom", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "axiom": 60, "by": 20, "cronitor-mcp": 40, "edge": "axiom", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "axiom": 83, "by": 28, "cronitor-mcp": 55, "edge": "axiom", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "axiom": 70, "by": 33, "cronitor-mcp": 37, "edge": "axiom", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Axiom MCP Server scores 68.2 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 5 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation and agent ergonomics. Both do incidents.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp", "json": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.min.md" }, "markdown": "Axiom MCP Server scores 68.2 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 5 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation and agent ergonomics. Both do incidents.\n\n- Axiom MCP Server: grade B, 68.2/100, rank #294 of 1510. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.json\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- 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### 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- Reliability, 72 against 55\n- Security \u0026 auth, 72 against 58\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 83 against 55\n- Transparency \u0026 trust, 70 against 37\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### 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 62\n- Agent ergonomics, 73 against 63\n\nWatch for: 71 tools, a heavy context load\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Axiom MCP Server +33\n\n- Axiom MCP Server (70): Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.\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\n### Maintenance \u0026 community: Axiom MCP Server +28\n\n- Axiom MCP Server (83): Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.\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\n### Payments \u0026 pricing: Axiom MCP Server +20\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- Cronitor MCP server (40): No machine payment protocol (0). Per-monitor and per-user prices public (20). Free plan for 5 monitors, no card mentioned (20). A person signs up or signs in through a browser (0). 0 + 20 + 20 + 0 = 40.\n\n### Schema \u0026 documentation: Cronitor MCP server +18\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- 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\n### Reliability: Axiom MCP Server +17\n\n- Axiom MCP Server (72): Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.\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\n### Security \u0026 auth: Axiom MCP Server +14\n\n- Axiom MCP Server (72): Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.\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\n## Score by category\n\n| Category | Weight | Axiom MCP Server | Cronitor MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 55 | Axiom MCP Server +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 80 | Cronitor MCP server +18 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 73 | Cronitor MCP server +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 58 | Axiom MCP Server +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | Axiom MCP Server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 55 | Axiom MCP Server +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 37 | Axiom MCP Server +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.2 · B** | **59.1 · C** | |\n\n## Facts side by side\n\n| Fact | Axiom MCP Server | Cronitor MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Axiom, Inc. | Cronitor |\n| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://cronitor.io/mcp` |\n| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 31 | 71 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `co.axiom/mcp` | `io.cronitor/cronitor` |\n| Last release | 2026-10-29 | none |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | no date given | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\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**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## 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### 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## Questions\n\n### Which is better for AI agents, Axiom MCP Server or Cronitor MCP server?\n\nAxiom MCP Server scores 68.2 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 5 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation and agent ergonomics.\n\n### Do Axiom MCP Server and Cronitor MCP server need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Axiom MCP Server and Cronitor MCP server without installing anything?\n\nYes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and Cronitor MCP server at https://cronitor.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"axiom\", \"b\": \"cronitor-mcp\"}`. From a terminal: `anchor compare axiom cronitor-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/axiom.json and https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json\n\n## Other comparisons with Axiom MCP Server or Cronitor MCP server\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- [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 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 Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)\n- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.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": "Axiom MCP Server vs Cronitor MCP server", "url": "" } ], "description": "Axiom scores 68.2 (B) to Cronitor's 59.1 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Axiom MCP Server B 68.2", "Cronitor MCP server C 59.1", "scores" ], "h1": "Axiom MCP Server vs Cronitor MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/axiom-vs-cronitor-mcp", "published": "2026-10-01", "section": "tools", "title": "Axiom vs Cronitor for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp" }, "tokens": { "markdown": 4400, "slim": 2680 }, "version": 1 }