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

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

At the door

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

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.

Found and recommended

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

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

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

All 360 checks, one company a day. Corrections to the corrections page.