# Cronitor MCP server vs PagerDuty MCP Server

> Cronitor scores 59.1 (C) to PagerDuty's 43.9 (E) for incidents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp
- Markdown: https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md (~4,550 tokens)
- 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-07

Cronitor MCP server scores 59.1 (C) on agent readiness against PagerDuty MCP Server's 43.9 (E), and leads in 5 of 7 scored categories. PagerDuty MCP Server leads on security & auth and transparency & trust. Both do incidents.

- Cronitor MCP server: grade C, 59.1/100, rank #718 of 1510. Markdown https://www.anchorterminal.com/tools/cronitor-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json
- PagerDuty MCP Server: grade E, 43.9/100, rank #1239 of 1510. Markdown https://www.anchorterminal.com/tools/pagerduty-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/pagerduty-mcp.json
- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md
- All 59 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 40
- Agent ergonomics, 73 against 59
- Payments & pricing, 40 against 10
- Maintenance & community, 55 against 17

Watch for: 71 tools, a heavy context load

### PagerDuty MCP Server (E)

Good for: Incident and on-call agents in PagerDuty shops on Professional or higher.

Ahead on:
- Security & auth, 66 against 58
- Transparency & trust, 75 against 37

Watch for: No read-only mode or tool filtering on the hosted server, so OAuth scopes are the only write barrier


## Why the edge

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

- 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.
- PagerDuty MCP Server (40): The hosted tool input schemas aren't published. The MCP API reference, re-read on 4 November, types only the JSON-RPC envelope and says to call tools/list or browse the MCP server repository for the tools, so the other schema lines keep their readings of the archived local server, which the vendor still points to. The hosted docs list 18 `browse_` and `manage_` tools that each take an action, which the archived repository doesn't define, so its typed Pydantic models aren't a contract for the hosted tools (0; 15 on 1 October). llms.txt, llms-full.txt and Markdown copies of each page at docs.pagerduty.com (10). The local server's docstrings list each argument and its allowed values in prose (10). Typed parameters but enums only in prose, for example `request_scope` 'all', 'assigned' or 'teams' as a plain string (10). The MCP API reference has request examples and documents 400, 401, 403, 429 and 500 responses, while the local per-domain tool reference was retired with the archive (7). No changelog for the hosted server. The local CHANGELOG has one undated entry (3). 0 + 10 + 10 + 10 + 7 + 3 = 40.

### Maintenance & community: Cronitor MCP server +38

- Cronitor MCP server (55): Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
- PagerDuty MCP Server (17): No hosted changelog or tagged release. The archived local server's last version bumps, 1.0.0 (12 June 2026) and 1.1.0 (7 July 2026), are untagged commits, 1.1.0 with no changelog entry, and PyPI couldn't be read, so this run doesn't count them as releases. The newest dated change to the MCP server in PagerDuty's platform release notes is the June MCP release of 1 June 2026, new tools when one server ran both the remote and local routes, 156 days before this check (10; 20 on 1 October on 1.1.0). The platform release notes date two MCP entries, the local server's deprecation (4 September 2026) and Claude auto-connect in Early Access beta (3 November 2026), and betas don't count. Fewer than three dated entries in the 90 days from 6 August (0). Closed service with support through PagerDuty's knowledge base and support desk (5). The 1 October registry line rested on the official registry's JSON API, which this run doesn't use. The archived repository's server.json naming io.github.PagerDuty/pagerduty-mcp 0.2.1 is a claim, and the hosted server isn't shown registered (0; 5 on 1 October). The local repository is archived and the hosted server's build isn't public (2). 10 + 0 + 5 + 0 + 2 = 17.

### Transparency & trust: PagerDuty MCP Server +38

