{
  "data": {
    "a": {
      "slug": "axiom",
      "name": "Axiom MCP Server",
      "vendor": "Axiom, Inc.",
      "vendorUrl": "https://axiom.co",
      "company": "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": 72,
        "grade": "BB",
        "agentReady": true,
        "rank": 239,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 2,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 63,
          "maintenance": 83,
          "payments": 90,
          "reliability": 72,
          "schema": 62,
          "security": 72,
          "transparency": 70
        },
        "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": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 72
          }
        ],
        "editorialScores": {
          "ergonomics": 63,
          "maintenance": 83,
          "payments": 90,
          "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",
          "lastMoved": "2026-11-13",
          "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-18T23:13:09.60626588Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 150,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 61,
          "p95ms24h": 240,
          "samples24h": 241,
          "samples30d": 3418,
          "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": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 233,
              "ok": 233
            }
          ],
          "since": "2026-11-04T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.axiom.co",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:12:30.227352939Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "co.axiom/mcp",
            "version": "1.0.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "securityTxt": {
          "url": "https://axiom.co/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-04-01T00:01:00Z",
          "checkedAt": "2026-11-18T16:31:06.253808627Z"
        },
        "llmsTxt": {
          "url": "https://axiom.co/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:13:28.694032292Z"
        },
        "domain": {
          "domain": "axiom.co",
          "checkedAt": "2026-11-15T15:22:34.715356337Z"
        },
        "pages": [
          {
            "url": "https://axiom.co/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:33.971517709Z",
            "changedAt": "2026-11-17T20:52:37.261374515Z",
            "fingerprint": "0f5d72fcf5d5"
          },
          {
            "url": "https://axiom.co/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:40.464804308Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "66349829a205"
          },
          {
            "url": "https://axiom.co/docs/legal/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:37.833021971Z",
            "changedAt": "2026-11-18T21:33:37.833021971Z",
            "fingerprint": "1e63bfd424a8"
          },
          {
            "url": "https://axiom.co/docs/legal/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:33:38.710722861Z",
            "changedAt": "2026-11-16T20:13:12.107368337Z",
            "fingerprint": "fd8039d62442"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.axiom.co/mcp",
          "checkedAt": "2026-11-18T04:21:47.787413323Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-05T01:28:59.877690188Z"
        },
        "updatedAt": "2026-11-18T23:13:09.60626588Z"
      },
      "streak": {
        "days": 14,
        "from": "2026-11-04",
        "sinceWatching": true,
        "best": 14
      }
    },
    "answer": "Axiom MCP Server scores 72 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
    "b": {
      "slug": "neat-pulse-mcp",
      "name": "Neat Pulse MCP",
      "vendor": "Neat",
      "vendorUrl": "https://neat.no",
      "company": "neat.no",
      "kind": "mcp",
      "category": "observability",
      "summary": "Neat Pulse MCP is Neat's local MCP server for Neat Pulse, the cloud service that manages Neat's meeting-room video devices. Agents list devices and rooms, read sensor data, reboot devices and change room set-up, for paid Pulse customers.",
      "url": "https://www.anchorterminal.com/tools/neat-pulse-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json",
      "dns": "neat-pulse-mcp.grade.anchorterminal.com",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@neat-no/pulse-mcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "A Neat Pulse API token in `PULSE_API_TOKEN`, with the organisation ID in `PULSE_ORG_ID`. Only an Owner of the Pulse organisation can create tokens, in the portal under Settings \u003e API Keys. A token takes either the Read scope or all scopes, is shown once, can be revoked, and the Pulse API has a key-rotation endpoint. The token's name appears in Pulse's audit logs.",
      "pricing": "byo-plan",
      "pricingNotes": "Included at no extra cost with a paid Neat Pulse Plus or Pro plan, and every device in the organisation must be on a paid plan. Plus and Pro are sold through resellers, with no public price. The free Pulse Starter plan doesn't include MCP or API access.",
      "priceSummary": "Your plan",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on neat.no, support.neat.no or the Pulse API reference, read on 2026-11-18. Pulse plans are bought through resellers.",
        "endpoints": []
      },
      "toolCount": 30,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://support.neat.no/article/neat-pulse-mcp-server/",
      "capabilities": [
        "observability.metrics"
      ],
      "tags": [
        "mcp",
        "stdio",
        "npm",
        "node",
        "api-key",
        "audit-log",
        "read-only-mode",
        "hardware",
        "meeting-rooms",
        "paid-plan",
        "iso-27001"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 45.8,
        "grade": "E",
        "agentReady": false,
        "rank": 1268,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 56
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.",
        "bestFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "strengths": [
          "A Pulse API token can be limited to the Read scope, which the docs say stops the server rebooting, deleting, creating or updating anything",
          "Every action taken through the MCP server is recorded in Pulse's audit logs under the token's name, and `list_audit_logs` reads them",
          "security.txt, a vulnerability reporting policy, public security advisories through 2026 and an ISO 27001 statement on Neat's support site",
          "Version 1.1.0 on 17 November 2026, four releases since 17 September 2026, and setup steps for seven MCP clients",
          "A data model guide served as an MCP resource and a tool, with IDs, hierarchy and which actions can't be undone"
        ],
        "weaknesses": [
          "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent",
          "No public source repository, licence, changelog or status page found",
          "Irreversible tools (delete room, delete device, reboot, reset enrolment code) rely on the assistant asking first. No server-side confirmation was found",
          "No rate limits or 429 handling documented for the server or the Pulse API",
          "Runs only in clients that can start local programs, and needs Node.js 20 or later"
        ],
        "agentNotes": [
          "Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices",
          "Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room",
          "Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy",
          "If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`",
          "If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 45.8
          }
        ],
        "editorialScores": {
          "ergonomics": 43,
          "maintenance": 59,
          "payments": 0,
          "reliability": 35,
          "schema": 49,
          "security": 79,
          "transparency": 47
        },
        "provenanceScore": 65,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx -y @neat-no/pulse-mcp@latest   # needs PULSE_API_TOKEN and PULSE_ORG_ID in the environment",
        "claudeCode": "claude mcp add neat-pulse -s user -e PULSE_API_TOKEN=YOUR_PULSE_TOKEN -e PULSE_ORG_ID=YOUR_ORG_ID -- npx -y @neat-no/pulse-mcp@latest",
        "config": {
          "mcpServers": {
            "neat-pulse": {
              "args": [
                "-y",
                "@neat-no/pulse-mcp@latest"
              ],
              "command": "npx",
              "env": {
                "PULSE_API_TOKEN": "YOUR_PULSE_TOKEN",
                "PULSE_ORG_ID": "YOUR_ORG_ID"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.metrics",
        "tool": "https://letme.dev/neat-pulse-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Neatframe Limited",
        "domain": "neat.no",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://neat.no/neat-pulse-terms-and-conditions/",
        "privacy": "https://neat.no/privacy-policy/",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-11-18",
        "notes": [
          "The Neat Pulse Agreement (last updated 26 March 2025) is between Neatframe Ltd. and the customer, and the privacy notice (13 July 2026) is Neatframe Limited's. The company page says Neat is based in Oslo.",
          "neat.no/robots.txt allows ClaudeBot and anthropic-ai outside account, cart, checkout and admin paths, with a crawl delay of 10 seconds. support.neat.no, api.pulse.neat.no and registry.npmjs.org allow all agents.",
          "neat.no/.well-known/security.txt gives security@neat.no, expires 7 August 2027 and links the vulnerability reporting policy on support.neat.no.",
          "No status page for Neat Pulse was linked from any page read. The MCP server calls the Pulse API at api.pulse.neat.no."
        ],
        "score": 65
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/neat-pulse-mcp.json"
    },
    "edges": [
      {
        "by": 90,
        "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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.",
          "b": "No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0."
        },
        "scores": {
          "a": 90,
          "b": 0
        }
      },
      {
        "by": 37,
        "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": "Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35."
        },
        "scores": {
          "a": 72,
          "b": 35
        }
      },
      {
        "by": 24,
        "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": "1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59."
        },
        "scores": {
          "a": 83,
          "b": 59
        }
      },
      {
        "by": 20,
        "category": "ergonomics",
        "leads": "axiom",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.",
          "b": "30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43."
        },
        "scores": {
          "a": 63,
          "b": 43
        }
      },
      {
        "by": 14,
        "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": "Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47."
        },
        "scores": {
          "a": 70,
          "b": 56
        }
      },
      {
        "by": 13,
        "category": "schema",
        "leads": "axiom",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use `queryMetrics` for metrics datasets instead of `queryDataset`, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.",
          "b": "The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49."
        },
        "scores": {
          "a": 62,
          "b": 49
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Axiom, Inc.",
        "b": "Neat",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.axiom.co/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP, SSE (legacy)",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Your plan",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "31",
        "b": "30",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "co.axiom/mcp",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-29",
        "b": "2026-11-17",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "2025-03-26",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "2026-07-13",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Axiom MCP Server scores 72 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.",
        "question": "Which is better for AI agents, Axiom MCP Server or Neat Pulse MCP?"
      },
      {
        "answer": "Axiom MCP Server uses an OAuth sign-in. Neat Pulse MCP needs an API key.",
        "question": "Do Axiom MCP Server and Neat Pulse MCP need an API key?"
      },
      {
        "answer": "Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Axiom MCP Server and Neat Pulse MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 72 against 35",
          "Schema \u0026 documentation, 62 against 49",
          "Agent ergonomics, 63 against 43",
          "Payments \u0026 pricing, 90 against 0",
          "Maintenance \u0026 community, 83 against 59",
          "Transparency \u0026 trust, 70 against 56"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "A hosted endpoint, with nothing to install",
          "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": [
          "Security \u0026 auth, 79 against 72"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.",
        "slug": "neat-pulse-mcp",
        "watchFor": "Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent"
      }
    ],
    "history": {
      "axiom": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 3.8,
          "from": 68.2,
          "fromGrade": "B",
          "to": 72,
          "toGrade": "BB"
        }
      ],
      "neat-pulse-mcp": null
    },
    "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/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-neat-pulse-mcp.json",
        "title": "Better Stack vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.json",
        "title": "Causely MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json",
        "title": "Cronitor MCP server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.json",
        "title": "Datadog MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.json",
        "title": "Grafana MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.json",
        "title": "Honeycomb MCP vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.json",
        "title": "Neat Pulse MCP vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic"
      },
      {
        "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/neat-pulse-mcp-vs-sentry-mcp.json",
        "title": "Neat Pulse MCP vs Sentry MCP",
        "url": "https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-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": 37,
        "edge": "axiom",
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "axiom": 62,
        "by": 13,
        "edge": "axiom",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "weight": 13
      },
      {
        "axiom": 63,
        "by": 20,
        "edge": "axiom",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "weight": 13
      },
      {
        "axiom": 72,
        "by": 7,
        "edge": "neat-pulse-mcp",
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "weight": 14
      },
      {
        "axiom": 90,
        "by": 90,
        "edge": "axiom",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "axiom": 83,
        "by": 24,
        "edge": "axiom",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "weight": 7
      },
      {
        "axiom": 70,
        "by": 14,
        "edge": "axiom",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "weight": 7
      }
    ],
    "summary": "Axiom MCP Server scores 72 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth. Both do metrics and monitoring.",
    "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.",
      "neat-pulse-mcp": "Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp",
    "json": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.min.md"
  },
  "markdown": "Axiom MCP Server scores 72 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth. Both do metrics and monitoring.\n\n- Axiom MCP Server: grade BB, 72/100, rank #239 of 1557. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.json\n- Neat Pulse MCP: grade E, 45.8/100, rank #1268 of 1557. Markdown https://www.anchorterminal.com/tools/neat-pulse-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Axiom MCP Server (BB)\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 35\n- Schema \u0026 documentation, 62 against 49\n- Agent ergonomics, 63 against 43\n- Payments \u0026 pricing, 90 against 0\n- Maintenance \u0026 community, 83 against 59\n- Transparency \u0026 trust, 70 against 56\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\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### Neat Pulse MCP (E)\n\nGood for: IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.\n\nAhead on:\n- Security \u0026 auth, 79 against 72\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Needs a paid Pulse Plus or Pro plan bought through a reseller, with no public price, no trial for MCP and no self-serve route for an agent\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Axiom MCP Server +90\n\n- Axiom MCP Server (90): 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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.\n- Neat Pulse MCP (0): No payment protocol (0). Pulse Plus and Pro are sold through resellers and the Pulse Agreement says the price is on the reseller's invoice, so no price is public (0). The free Starter plan excludes MCP and API access (0). A person must buy a plan and an Owner must create the token in the portal (0). 0 + 0 + 0 + 0 = 0.\n\n### Reliability: Axiom MCP Server +37\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- Neat Pulse MCP (35): Read with the local-software lines, since the server is an npm package the client starts on the person's machine. Official npm package with Node.js 20 or later stated (20). No public repository, so no CI or test suite could be seen (0). No public issue tracker (0). Versions follow semver on npm, but no changelog was found (0). Version 1.1.0 and generally available since 18 November 2026 (15). The Pulse cloud API it relays to has no status page linked from the pages read. 20 + 0 + 0 + 0 + 15 = 35.\n\n### Maintenance \u0026 community: Axiom MCP Server +24\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- Neat Pulse MCP (59): 1.1.0 on 17 November 2026 (30). 0.2.2, 0.2.3, 1.0.0 and 1.1.0 since 17 September 2026 (20). Closed source with no public changelog. Paid plans include priority email support with an SLA per the Pulse Agreement, and the setup guide was updated on 17 November (5). Not in the official MCP registry, by a search for Neat (0). Current MCP SDK and zod versions in the npm metadata, with no visible CI (4). 30 + 20 + 5 + 0 + 4 = 59.\n\n### Agent ergonomics: Axiom MCP Server +20\n\n- Axiom MCP Server (63): 31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.\n- Neat Pulse MCP (43): 30 tools, in the 11 to 30 band, with no toolsets or read-only subset that hides write tools that we found (15). `list_audit_logs` pages between dates, but `list_devices` and `list_rooms` return everything in the organisation (6). Documented 401 and 404 causes, and `move_device` returns a status asking for confirmation instead of failing (10). Annotations couldn't be read. The docs ask the assistant to confirm reboots and messages, and no idempotency is described (5). Two environment variables to start. The Pulse API reference shows generated client snippets, but no official SDK package was found (7). 15 + 6 + 10 + 5 + 7 = 43.\n\n### Transparency \u0026 trust: Axiom MCP Server +14\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- Neat Pulse MCP (56): Closed source, and the npm package carries no licence field. The Pulse Agreement covers the service clearly (12). A privacy notice of 13 July 2026, a DPA, a GDPR page and a data residency article, with retention described only as long as necessary (18). The Pulse Agreement supports the current and prior major release, and nothing covers the MCP server's deprecation (3). Pulse data stays in one Azure region per chosen zone, mapped by name. No subprocessor list was read (14). 12 + 18 + 3 + 14 = 47.\n\n### Schema \u0026 documentation: Axiom MCP Server +13\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- Neat Pulse MCP (49): The npm metadata lists zod and the MCP SDK, but the tool schemas themselves weren't read, since the source isn't public and the package wasn't installed. Partial credit for a contract that exists but isn't published, as for Causely (12). No llms.txt found. The README points agents to an `llms-install.md` in the package, which wasn't read (5). The support reference describes every tool, what it returns and which changes can't be undone, and the domain guide explains the data model (14). Inputs are described only in passing, such as `assign_room_profile` (5). Example prompts, a troubleshooting table for 401, 404 and npx errors, and the `profile_confirmation_needed` status (8). Semver versions on npm and dated support articles, but no changelog (5). 12 + 5 + 14 + 5 + 8 + 5 = 49.\n\n## Score by category\n\n| Category | Weight | Axiom MCP Server | Neat Pulse MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 72 | 35 | Axiom MCP Server +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 62 | 49 | Axiom MCP Server +13 |\n| Agent ergonomics | 13% | 63 | 43 | Axiom MCP Server +20 |\n| Security \u0026 auth | 14% | 72 | 79 | Neat Pulse MCP +7 |\n| Payments \u0026 pricing | 10% | 90 | 0 | Axiom MCP Server +90 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 83 | 59 | Axiom MCP Server +24 |\n| Transparency \u0026 trust | 7% | 70 | 56 | Axiom MCP Server +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72 · BB** | **45.8 · E** | |\n\n## Facts side by side\n\n| Fact | Axiom MCP Server | Neat Pulse MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Axiom, Inc. | Neat |\n| Hosted endpoint | `https://mcp.axiom.co/mcp` | no (local only) |\n| Transports | Streamable HTTP, SSE (legacy) | stdio |\n| Auth | OAuth | API key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Tools exposed | 31 | 30 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | `co.axiom/mcp` | not listed |\n| Last release | 2026-10-29 | 2026-11-17 |\n| Terms last updated | no date given | 2025-03-26 |\n| Privacy policy last updated | no date given | 2026-07-13 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## How the scores have moved\n\n### Axiom MCP Server\n\n- +3.8 on 13 November 2026 (B to BB): checklist\n\n### Neat Pulse MCP\n\nNo score change since it was listed.\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**Neat Pulse MCP.** Agents get 30 documented tools for a Neat device fleet, behind a revocable Pulse API token that can be read-only, with every action written to Pulse's audit log. It needs a paid Pulse plan bought through a reseller, prices aren't public, and there is no public source, changelog or status page.\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### Neat Pulse MCP\n\n1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices\n2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room\n3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy\n4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`\n5. If a call returns 401, ask the person for a new Pulse token. If it returns 404, check `PULSE_ORG_ID`\n\n## Questions\n\n### Which is better for AI agents, Axiom MCP Server or Neat Pulse MCP?\n\nAxiom MCP Server scores 72 (BB) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 6 of 7 scored categories. Neat Pulse MCP leads on security \u0026 auth.\n\n### Do Axiom MCP Server and Neat Pulse MCP need an API key?\n\nAxiom MCP Server uses an OAuth sign-in. Neat Pulse MCP needs an API key.\n\n### Can an agent call Axiom MCP Server and Neat Pulse MCP without installing anything?\n\nAxiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"axiom\", \"b\": \"neat-pulse-mcp\"}`. From a terminal: `anchor compare axiom neat-pulse-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/axiom.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json\n\n## Other comparisons with Axiom MCP Server or Neat Pulse MCP\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)\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 Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)\n- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)\n- [Cronitor MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md)\n- [Datadog MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md)\n- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)\n- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)\n- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.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- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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 Neat Pulse MCP",
        "url": ""
      }
    ],
    "description": "Axiom scores 72 (BB) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Axiom MCP Server BB 72",
      "Neat Pulse MCP E 45.8",
      "scores"
    ],
    "h1": "Axiom MCP Server vs Neat Pulse MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/axiom-vs-neat-pulse-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Axiom vs Neat Pulse MCP for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp"
  },
  "tokens": {
    "markdown": 4650,
    "slim": 1030
  },
  "version": 1
}
