{
  "data": {
    "a": {
      "slug": "cronitor-mcp",
      "name": "Cronitor MCP server",
      "vendor": "Cronitor",
      "vendorUrl": "https://cronitor.io",
      "company": "cronitor.io",
      "kind": "mcp",
      "category": "observability",
      "summary": "Cronitor's hosted MCP server lets an agent create and manage cron job, heartbeat and uptime monitors, issues, status pages, alert integrations and metrics in a Cronitor account, over OAuth or an API key.",
      "url": "https://www.anchorterminal.com/tools/cronitor-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json",
      "dns": "cronitor-mcp.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://cronitor.io/mcp",
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth through protected-resource metadata, with sign-in and consent in a browser; the token carries the user's role, capped at the SDK Integration key's permissions, with no scope selection. An API key in a header works for headless clients, with the key's granular read or write scopes.",
      "pricing": "freemium",
      "pricingNotes": "Free forever for 5 monitors. Business is $2 a monitor and $5 a user a month after a 14-day trial (checked 2026-11-07).",
      "priceSummary": "Freemium",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).",
        "endpoints": []
      },
      "toolCount": 71,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-07"
      },
      "docsUrl": "https://cronitor.io/docs/mcp-server",
      "llmsTxt": "https://cronitor.io/llms.txt",
      "registryName": "io.cronitor/cronitor",
      "capabilities": [
        "observability.incidents",
        "observability.metrics",
        "events.schedule",
        "agent.tools"
      ],
      "tags": [
        "official",
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "api-key",
        "freemium",
        "free-tier",
        "status-page",
        "llms-txt",
        "mcp-registry"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 61.6,
        "grade": "C",
        "agentReady": false,
        "rank": 723,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 7,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 55,
          "payments": 60,
          "reliability": 55,
          "schema": 80,
          "security": 58,
          "transparency": 37
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-07"
        },
        "negative": 0,
        "verdict": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.",
        "bestFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.",
        "strengths": [
          "Strict input schemas (additionalProperties false) with enums and required combinations",
          "Summary modes with paging keep list output small",
          "JSON-RPC error codes with retry_after_seconds and required_scope",
          "Clear guidance on secrets in event messages and output",
          "Free plan for 5 monitors"
        ],
        "weaknesses": [
          "71 tools, a heavy context load",
          "No public changelog",
          "Terms and privacy closed to crawlers, so unread",
          "No audit log of agent calls found"
        ],
        "agentNotes": [
          "Start with list_monitors and list_issues in summary mode",
          "Ask the user before expanding event messages, command output or request bodies",
          "On a rate-limit error, wait retry_after_seconds",
          "Over the plan's monitor limit, new monitors are saved but disabled"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 61.6
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 55,
          "payments": 60,
          "reliability": 55,
          "schema": 80,
          "security": 58,
          "transparency": 25
        },
        "provenanceScore": 48,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-07",
            "maintenance": "2026-11-07",
            "payments": "2026-11-07",
            "reliability": "2026-11-07",
            "schema": "2026-11-07",
            "security": "2026-11-07",
            "transparency": "2026-11-07"
          },
          "last": "2026-11-07",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-07",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "claudeCode": "claude mcp add cronitor --transport http https://cronitor.io/mcp",
        "config": {
          "mcpServers": {
            "cronitor": {
              "url": "https://cronitor.io/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/observability.incidents",
        "tool": "https://letme.dev/cronitor-mcp"
      },
      "area": "developer",
      "provenance": {
        "legalEntity": "Cronitor",
        "domain": "cronitor.io",
        "domainRegistered": "",
        "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.",
        "endpointOnVendorDomain": true,
        "terms": "",
        "privacy": "",
        "statusPage": "https://status.cronitor.io",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-07",
        "notes": [
          "robots.txt disallows the terms and privacy pages, so the legal entity wasn't read.",
          "security.txt answered 404."
        ],
        "score": 48
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.json",
      "live": {
        "slug": "cronitor-mcp",
        "probe": {
          "target": "https://cronitor.io/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T23:13:16.714771083Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 819,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 605,
          "p95ms24h": 832,
          "samples24h": 241,
          "samples30d": 2715,
          "days": [
            {
              "date": "2026-11-07",
              "probes": 53,
              "ok": 53
            },
            {
              "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-07T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.cronitor.io",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:52:20.541596065Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.cronitor/cronitor",
            "version": "1.0.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "securityTxt": {
          "url": "https://cronitor.io/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:22.894508778Z"
        },
        "llmsTxt": {
          "url": "https://cronitor.io/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:03.310796316Z"
        },
        "domain": {
          "domain": "cronitor.io",
          "checkedAt": "2026-11-15T15:41:04.802744212Z"
        },
        "mcpTools": {
          "url": "https://cronitor.io/mcp",
          "checkedAt": "2026-11-18T04:22:59.062032429Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-08T01:57:14.564408153Z"
        },
        "updatedAt": "2026-11-18T23:13:16.714771083Z"
      },
      "streak": {
        "days": 11,
        "from": "2026-11-07",
        "sinceWatching": true,
        "best": 11
      }
    },
    "answer": "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 \u0026 auth and transparency \u0026 trust.",
    "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": 60,
        "category": "payments",
        "leads": "cronitor-mcp",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "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": 60,
          "b": 0
        }
      },
      {
        "by": 31,
        "category": "schema",
        "leads": "cronitor-mcp",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "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": 80,
          "b": 49
        }
      },
      {
        "by": 30,
        "category": "ergonomics",
        "leads": "cronitor-mcp",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "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": 73,
          "b": 43
        }
      },
      {
        "by": 21,
        "category": "security",
        "leads": "neat-pulse-mcp",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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.",
          "b": "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."
        },
        "scores": {
          "a": 58,
          "b": 79
        }
      },
      {
        "by": 20,
        "category": "reliability",
        "leads": "cronitor-mcp",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "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": 55,
          "b": 35
        }
      },
      {
        "by": 19,
        "category": "transparency",
        "leads": "neat-pulse-mcp",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "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": 37,
          "b": 56
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Cronitor",
        "b": "Neat",
        "name": "Vendor"
      },
      {
        "a": "https://cronitor.io/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "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": "71",
        "b": "30",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "io.cronitor/cronitor",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "none",
        "b": "2026-11-17",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "2025-03-26",
        "name": "Terms last updated"
      },
      {
        "a": "no document linked",
        "b": "2026-07-13",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 auth and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Cronitor MCP server or Neat Pulse MCP?"
      },
      {
        "answer": "Cronitor MCP server uses an OAuth sign-in. Neat Pulse MCP needs an API key.",
        "question": "Do Cronitor MCP server and Neat Pulse MCP need an API key?"
      },
      {
        "answer": "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.",
        "question": "Can an agent call Cronitor MCP server and Neat Pulse MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 55 against 35",
          "Schema \u0026 documentation, 80 against 49",
          "Agent ergonomics, 73 against 43",
          "Payments \u0026 pricing, 60 against 0"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.",
        "slug": "cronitor-mcp",
        "watchFor": "71 tools, a heavy context load"
      },
      {
        "aheadOn": [
          "Security \u0026 auth, 79 against 58",
          "Transparency \u0026 trust, 56 against 37"
        ],
        "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": {
      "cronitor-mcp": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 59.1,
          "fromGrade": "C",
          "to": 61.6,
          "toGrade": "C"
        }
      ],
      "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/better-stack-vs-cronitor-mcp.json",
        "title": "Better Stack vs Cronitor MCP server",
        "url": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.json",
        "title": "Causely MCP server vs Cronitor MCP server",
        "url": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json",
        "title": "Cronitor MCP server vs Datadog MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.json",
        "title": "Cronitor MCP server vs Grafana MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json",
        "title": "Cronitor MCP server vs incident.io API",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json",
        "title": "Cronitor MCP server vs New Relic MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.json",
        "title": "Cronitor MCP server vs PagerDuty MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json",
        "title": "Cronitor MCP server vs Rootly MCP Server",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-mcp.json",
        "title": "Axiom MCP Server vs Neat Pulse MCP",
        "url": "https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-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-honeycomb-mcp.json",
        "title": "Cronitor MCP server vs Honeycomb MCP",
        "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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/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"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 20,
        "cronitor-mcp": 55,
        "edge": "cronitor-mcp",
        "key": "reliability",
        "name": "Reliability",
        "neat-pulse-mcp": 35,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 31,
        "cronitor-mcp": 80,
        "edge": "cronitor-mcp",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "neat-pulse-mcp": 49,
        "weight": 13
      },
      {
        "by": 30,
        "cronitor-mcp": 73,
        "edge": "cronitor-mcp",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "neat-pulse-mcp": 43,
        "weight": 13
      },
      {
        "by": 21,
        "cronitor-mcp": 58,
        "edge": "neat-pulse-mcp",
        "key": "security",
        "name": "Security \u0026 auth",
        "neat-pulse-mcp": 79,
        "weight": 14
      },
      {
        "by": 60,
        "cronitor-mcp": 60,
        "edge": "cronitor-mcp",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "neat-pulse-mcp": 0,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 4,
        "cronitor-mcp": 55,
        "edge": "neat-pulse-mcp",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "neat-pulse-mcp": 59,
        "weight": 7
      },
      {
        "by": 19,
        "cronitor-mcp": 37,
        "edge": "neat-pulse-mcp",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "neat-pulse-mcp": 56,
        "weight": 7
      }
    ],
    "summary": "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 \u0026 auth and transparency \u0026 trust. Both do metrics and monitoring.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "cronitor-mcp": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.",
      "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/cronitor-mcp-vs-neat-pulse-mcp",
    "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp.min.md"
  },
  "markdown": "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 \u0026 auth and transparency \u0026 trust. Both do metrics and monitoring.\n\n- 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\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### Cronitor MCP server (C)\n\nGood for: Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.\n\nAhead on:\n- Reliability, 55 against 35\n- Schema \u0026 documentation, 80 against 49\n- Agent ergonomics, 73 against 43\n- Payments \u0026 pricing, 60 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: 71 tools, a heavy context load\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 58\n- Transparency \u0026 trust, 56 against 37\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: Cronitor MCP server +60\n\n- 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.\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### Schema \u0026 documentation: Cronitor MCP server +31\n\n- Cronitor MCP server (80): Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.\n- 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### Agent ergonomics: Cronitor MCP server +30\n\n- 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.\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### Security \u0026 auth: Neat Pulse MCP +21\n\n- Cronitor MCP server (58): OAuth bounded by role with no scope choice, or scoped API keys (22 of 30). Read-only users get only read tools; write tools follow the role (14 of 20). The docs warn that event messages, command output and request bodies can hold customer data or secrets, and tell the agent to ask before expanding them; secrets are redacted (12 of 15). No audit log of MCP calls found (0). The security page covers encryption and relies on AWS's certifications; no security.txt (404) and no disclosure policy found (10 of 20). 22 + 14 + 12 + 0 + 10 = 58.\n- 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.\n\n### Reliability: Cronitor MCP server +20\n\n- Cronitor MCP server (55): Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.\n- 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### Transparency \u0026 trust: Neat Pulse MCP +19\n\n- Cronitor MCP server (37): robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.\n- 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## Score by category\n\n| Category | Weight | Cronitor MCP server | Neat Pulse MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 55 | 35 | Cronitor MCP server +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 80 | 49 | Cronitor MCP server +31 |\n| Agent ergonomics | 13% | 73 | 43 | Cronitor MCP server +30 |\n| Security \u0026 auth | 14% | 58 | 79 | Neat Pulse MCP +21 |\n| Payments \u0026 pricing | 10% | 60 | 0 | Cronitor MCP server +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 55 | 59 | Neat Pulse MCP +4 |\n| Transparency \u0026 trust | 7% | 37 | 56 | Neat Pulse MCP +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.6 · C** | **45.8 · E** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | Neat Pulse MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Cronitor | Neat |\n| Hosted endpoint | `https://cronitor.io/mcp` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth | API key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Tools exposed | 71 | 30 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | `io.cronitor/cronitor` | not listed |\n| Last release | none | 2026-11-17 |\n| Terms last updated | no document linked | 2025-03-26 |\n| Privacy policy last updated | no document linked | 2026-07-13 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | yes |\n\n## How the scores have moved\n\n### Cronitor MCP server\n\n- +2.5 on 13 November 2026: checklist\n\n### Neat Pulse MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Cronitor MCP server.** Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.\n\n**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### Cronitor MCP server\n\n1. Start with list_monitors and list_issues in summary mode\n2. Ask the user before expanding event messages, command output or request bodies\n3. On a rate-limit error, wait retry_after_seconds\n4. Over the plan's monitor limit, new monitors are saved but disabled\n\n### 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, Cronitor MCP server or Neat Pulse MCP?\n\nCronitor 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 \u0026 auth and transparency \u0026 trust.\n\n### Do Cronitor MCP server and Neat Pulse MCP need an API key?\n\nCronitor MCP server uses an OAuth sign-in. Neat Pulse MCP needs an API key.\n\n### Can an agent call Cronitor MCP server and Neat Pulse MCP without installing anything?\n\nCronitor MCP server has a hosted endpoint at https://cronitor.io/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/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\n- 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`\n- 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\n\n## Other comparisons with Cronitor 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- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)\n- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md)\n- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)\n- [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md)\n- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)\n- [Axiom MCP Server vs Neat Pulse MCP](https://www.anchorterminal.com/compare/axiom-vs-neat-pulse-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 Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-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- [Neat Pulse MCP vs Sentry MCP](https://www.anchorterminal.com/compare/neat-pulse-mcp-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": "Cronitor MCP server vs Neat Pulse MCP",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "Cronitor MCP server C 61.6",
      "Neat Pulse MCP E 45.8",
      "scores"
    ],
    "h1": "Cronitor MCP server vs Neat Pulse MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/cronitor-mcp-vs-neat-pulse-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Cronitor vs Neat Pulse MCP for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-neat-pulse-mcp"
  },
  "tokens": {
    "markdown": 4000,
    "slim": 1130
  },
  "version": 1
}
