Head to head · Metrics and monitoring · October 2026 research run
Axiom MCP Server vs Neat Pulse MCP
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 & auth. Both do metrics and monitoring.
Best observability and incident tools for AI agents · All 68 observability comparisons
Which one, for what
Best 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.
Ahead on
- Reliability, 72 against 35
- Schema & documentation, 62 against 49
- Agent ergonomics, 63 against 43
- Payments & pricing, 90 against 0
- Maintenance & community, 83 against 59
- Transparency & trust, 70 against 56
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
The server is closed source and tool input schemas are only visible through an authenticated session
Best for IT administrators running Neat meeting-room devices on Pulse who want an agent to check fleet health, sensor readings and room set-up.
Ahead on
- Security & auth, 79 against 72
Also in its favour
- Runs on your own machine
Watch 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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Axiom MCP Server +90
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.
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.
Reliability Axiom MCP Server +37
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.
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.
Maintenance & community Axiom MCP Server +24
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.
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.
Agent ergonomics Axiom MCP Server +20
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.
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.
Transparency & trust Axiom MCP Server +14
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.
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.
Schema & documentation Axiom MCP Server +13
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.
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.
Score by category
| Category | Weight | Axiom MCP Server | Neat Pulse MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 72 | 35 | Axiom MCP Server +37 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 62 | 49 | Axiom MCP Server +13 |
| Agent ergonomics | 13% | 63 | 43 | Axiom MCP Server +20 |
| Security & auth | 14% | 72 | 79 | Neat Pulse MCP +7 |
| Payments & pricing | 10% | 90 | 0 | Axiom MCP Server +90 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 59 | Axiom MCP Server +24 |
| Transparency & trust | 7% | 70 | 56 | Axiom MCP Server +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 72/100 | E 45.8/100 |
Facts side by side
| Fact | Axiom MCP Server | Neat Pulse MCP |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Axiom, Inc. | Neat |
| Hosted endpoint | https://mcp.axiom.co/mcp | no (local only) |
| Transports | Streamable HTTP, SSE (legacy) | stdio |
| Auth | OAuth | API key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Tools exposed | 31 | 30 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | co.axiom/mcp | not listed |
| Last release | 2026-10-29 | 2026-11-17 |
| Terms last updated | no date given | 2025-03-26 |
| Privacy policy last updated | no date given | 2026-07-13 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
How the scores have moved
Neat Pulse MCP
No score change since it was listed.
Verdicts
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.
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.
Before you call either
Axiom MCP Server
- With no organisation, call
POST https://api.axiom.co/v2/orgs/provisiononce, store the returned token and surface theclaimUrlto the person; both are shown once and the organisation is deleted after 24 hours unclaimed - Call
listDatasetsandgetDatasetFieldsbeforequeryDataset; metrics datasets takequeryMetricswith MPL, not APL - Treat a 429 as a rate limit or a query-cost cap; read
X-RateLimit-Resetor 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,deleteMonitoranddeleteNotifierare live writes with no confirmation step; list first and confirm with the person before deleting
Neat Pulse MCP
- Ask the person to confirm before
delete_room,delete_device,reboot_deviceorreset_enrolment_code. Deleting a room unenrols all its devices - Ask the person before
send_message_to_deviceorsend_message_to_room, because the message shows on screens in the room - Call
get_domain_guidefirst if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy - If
move_devicereturnsprofile_confirmation_needed, ask whether to apply the room's profile, then repeat the call withassign_room_profile - If a call returns 401, ask the person for a new Pulse token. If it returns 404, check
PULSE_ORG_ID
Questions
Which is better for AI agents, Axiom MCP Server or Neat Pulse MCP?
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 & auth.
Do Axiom MCP Server and Neat Pulse MCP need an API key?
Axiom MCP Server uses an OAuth sign-in. Neat Pulse MCP needs an API key.
Can an agent call Axiom MCP Server and Neat Pulse MCP without installing anything?
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.
Other comparisons with Axiom MCP Server or Neat Pulse MCP
- Axiom MCP Server vs Cronitor MCP server
- Axiom MCP Server vs incident.io API
- Axiom MCP Server vs PagerDuty MCP Server
- Axiom MCP Server vs Rootly MCP Server
- Better Stack vs Neat Pulse MCP
- Causely MCP server vs Neat Pulse MCP
- Cronitor MCP server vs Neat Pulse MCP
- Datadog MCP Server vs Neat Pulse MCP
- Grafana MCP Server vs Neat Pulse MCP
- Honeycomb MCP vs Neat Pulse MCP
- Neat Pulse MCP vs New Relic MCP Server
- Axiom MCP Server vs Better Stack
- Axiom MCP Server vs Causely MCP server
- Axiom MCP Server vs Datadog MCP Server
- Axiom MCP Server vs Grafana MCP Server
- Axiom MCP Server vs Honeycomb MCP
- Axiom MCP Server vs New Relic MCP Server
- Neat Pulse MCP vs Sentry MCP
- Axiom MCP Server vs Sentry MCP
Machine-readable
- This page as Markdown
/compare/axiom-vs-neat-pulse-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/axiom.json·/api/v1/tools/neat-pulse-mcp.json - From a terminal
anchor compare axiom neat-pulse-mcp(the CLI) - Over MCP
compare_tools {"a": "axiom", "b": "neat-pulse-mcp"}at/mcp, no key