{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"pagerduty-mcp-server","slug":"pagerduty-mcp-server","name":"PagerDuty MCP Server","type":"mcp","url":"https://github.com/PagerDuty/mcp-server-pagerduty","page_url":"https://unfragile.ai/pagerduty-mcp-server","categories":["mcp-servers"],"tags":["pagerduty","incidents","on-call","community"],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"pagerduty-mcp-server__cap_0","uri":"capability://tool.use.integration.incident.list.and.filter.with.status.awareness","name":"incident-list-and-filter-with-status-awareness","description":"Retrieves incidents from PagerDuty API with real-time status filtering (triggered, acknowledged, resolved) and pagination support. Implements MCP tool protocol to expose PagerDuty's incident endpoint as a callable function, translating query parameters into REST API calls and normalizing response data into structured JSON for LLM consumption.","intents":["Get a list of all active incidents across my organization right now","Filter incidents by status to see which ones need immediate attention","Retrieve incident details programmatically to feed into an LLM-based incident analysis workflow","Integrate incident data into an AI agent that makes decisions about escalation"],"best_for":["DevOps teams building AI-powered incident dashboards","SREs automating incident triage with LLM agents","On-call engineers using Claude or other LLM clients with MCP support"],"limitations":["Pagination is manual — no built-in cursor iteration, requires multiple tool calls for large incident lists","Real-time filtering happens server-side via PagerDuty API; no local caching means latency depends on API response time","Limited to incidents accessible by the API token's service account permissions"],"requires":["PagerDuty API token with read access to incidents","MCP client that supports tool calling (Claude Desktop, Cline, etc.)","Network connectivity to PagerDuty API endpoints"],"input_types":["query parameters (status, limit, offset, service_ids)"],"output_types":["JSON array of incident objects with id, title, status, urgency, service, assigned_via_escalation_policy"],"categories":["tool-use-integration","incident-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_1","uri":"capability://tool.use.integration.incident.acknowledgment.with.context.preservation","name":"incident-acknowledgment-with-context-preservation","description":"Acknowledges incidents in PagerDuty by incident ID, optionally attaching context notes or metadata. Implements MCP tool that wraps PagerDuty's PATCH /incidents endpoint, preserving incident state while updating acknowledgment status and optionally adding notes for audit trails. Supports idempotent operations to prevent duplicate acknowledgments.","intents":["Acknowledge an incident from an LLM agent without manual PagerDuty UI interaction","Add context or notes when acknowledging to document why an incident was acknowledged","Prevent duplicate acknowledgments when the same incident is processed multiple times","Create an audit trail of AI-driven incident acknowledgments for compliance"],"best_for":["Automated incident response workflows driven by LLM agents","Teams using Claude or other LLM clients to triage and acknowledge incidents","Organizations requiring audit trails of incident state changes"],"limitations":["Acknowledgment is user-scoped to the API token's service account; cannot acknowledge on behalf of specific on-call engineers","No rollback mechanism — acknowledged incidents cannot be automatically un-acknowledged if the agent makes an error","Notes are appended as incident timeline entries; no structured metadata field for machine-readable context"],"requires":["PagerDuty API token with write access to incidents","Valid incident ID from PagerDuty","MCP client with tool-calling capability"],"input_types":["incident_id (string), optional notes (string)"],"output_types":["JSON object with updated incident status, acknowledgement timestamp, and timeline entry"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_2","uri":"capability://tool.use.integration.on.call.schedule.querying.with.time.aware.lookup","name":"on-call-schedule-querying-with-time-aware-lookup","description":"Queries PagerDuty on-call schedules to determine who is currently on-call or scheduled for future shifts. Implements MCP tool that calls PagerDuty's schedule endpoint with optional time range parameters, returning on-call user details and shift times. Supports querying multiple schedules and resolving escalation policies to their underlying on-call users.","intents":["Find out who is on-call right now for a specific service or escalation policy","Check the on-call schedule for the next 7 days to plan incident response","Resolve an escalation policy to the actual on-call engineer for context in incident analysis","Build an LLM agent that can answer 'who should I contact about this incident?'"],"best_for":["On-call engineers building AI assistants that need to know shift coverage","Incident response teams automating escalation decisions based on schedule data","Organizations with complex escalation policies requiring schedule resolution"],"limitations":["Schedule data is point-in-time; no real-time updates if an on-call engineer manually changes their availability","Timezone handling depends on PagerDuty account configuration; queries must specify timezone or use account default","Cannot query historical on-call data beyond PagerDuty's retention window (typically 90 days)"],"requires":["PagerDuty API token with read access to schedules","Schedule IDs or escalation policy IDs to query","Optional: timezone string (e.g., 'America/New_York') for accurate time-based queries"],"input_types":["schedule_id or escalation_policy_id (string), optional since (ISO 8601 timestamp), optional until (ISO 8601 timestamp)"],"output_types":["JSON object with on-call user details (name, email, phone), shift start/end times, and schedule metadata"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_3","uri":"capability://tool.use.integration.escalation.policy.trigger.with.validation","name":"escalation-policy-trigger-with-validation","description":"Triggers escalation policies in PagerDuty to manually escalate incidents or create new incidents. Implements MCP tool that wraps PagerDuty's incident creation/escalation endpoint, validating escalation policy IDs and service associations before submission. Supports custom incident titles, descriptions, and urgency levels to provide context for escalated incidents.","intents":["Manually escalate an incident to the next level in the escalation policy from an LLM agent","Create a new incident with a specific escalation policy when an automated system detects a critical issue","Trigger an escalation with custom context (title, description, urgency) to ensure on-call engineers have full details","Build an LLM agent that can decide when to escalate and execute escalation automatically"],"best_for":["Automated incident response systems that need to escalate based on AI-driven decisions","On-call teams using LLM agents to manage incident escalation workflows","Organizations automating escalation decisions based on incident severity or age"],"limitations":["Escalation is immediate and irreversible; no dry-run mode to preview escalation before execution","Escalation policy must be pre-configured in PagerDuty; MCP tool cannot create or modify policies","Cannot escalate to specific individuals — escalation follows the policy's defined levels and users"],"requires":["PagerDuty API token with write access to incidents","Valid escalation policy ID from PagerDuty","Service ID associated with the escalation policy"],"input_types":["escalation_policy_id (string), service_id (string), optional title (string), optional description (string), optional urgency (high/low)"],"output_types":["JSON object with newly created or escalated incident ID, status, escalation policy details, and assigned user"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_4","uri":"capability://tool.use.integration.alert.acknowledgment.with.deduplication","name":"alert-acknowledgment-with-deduplication","description":"Acknowledges individual alerts within PagerDuty incidents, supporting deduplication to prevent duplicate acknowledgments of the same alert. Implements MCP tool that wraps PagerDuty's alert acknowledgment endpoint, tracking alert IDs and timestamps to ensure idempotent operations. Supports batch acknowledgment of multiple alerts from a single incident.","intents":["Acknowledge a specific alert within an incident without acknowledging the entire incident","Prevent duplicate acknowledgments when the same alert is processed multiple times by an LLM agent","Batch acknowledge multiple alerts from a single incident in one operation","Create a detailed audit trail of which alerts were acknowledged and when"],"best_for":["Teams managing incidents with multiple alerts that need granular acknowledgment","Automated alert processing systems that need to deduplicate acknowledgments","Organizations requiring detailed audit trails of alert state changes"],"limitations":["Alert deduplication is client-side; no server-side deduplication tracking, so duplicate calls within the same session may still process","Batch acknowledgment requires multiple alert IDs; no wildcard or pattern-based acknowledgment","Alert data is tied to incident lifecycle; acknowledged alerts are archived when incidents are resolved"],"requires":["PagerDuty API token with write access to incidents","Valid incident ID and alert ID(s) from PagerDuty","MCP client with tool-calling capability"],"input_types":["incident_id (string), alert_id or alert_ids (string or array of strings)"],"output_types":["JSON object with acknowledged alert details, acknowledgment timestamp, and updated incident alert summary"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_5","uri":"capability://tool.use.integration.incident.detail.enrichment.with.timeline.context","name":"incident-detail-enrichment-with-timeline-context","description":"Retrieves detailed incident information including full timeline, notes, and related alerts. Implements MCP tool that fetches incident details from PagerDuty's incident endpoint, aggregating timeline entries, notes, and alert data into a single enriched response. Supports filtering timeline entries by type (escalation, acknowledgment, note) to provide contextual information for LLM analysis.","intents":["Get the full incident timeline to understand how an incident has evolved","Retrieve all notes and context added by team members during incident response","Fetch related alerts to understand the root cause of an incident","Build an LLM agent that can analyze incident history and provide recommendations"],"best_for":["Incident analysis and post-mortem automation using LLM agents","Teams building AI-powered incident intelligence systems","On-call engineers using LLM assistants to understand incident context"],"limitations":["Timeline data is immutable after incident resolution; cannot retrieve historical changes to incident metadata","Large incidents with many timeline entries may exceed token limits in LLM context windows","Alert data is aggregated from PagerDuty's alert endpoint; no direct correlation to external monitoring systems"],"requires":["PagerDuty API token with read access to incidents","Valid incident ID from PagerDuty","MCP client with sufficient context window for large timeline responses"],"input_types":["incident_id (string), optional include_timeline (boolean), optional timeline_type_filter (escalation/acknowledgment/note)"],"output_types":["JSON object with incident details, full timeline array, notes, alert summary, and escalation policy metadata"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_6","uri":"capability://tool.use.integration.service.and.escalation.policy.metadata.lookup","name":"service-and-escalation-policy-metadata-lookup","description":"Queries PagerDuty to retrieve metadata about services and escalation policies, including policy levels, notification rules, and service integrations. Implements MCP tool that fetches service and escalation policy details from PagerDuty's API, normalizing response data for LLM consumption. Supports searching services by name or ID and resolving escalation policy structures.","intents":["Look up a service by name to get its ID for incident creation or filtering","Understand the structure of an escalation policy (levels, users, notification rules) for decision-making","Find all services managed by a specific team or escalation policy","Build an LLM agent that can recommend the correct escalation policy based on incident type"],"best_for":["Teams building incident routing systems with LLM agents","On-call engineers using AI assistants to navigate service and escalation policy structures","Organizations automating incident creation with context-aware escalation policy selection"],"limitations":["Metadata is static; changes to escalation policies or service configurations require re-querying","No caching mechanism in the MCP server; every query hits the PagerDuty API","Service search is limited to exact name matches or ID lookups; no fuzzy matching or regex support"],"requires":["PagerDuty API token with read access to services and escalation policies","Service name or ID, or escalation policy ID to query","MCP client with tool-calling capability"],"input_types":["service_id or service_name (string), or escalation_policy_id (string)"],"output_types":["JSON object with service details (name, ID, integrations) or escalation policy structure (levels, users, notification rules)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_7","uri":"capability://tool.use.integration.mcp.protocol.tool.registration.and.schema.validation","name":"mcp-protocol-tool-registration-and-schema-validation","description":"Registers PagerDuty operations as MCP tools with JSON Schema validation, ensuring that LLM clients can discover and call PagerDuty functions with type-safe parameters. Implements MCP server that exposes tools with standardized schemas (input/output types, required parameters, descriptions), enabling LLM clients to validate parameters before execution and provide autocomplete in IDE environments.","intents":["Enable Claude, Cline, or other MCP clients to discover PagerDuty operations as callable tools","Validate incident IDs, service IDs, and other parameters before sending to PagerDuty API","Provide IDE autocomplete and type hints for PagerDuty operations in LLM agent code","Ensure LLM agents cannot accidentally call PagerDuty with malformed parameters"],"best_for":["LLM client developers integrating PagerDuty into AI agents","Teams using Claude Desktop or Cline with MCP support","Organizations standardizing on MCP for tool integration across multiple services"],"limitations":["Schema validation is client-side; malicious or non-compliant clients can bypass validation","Tool discovery is static; schema changes require server restart","No runtime parameter validation on the server side; relies on client-side schema enforcement"],"requires":["MCP client that supports tool calling (Claude Desktop, Cline, etc.)","MCP server running and accessible to the client","PagerDuty API token configured in the MCP server environment"],"input_types":["JSON objects conforming to tool schemas"],"output_types":["JSON objects conforming to tool output schemas, or error responses with validation details"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__cap_8","uri":"capability://tool.use.integration.api.authentication.and.token.management","name":"api-authentication-and-token-management","description":"Manages PagerDuty API authentication using bearer tokens, handling token validation and error responses from the PagerDuty API. Implements secure token storage in environment variables or configuration files, with error handling for expired or invalid tokens. Supports token rotation and re-authentication without restarting the MCP server.","intents":["Securely authenticate to PagerDuty API without exposing tokens in code or logs","Handle authentication errors gracefully when tokens expire or are revoked","Rotate API tokens without restarting the MCP server or LLM client","Ensure that all PagerDuty API calls are authenticated with valid credentials"],"best_for":["Teams deploying MCP servers in production environments","Organizations with strict security policies requiring token rotation","DevOps teams managing MCP server infrastructure"],"limitations":["Token storage is environment-dependent; no built-in encryption for tokens at rest","Token rotation requires manual configuration or external secret management system","No token expiration tracking; expired tokens will cause API errors until manually rotated"],"requires":["PagerDuty API token with appropriate permissions","Environment variable or configuration file to store token securely","Network connectivity to PagerDuty API endpoints"],"input_types":["API token (string) provided via environment variable or configuration"],"output_types":["Authentication headers for PagerDuty API requests, or error responses for invalid tokens"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"pagerduty-mcp-server__headline","uri":"capability://tool.use.integration.mcp.server.for.pagerduty.incident.management","name":"mcp server for pagerduty incident management","description":"A community-driven MCP server specifically designed for managing PagerDuty incidents, providing tools for alert acknowledgment, incident listing, and on-call schedule queries, making it ideal for DevOps teams.","intents":["best MCP server for incident management","MCP server for PagerDuty integration","community MCP server for alert management","MCP server for on-call scheduling","MCP server for escalation policies"],"best_for":["DevOps teams","incident management"],"limitations":[],"requires":[],"input_types":[],"output_types":[],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":62,"verified":false,"data_access_risk":"high","permissions":["PagerDuty API token with read access to incidents","MCP client that supports tool calling (Claude Desktop, Cline, etc.)","Network connectivity to PagerDuty API endpoints","PagerDuty API token with write access to incidents","Valid incident ID from PagerDuty","MCP client with tool-calling capability","PagerDuty API token with read access to schedules","Schedule IDs or escalation policy IDs to query","Optional: timezone string (e.g., 'America/New_York') for accurate time-based queries","Valid escalation policy ID from PagerDuty"],"failure_modes":["Pagination is manual — no built-in cursor iteration, requires multiple tool calls for large incident lists","Real-time filtering happens server-side via PagerDuty API; no local caching means latency depends on API response time","Limited to incidents accessible by the API token's service account permissions","Acknowledgment is user-scoped to the API token's service account; cannot acknowledge on behalf of specific on-call engineers","No rollback mechanism — acknowledged incidents cannot be automatically un-acknowledged if the agent makes an error","Notes are appended as incident timeline entries; no structured metadata field for machine-readable context","Schedule data is point-in-time; no real-time updates if an on-call engineer manually changes their availability","Timezone handling depends on PagerDuty account configuration; queries must specify timezone or use account default","Cannot query historical on-call data beyond PagerDuty's retention window (typically 90 days)","Escalation is immediate and irreversible; no dry-run mode to preview escalation before execution","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.8500000000000001,"ecosystem":0.42,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.060Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=pagerduty-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=pagerduty-mcp-server"}},"signature":"t9ZDEh2ywhr8KLWU+N/I1AnrrW0tParHo8UiJFP/PeMBF86OJi70tdpMEmTXvpkaL0jJzaYE697kB4OU9HICDw==","signedAt":"2026-06-15T05:33:38.404Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/pagerduty-mcp-server","artifact":"https://unfragile.ai/pagerduty-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=pagerduty-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}