"PagerDuty" matching MCP tools:

• get_outage_alertsA

  hyperpingA

  Who was notified for one outage, and how: every alert delivery attempt (time, channel email/sms/phonecall/slack/teams/webhook/pagerduty/opsgenie/…, recipient: user name and email, phone as its last 4 digits, or the integration name; down or up; escalation step) with its status: sent, failed (+ error) or suppressed (+ reason: grouped alerts, quiet hours, SMS flapping/delay, email daily cap). Also the escalation policy, the acknowledgement, mutes and maintenance windows that covered it, and a summary. Use it to answer "why wasn't I alerted?" for an outage_ uuid from list_outages; get_outage_timeline tells the incident's story. 100 deliveries by default, max 300 (truncated flag).

  ConnectorNo auth

• list_alert_channelsA

  monit.rsA

  List alert channels configured on the authenticated account. Does NOT return decrypted config (webhook URLs, PagerDuty routing keys, etc.). Use the dashboard or `describe_alert_channel` HTTP API when you need to inspect the actual config.

  ConnectorNo auth

• query_eventsA

  PlutusA

  Query this account's business-event timeline (GitHub releases/PRs, PagerDuty incidents, Jira issues, GitLab, Salesforce onboarding/churn, Stripe subscription created/canceled, Vercel production deploys, Linear issue creation, Sentry newly reported errors) — the same events overlaid on the Cost/Event Explorer charts. Always scope with start_date/end_date: there is no pagination and results are capped at 5000 rows (oldest-first), so an unscoped query over a long history may be silently truncated. Carries no cost figure. Mirrors GET /api/events.

  ConnectorNo auth

• create_notification_channelA

  email-deliverabilityA

  Create a channel that InboxGuard alerts are delivered to: webhook (HMAC-signed), Slack, Microsoft Teams, PagerDuty, SMS, or email. Returns the channel id, and for kind=webhook the `signing_secret` used to verify deliveries. Requires an owner/admin API key with write or full scope.

  ConnectorNo auth

• listIntegrationStatusesA

  CortexC

  List every integration installed in this workspace (GitHub, Jira, PagerDuty, Slack, etc.) with the result of its most recent connection check. Use to find integrations whose credentials are failing (INVALID) or have not been checked recently (UNKNOWN). lastValidatedAt is when the connection was last checked, not when data was last synced, so do not report it as data freshness. message is null unless the caller has the Manage Integrations permission.

  ConnectorNo auth

• create_alert_channelA

  monit.rsA

  Create an alert channel. Pass EXACTLY one of email_address / webhook_url / pagerduty_routing_key matching the channel_type: - channel_type='email' → email_address='ops@example.com' - channel_type='webhook' → webhook_url='https://your-endpoint' - channel_type='slack' → webhook_url='https://hooks.slack.com/...' - channel_type='pagerduty' → pagerduty_routing_key='<Events v2 key>'

  ConnectorNo auth

• list_integrationsA

  hyperpingA

  All notification integrations in the project (Slack, Telegram, Discord, PagerDuty, OpsGenie, Teams, webhook, etc.).

  ConnectorNo auth

• checkly_list_alert_channels

  Checkly MCP by usefulapiB

  List all alert channels (email, Slack, webhook, PagerDuty, etc.) configured in the account. Public API: GET /v1/alert-channels.

  ConnectorNo auth

• whats_broken_since_last_deploy

  Release Radar MCP by usefulapiA

  COMPOSITE. Finds the latest GitHub deployment/release for a repo, then queries Sentry for unresolved issues SINCE that deploy's timestamp (the deploy time drives the Sentry window), then looks up who's currently on-call in PagerDuty — and synthesizes one situational-awareness object. Degrades gracefully: if Sentry or PagerDuty creds are absent it returns what it can plus a note. GitHub is required (it's the anchor).

  ConnectorNo auth

• incident_snapshot

  Release Radar MCP by usefulapiA

  COMPOSITE. A right-now on-call picture: top unresolved Sentry issues + active (triggered/acknowledged) PagerDuty incidents + who's currently on-call, fused into one snapshot with a human summary. Each service degrades independently if its creds are missing.

  ConnectorNo auth

• oncall_handoff

  Release Radar MCP by usefulapiA

  COMPOSITE. A start-of-shift briefing for whoever is currently on call, fusing all three services: (a) PagerDuty current on-call + any active (triggered/acknowledged) incidents they're inheriting, (b) the GitHub deployment/release that most recently shipped (what's live), and (c) Sentry's top unresolved errors. Correlates them into one object — including a heads-up when a fresh deploy coincides with active incidents (a likely culprit). Degrades gracefully: every service is optional; whatever's unconfigured or failing is named in `notes` and the briefing still returns. Never crashes.

  ConnectorNo auth