← Registry tracker

PagerDuty

Manage incidents, create services, schedule overrides, and track on-call rotations with your PagerDuty account

View in the Claude registry
Integration type
Connector
Verification status
Verified connector
Platform
Claude
Category
Developer Tools

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Observability, Monitoring & Incident Response

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
Business Data & Low-Code AppsCI/CD & Internal Developer PlatformsCloud DevOps & ObservabilityCloud Infrastructure ManagementDatabases & Backend Data StoresTeam Chat & MessagingTeam Chat & Messaging

Other Subcategories where the Integration is visible.

Brand
PagerDuty
Access
Account required
First tracked
2026-03-06
Tool count
64
Geography
US

Claude Discoverability Score

Live · refreshed daily. Last refreshed

PagerDuty in Observability, Monitoring & Incident Response

43/100
Emerging

#4of 20competitors

Shown to buyers in 42.8% of contested Runs.

How this score is measured
Improve your score Talk to our team

What we measure

One core score. Three important factors to discoverability.

  • Picked

    · 42.8/100
    Sets the score

  • Found

    · 32.9/100
    Diagnostic

  • Positioned

    · 59.5/100
    Diagnostic
Primary Subcategory

Competing in Claude Observability, Monitoring & Incident Response

View Category
#4 of 20ranked by public Discoverability Score
Primary Subcategory
1Datadog93/100
2Coralogix52/100
3incident.io49/100
4PagerDuty43/100
5Vercel21/100
Score explained

What does 43/100 mean?

43 is PagerDuty's rounded picker appearance rate. It appeared in the connector picker, or Claude invoked it directly, in 42.8% of contested conversations. All three measures are important to discoverability: Picked determines the headline score, Found shows how often Claude found PagerDuty in connector search, and Positioned shows where it appeared in the picker.

InvisibleBuriedEmergingCompetitiveWinning

PagerDuty is 17 points from Competitive.

FoundDiagnostic

Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodologyRecommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.
Tools

64 tools agents can invoke

PagerDuty FAQ
How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are PagerDuty alternatives on Claude?

As of 2026-08-14, PagerDuty competes with Datadog, Coralogix, incident.io, Vercel, Sentry, Honeycomb, Railway, Bronto, Origin, Subtext, Axiom, Expo, Lightrun, LogRocket, Orb, Resolve AI, Steadybit, Stealthium, Tsuga in Claude Observability, Monitoring & Incident Response, ranked by public Discoverability Score.

Where does PagerDuty rank in Observability, Monitoring & Incident Response on Claude?

As of 2026-08-14, PagerDuty ranks #4 of 20 in Claude Observability, Monitoring & Incident Response with a Discoverability Score of 43/100 (Emerging).

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.