Axiom MCP Server vs Datadog MCP Server

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.

Datadog MCP Server 20

No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check.

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.

Datadog MCP Server 33

Scored as a hosted MCP server. status.datadoghq.com now answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of its front page (components with no MCP component, three late-September incidents in other products) is struck. Datadog's Acceptable Use Policy also bars robots from its sites, so nothing more was requested. With no component reading left, the status-page line is 0, and the 90-day incident history is unread (5). The changelog publishes a burst limit of 50 calls per 10 seconds and a monthly quota of 100,000 tool calls per organisation, doubled from 50,000 on 28 August (15). Read-only software-delivery calls are retried on transient failures and get_datadog_k8s_manifest explains what to do when rate limited, but no Retry-After or backoff guidance for MCP clients was found. The 5 is kept from 1 October as a partly met line (5). No SLA found (0). GA since 9 March 2026 on the stable /v1 URL since 20 July, with some toolsets still experimental, kept at 8 as partly met (8). 0+5+15+5+0+8 = 33.

Axiom MCP Server 63

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

Datadog MCP Server 78

More than 30 toolsets chosen with the toolsets parameter, omit_tools per the 30 September check, whoami and toolsets resources, and a core set trimmed by about 15 per cent in March. An execute_code toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). limit, cursors, custom_attributes, token budgets and flattening on aggregates, and exclude_fields on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says execute_code is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).

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.

Datadog MCP Server 68

Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.