---
title: "PagerDuty: the 360 agent-readiness check | Agent MCP Directory"
description: "PagerDuty on Ora's agent-readiness scan, read 2026-11-09: 70 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call."
canonical: https://agentmcpdirectory.com/blog/pagerduty-agent-readiness
site: "Agent MCP Directory"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# PagerDuty: the 360 agent-readiness check | Agent MCP Directory

> PagerDuty on Ora's agent-readiness scan, read 2026-11-09: 70 of 100, grade B, with the MCP, API and OAuth surfaces an agent can call.

Source: https://agentmcpdirectory.com/blog/pagerduty-agent-readiness
Site: Agent MCP Directory
Last reviewed: 2026-11-09

# PagerDuty: the 360 agent-readiness check

PagerDuty scores 70 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. Markdown on request and a live server, with the specification still to publish.

On 9 November 2026 the public site at pagerduty.com scored 70 of 100 on [Ora's](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a B, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: PagerDuty offers strong developer discoverability and SDK packages, but lacks a published OpenAPI specification for agents to call its API.

## The score

| Layer | Asks | Points | Share |
| --- | --- | --- | --- |
| Usability | Can agents use it | 47 of 81 | 58% |
| Access | Can agents read it | 46 of 62 | 74% |
| Discovery | Can agents find and recommend it | 14 of 16 | 88% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 70 of 100 | 70% |

## What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.

In the directory, PagerDuty no MCP endpoint on record; the connector run of 4 November 2026 is on [the entry page](https://agentmcpdirectory.com/directory/pagerduty-com/). Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.pagerduty.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Partial | 1 of 2 | MCP server at https://mcp.pagerduty.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://docs.pagerduty.com/get-started.md. GraphQL endpoint at https://api.pagerduty.com/graphql is reachable; introspection requires authentication (API key / OAuth), |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.pagerduty.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://app.pagerduty.com/global/oauth/anonymous |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 22 of 22 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Partial | 2 of 3 | CLI tool mentioned in llms.txt |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 4 ecosystems: npm, pypi, go, rubygems |
| Rate limit response headers rate-limit-headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |

## At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://pagerduty.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |

## What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 6712 chars with H1, but 4.5% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~3K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.pagerduty.com/sitemap_index.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.pagerduty.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt contains markdown links and has 211 lines, but it doesn't start with a markdown heading. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Returns markdown when requested via Accept header |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://pagerduty.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Partial | 3 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 1 of 2 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |

## Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

| Check | Result | Points | What Ora saw |
| --- | --- | --- | --- |
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | pagerduty.com ranks #1 for "PagerDuty incident management" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "PagerDuty" and Wikidata Q48989804 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | No verified entry in the official MCP Registry or on Smithery, and no npm or PyPI package of yours that runs as an MCP server. To pass, |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (73 community skills with potential relation to this domain found, but only self-published official skills count) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |

## Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to pagerduty.com.

## The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for PagerDuty, with what Ora observed. The wording of each fix is Ora's; [the 28 checks it runs on an MCP server](https://agentmcpdirectory.com/mcp-checks/) are listed with their layer and tier.

-   OpenAPI spec published: fail, 0 of 7, about 3.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
-   Scoped permissions: fail, 0 of 5, about 2.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
-   WebMCP support: fail, 0 of 5, about 2.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 22 of 22 same-origin script bundle(s) for modelContext registrations)
-   JSON error responses: fail, 0 of 4, about 2.2 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
-   GraphQL typed error model: fail, 0 of 3, about 1.6 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages

## Our read

PagerDuty's act layer is the fintech shape in an infrastructure company: live surfaces, thin description. The MCP server at mcp.pagerduty.com/mcp answers and requires authentication, OAuth authorization server metadata is at app.pagerduty.com, REST documentation is at docs.pagerduty.com with an llms.txt beside it, SDKs are in four registries and the site returns markdown when an agent asks for it with an Accept header, a row most companies here fail. Ora found no OpenAPI specification and no declared scopes, together about 6.5 points, endpoints that do not answer errors as JSON, a GraphQL endpoint whose introspection is gated, and no WebMCP registration in 22 script bundles. The reading side is sound, with a 6,712-character home page just under the 5 percent text target and an Organization block missing only its description, and the domain ranks first for its product term. A specification is the one file between this and an A.

## Test your own surfaces

The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; [the reasons, the limits and the alternatives](https://agentmcpdirectory.com/test-your-mcp-server/) are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

```bash
npx ax@0.10 audit https://example.com --min-score 70
```

[All 360 checks](https://agentmcpdirectory.com/blog/), one company a day. Corrections to [the corrections page](https://agentmcpdirectory.com/corrections/).

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/blog/pagerduty-agent-readiness/index.md)

## Sources

-   [Ora's scan of pagerduty.com, GET /api/score (vendor)](https://ora.ai/api/score/pagerduty.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 9 November 2026
-   [Ora check catalogue, contract 1.38.0](https://ora.ai/api/checks?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=check), read 5 November 2026
-   [pagerduty.com, the company's site](https://www.pagerduty.com/), read 9 November 2026

Last reviewed 9 November 2026