# Cronitor MCP server vs Neat Pulse MCP

> Cronitor scores 61.6 (C) to Neat Pulse MCP's 45.8 (E) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp
- Markdown: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md (~4,000 tokens)
- Slim: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Cronitor MCP server scores 61.6 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 4 of 7 scored categories. Neat Pulse MCP leads on security & auth and transparency & trust. Both do metrics and monitoring.

- Cronitor MCP server: grade C, 61.6/100, rank #723 of 1557. Markdown https://www.anchorterminal.com/tools/cronitor-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json
- 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
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 68 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md

## Which one, for what

### Cronitor MCP server (C)

Good for: Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.

Ahead on:
- Reliability, 55 against 35
- Schema & documentation, 80 against 49
- Agent ergonomics, 73 against 43
- Payments & pricing, 60 against 0

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: 71 tools, a heavy context load

### Neat Pulse MCP (E)

Good 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 58
- Transparency & trust, 56 against 37

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

### Payments & pricing: Cronitor MCP server +60

- Cronitor MCP server (60): 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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
- 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.

### Schema & documentation: Cronitor MCP server +31

- 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.
- 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.

### Agent ergonomics: Cronitor MCP server +30

- Cronitor MCP server (73): 71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73.
- 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.

### Security & auth: Neat Pulse MCP +21

- 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.
- Neat Pulse MCP (79): Scoped, revocable Pulse API tokens with a rotation endpoint, created only by organisation Owners and passed in an environment variable. The scopes are coarse, Read or everything (27). A Read-only token blocks every change per the setup guide, and the reference flags irreversible tools, but confirmation is left to the assistant (14). Room notes and device names are text people enter, and no prompt-injection guidance was found (5). Pulse audit logs record every MCP action under the token's name, and an MCP tool reads them (15). security.txt valid to August 2027, a vulnerability reporting policy, public advisories through November 2026, and a support article stating ISO 27001 certification. No bug bounty found (18). 27 + 14 + 5 + 15 + 18 = 79.

### Reliability: Cronitor MCP server +20

- 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.
- 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.

### Transparency & trust: Neat Pulse MCP +19

- 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.
- 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.

## Score by category

| Category | Weight | Cronitor MCP server | Neat Pulse MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 55 | 35 | Cronitor MCP server +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 49 | Cronitor MCP server +31 |
| Agent ergonomics | 13% | 73 | 43 | Cronitor MCP server +30 |
| Security & auth | 14% | 58 | 79 | Neat Pulse MCP +21 |
| Payments & pricing | 10% | 60 | 0 | Cronitor MCP server +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 55 | 59 | Neat Pulse MCP +4 |
| Transparency & trust | 7% | 37 | 56 | Neat Pulse MCP +19 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.6 · C** | **45.8 · E** | |

## Facts side by side

| Fact | Cronitor MCP server | Neat Pulse MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Cronitor | Neat |
| Hosted endpoint | `https://cronitor.io/mcp` | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth | API key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Tools exposed | 71 | 30 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `io.cronitor/cronitor` | not listed |
| Last release | none | 2026-11-17 |
| Terms last updated | no document linked | 2025-03-26 |
| Privacy policy last updated | no document linked | 2026-07-13 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |

## How the scores have moved

### Cronitor MCP server

- +2.5 on 13 November 2026: checklist

### Neat Pulse MCP

No score change since it was listed.

## Verdicts

**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.

**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

### Cronitor MCP server

1. Start with list_monitors and list_issues in summary mode
2. Ask the user before expanding event messages, command output or request bodies
3. On a rate-limit error, wait retry_after_seconds
4. Over the plan's monitor limit, new monitors are saved but disabled

### Neat Pulse MCP

1. Ask the person to confirm before `delete_room`, `delete_device`, `reboot_device` or `reset_enrolment_code`. Deleting a room unenrols all its devices
2. Ask the person before `send_message_to_device` or `send_message_to_room`, because the message shows on screens in the room
3. Call `get_domain_guide` first if the client doesn't read MCP resources, to learn the region, location, room and device hierarchy
4. If `move_device` returns `profile_confirmation_needed`, ask whether to apply the room's profile, then repeat the call with `assign_room_profile`
5. 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, Cronitor MCP server or Neat Pulse MCP?

Cronitor MCP server scores 61.6 (C) on agent readiness against Neat Pulse MCP's 45.8 (E), and leads in 4 of 7 scored categories. Neat Pulse MCP leads on security & auth and transparency & trust.

### Do Cronitor MCP server and Neat Pulse MCP need an API key?

Cronitor MCP server uses an OAuth sign-in. Neat Pulse MCP needs an API key.

### Can an agent call Cronitor MCP server and Neat Pulse MCP without installing anything?

Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp. Neat Pulse MCP runs on your own machine, with no hosted endpoint listed.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "cronitor-mcp", "b": "neat-pulse-mcp"}`. From a terminal: `anchor compare cronitor-mcp neat-pulse-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/neat-pulse-mcp.json

## Other comparisons with Cronitor MCP server or Neat Pulse MCP

- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)
- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)
- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)
- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)
- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)
- [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md)
- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)
- [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md)
- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)
- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.md)
- [Better Stack vs Neat Pulse MCP](https://www.anchorterminal.com/compare/better-stack-vs-neat-pulse-mcp.md)
- [Causely MCP server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/causely-vs-neat-pulse-mcp.md)
- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)
- [Datadog MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-neat-pulse-mcp.md)
- [Grafana MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-neat-pulse-mcp.md)
- [Honeycomb MCP vs Neat Pulse MCP](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-neat-pulse-mcp.md)
- [Neat Pulse MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-new-relic.md)
- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-vs-sentry-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