- 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.
- PagerDuty MCP Server (75): The hosted server is closed with published terms (effective 21 December 2023), and the archived local server was Apache-2.0 (18). Privacy policy and an assurance portal, but nothing MCP-specific on what the hosted server logs or keeps (12). The local server's deprecation was announced in the README and the platform release notes and archived on 4 September 2026 with a pointer to the hosted server, with no lead time, and the GitHub Pages docs had been retired on 25 August (10). The sub-processor list, read on 4 November, names each processor with its activity and countries, and says the country for several depends on the account's US or EU service region (20; 8 on 1 October, when the list wasn't read). 18 + 12 + 10 + 20 = 60.

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

- Cronitor MCP server (40): 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.
- PagerDuty MCP Server (10): No x402, MPP or L402 (0). Plan prices are public, re-read on 4 November. Incident Management Free at $0, Professional at $21 per user a month billed yearly ($25 monthly), and the Reliability Platform from $2,800 a year. No per-call price and no statement that MCP costs nothing extra (10). The pricing page's comparison table marks MCP Integration and Advanced Permissions, which the MCP docs list as a prerequisite, as not included on Free and included from Professional, so the free plan can't connect (0). A person signs up and creates a key or an OAuth client (0). 0 + 10 + 0 + 0 = 10.

### 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.
- PagerDuty MCP Server (35): Scored as a hosted MCP server. status.pagerduty.com answered its robots.txt request on 4 November 2026 with the status page's own HTML app, so the host is left unread, and no component reading of it is on record (the 1 October check found it rendered only with JavaScript). A status-page line with no component reading scores 0 (15 on 1 October), and no incident history could be read (5). The REST API allows 960 requests a minute per account key, user key or app token, re-read on 4 November, and the MCP docs don't say whether the same limit applies to mcp.pagerduty.com (10, a partial kept from 1 October). The REST docs describe 429 with `ratelimit-limit`, `ratelimit-remaining` and `ratelimit-reset` and tell clients to slow down and wait out the reset before retrying, and the MCP API reference lists a 429 response. No `Retry-After`, no idempotency key and nothing on retrying writes, so retry-wait guidance alone (10; the 1 October 12 needs safe-retry guidance). No SLA on the pricing page (0). The hosted server is the supported path and carries no beta or preview label, though Claude auto-connect, one sign-in route, is an Early Access beta since 3 November (10). 0 + 5 + 10 + 10 + 0 + 10 = 35.

### Agent ergonomics: Cronitor MCP server +14

- 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.
- PagerDuty MCP Server (59): The hosted server's documentation page, re-read on 4 November, lists 18 tools, `browse_` and `manage_` pairs for incidents, services, schedules, teams, event orchestrations, alert grouping and status pages, plus `browse_escalation_policies`, `browse_users`, `browse_change_events` and `browse_activity`, each taking an action. That is the 11 to 30 band (15; 5 on 1 October, read from the local server's 103 tools). Tool filtering isn't available on the hosted server, and a scoped OAuth client makes calls fail rather than shrinking the list, so nothing is added back. Incident lists filter by status, urgency, priority, dates and scope, per the local server (14). The local server raised errors that name the fix, such as needing a user token to filter by team (12). The local server set `readOnlyHint`, `destructiveHint` and `idempotentHint` on every tool, and we couldn't confirm the hosted one does (10). Few required parameters (8). 15 + 14 + 12 + 10 + 8 = 59.

## Score by category

| Category | Weight | Cronitor MCP server | PagerDuty MCP Server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 35 | Cronitor MCP server +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 40 | Cronitor MCP server +40 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 59 | Cronitor MCP server +14 |
| Security & auth | 14% (17.5 this run) | 58 | 66 | PagerDuty MCP Server +8 |
| Payments & pricing | 10% (12.5 this run) | 40 | 10 | Cronitor MCP server +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 55 | 17 | Cronitor MCP server +38 |
| Transparency & trust | 7% (8.8 this run) | 37 | 75 | PagerDuty MCP Server +38 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **59.1 · C** | **43.9 · E** | |

## Facts side by side

| Fact | Cronitor MCP server | PagerDuty MCP Server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Cronitor | PagerDuty |
| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.pagerduty.com/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Your plan |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Tools exposed | 71 | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.cronitor/cronitor` | not listed |
| Last release | none | 2026-09-04 |
| Terms last updated | no document linked | 2023-12-21 |
| Privacy policy last updated | no document linked | 2025-09-01 |
| 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 | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Agent reviews | none | 1.5/5 (2) |

## How the scores have moved

### Cronitor MCP server

No score change since it was listed.

### PagerDuty MCP Server

- -4.7 on 4 November 2026 (D to E): new evidence, correction
- +0.2 on 27 October 2026: checklist
- -0.1 on 8 October 2026: checklist

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

**PagerDuty MCP Server.** PagerDuty's hosted MCP server takes scoped OAuth with per-resource scopes and mandatory PKCE, or an API key in a header, and its docs list 18 tools. It has no read-only mode or tool filtering, MCP needs the Professional plan or higher, and the status page couldn't be read.

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

### PagerDuty MCP Server

1. Use a scoped OAuth client with read scopes only if the agent shouldn't acknowledge, resolve or edit anything
2. Use a user API key or user OAuth for `assigned` or `teams` filters. Account-level keys fail those calls
3. Pass `limit` and a date range on incident lists to keep responses small
4. EU accounts must use mcp.eu.pagerduty.com
5. On 429, wait `ratelimit-reset` seconds before retrying. There's no Retry-After header

## Questions

### Which is better for AI agents, Cronitor MCP server or PagerDuty MCP Server?

Cronitor MCP server scores 59.1 (C) on agent readiness against PagerDuty MCP Server's 43.9 (E), and leads in 5 of 7 scored categories. PagerDuty MCP Server leads on security & auth and transparency & trust.

### Do Cronitor MCP server and PagerDuty MCP Server need an API key?

Cronitor MCP server uses an OAuth sign-in. PagerDuty MCP Server takes an API key or an OAuth sign-in.

### Can an agent call Cronitor MCP server and PagerDuty MCP Server without installing anything?

Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and PagerDuty MCP Server at https://mcp.pagerduty.com/mcp.


## For agents

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

## Other comparisons with Cronitor MCP server or PagerDuty MCP Server

- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)
- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md)
- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)
- [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md)
- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)
- [Causely MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/causely-vs-pagerduty-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 Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)
- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.md)
- [Grafana MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-pagerduty-mcp.md)
- [incident.io API vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.md)
- [New Relic MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.md)
- [PagerDuty MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/pagerduty-mcp-vs-rootly-mcp.md)
- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)

---

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