Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/pagerduty

PYPI · MCPARMORY-PAGERDUTY · 2 COMPONENTS · SCANNED SEP 20

Manage incidents, on-call schedules, escalation policies, and alert notifications

0 this week 37 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Install-script risk not yet assessed.Unverified
  • 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
  • Stability not yet verified: the captured schema was too large for us to store in full, and comparing a partial copy would report our own trimming as a change.Unverified
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full, and the trim removes the very descriptions this category reads.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the com.mcparmory/pagerduty MCP server?

com.mcparmory/pagerduty runs locally as a PyPI package, launched with uvx mcparmory-pagerduty. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-pagerduty

# add to Claude Code
claude mcp add com-mcparmory-pagerduty -- uvx mcparmory-pagerduty
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-pagerduty": {
      "command": "uvx",
      "args": [
        "mcparmory-pagerduty"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-pagerduty": {
      "command": "uvx",
      "args": [
        "mcparmory-pagerduty"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-pagerduty -- uvx mcparmory-pagerduty
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-pagerduty": {
      "type": "local",
      "command": [
        "uvx",
        "mcparmory-pagerduty"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcparmory-pagerduty --command uvx --arg mcparmory-pagerduty
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-pagerduty:
    command: "uvx"
    args: ["mcparmory-pagerduty"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-pagerduty": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcparmory-pagerduty"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mcparmory-pagerduty -t stdio -c uvx -a mcparmory-pagerduty
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-pagerduty": {
      "command": "uvx",
      "args": [
        "mcparmory-pagerduty"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Sept 26 +15
    • Malware scan: unverified → pass security
  • 17 Sept 26 −15
    • Malware scan: pass → unverified security
  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 31 Aug 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
  • 26 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Aug 26 0
    • Malware scan: unverified → pass security
  • 11 Aug 26 0
    • Malware scan: pass → unverified security
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/mcparmory-pagerduty@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Dependencies 46 packages
Packages resolved 46
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 342 exposed · ~56,260 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_status_page_severities ~128

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
post_typestring

No output schema declared.

No examples provided.

list_status_page_statuses ~121

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
post_typestring

No output schema declared.

No examples provided.

list_status_page_subscriptions ~127

No description provided.

NameTypeReqDescription
Acceptstringyes
channelstring
idstringyes
statusstring

No output schema declared.

No examples provided.

list_status_pages ~101

No description provided.

NameTypeReqDescription
Acceptstringyes
status_page_typestring

No output schema declared.

No examples provided.

list_supporting_service_impacts ~179

No description provided.

NameTypeReqDescription
Acceptstringyes
additional_fieldsstring
idstringyes
idsstring

No output schema declared.

No examples provided.

list_tags ~85

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes

No output schema declared.

No examples provided.

list_tags_for_entity ~148

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
entity_typestringyes
idstringyes

No output schema declared.

No examples provided.

list_team_members ~124

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
includestring

No output schema declared.

No examples provided.

list_team_notification_subscriptions ~79

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes

No output schema declared.

No examples provided.

list_teams ~92

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes

No output schema declared.

No examples provided.

list_teams_audit_records ~185

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
sincestring
untilstring

No output schema declared.

No examples provided.

list_template_fields ~86

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes

No output schema declared.

No examples provided.

list_templates ~99

No description provided.

NameTypeReqDescription
sort_bystring
template_typestring

No output schema declared.

No examples provided.

list_user_audit_records ~196

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
sincestring
untilstring

No output schema declared.

No examples provided.

list_user_contact_methods ~103

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes

No output schema declared.

No examples provided.

list_user_notification_rules ~204

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
includestring
urgencystring

No output schema declared.

No examples provided.

list_user_notification_subscriptions ~80

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes

No output schema declared.

No examples provided.

list_user_oauth_delegations ~180

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
delegation_typestring
idstringyes
statusstring

No output schema declared.

No examples provided.

list_users ~167

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
includestring
team_idsarray

No output schema declared.

No examples provided.

list_vendors ~100

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes

No output schema declared.

No examples provided.

list_webhook_subscriptions ~137

No description provided.

NameTypeReqDescription
Acceptstringyes
filter_idstring
filter_typestring

No output schema declared.

No examples provided.

list_workflow_integration_connections ~62

No description provided.

NameTypeReqDescription
Acceptstringyes

No output schema declared.

No examples provided.

list_workflow_integration_connections_for_integration ~84

No description provided.

NameTypeReqDescription
Acceptstringyes
integration_idstringyes

No output schema declared.

No examples provided.

list_workflow_integrations ~100

No description provided.

NameTypeReqDescription
Acceptstringyes
include_deprecatedboolean

No output schema declared.

No examples provided.

merge_incidents ~177

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
Fromstringyes
idstringyes
source_incidentsarrayyes

No output schema declared.

No examples provided.

move_integration_between_orchestrations ~194

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
integration_idstringyes
source_idstringyes
source_typestringyes

No output schema declared.

No examples provided.

preview_schedule ~192

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
overflowboolean
scheduleobjectyes
sincestring
untilstring

No output schema declared.

No examples provided.

remove_automation_action_service_association ~120

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
service_idstringyes

No output schema declared.

No examples provided.

remove_automation_action_team_association ~122

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
team_idstringyes

No output schema declared.

No examples provided.

remove_business_service_account_subscription ~89

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes

No output schema declared.

No examples provided.

remove_business_service_notification_subscribers ~112

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
subscribersarrayyes

No output schema declared.

No examples provided.

remove_escalation_policy_from_team ~148

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
escalation_policy_idstringyes
idstringyes

No output schema declared.

No examples provided.

remove_incident_notification_subscribers ~98

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
subscribersarrayyes

No output schema declared.

No examples provided.

remove_runner_from_team ~117

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
team_idstringyes

No output schema declared.

No examples provided.

remove_service_dependencies ~112

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
relationshipsarray

No output schema declared.

No examples provided.

remove_service_from_incident_workflow_trigger ~136

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
service_idstringyes
trigger_idstringyes

No output schema declared.

No examples provided.

remove_team_notification_subscriptions ~106

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
subscribablesarrayyes

No output schema declared.

No examples provided.

remove_user_from_team ~123

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
user_idstringyes

No output schema declared.

No examples provided.

remove_user_notification_subscriptions ~110

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes
subscribablesarrayyes

No output schema declared.

No examples provided.

render_template ~93

No description provided.

NameTypeReqDescription
bodyobjectyes
idstringyes

No output schema declared.

No examples provided.

revoke_user_oauth_delegations ~166

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
typestringyes
user_idstringyes

No output schema declared.

No examples provided.

send_change_event ~87

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes

No output schema declared.

No examples provided.

send_responder_request_for_incident ~194

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
messagestringyes
requester_idstringyes
responder_request_targetsyes

No output schema declared.

No examples provided.

send_webhook_subscription_test_ping ~82

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes

No output schema declared.

No examples provided.

snooze_incident ~151

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
Fromstringyes
durationintegeryes
idstringyes

No output schema declared.

No examples provided.

subscribe_account_to_business_service ~81

No description provided.

NameTypeReqDescription
Acceptstringyes
idstringyes

No output schema declared.

No examples provided.

update_automation_action ~107

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
actionyes
idstringyes

No output schema declared.

No examples provided.

update_automation_actions_runner ~127

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
idstringyes
runneryes

No output schema declared.

No examples provided.

update_business_service ~168

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
descriptionstring
idstringyes
point_of_contactstring
teamIdstring

No output schema declared.

No examples provided.

update_cache_variable_data ~156

No description provided.

NameTypeReqDescription
Acceptstringyes
Content-Typestringyes
cache_variable_datastringyes
cache_variable_idstringyes
service_idstringyes

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/pagerduty MCP server?

com.mcparmory/pagerduty is an MCP server listed in the public MCP registry as com.mcparmory/pagerduty. Manage incidents, on-call schedules, escalation policies, and alert notifications. This page covers its PyPI package (mcparmory-pagerduty).

Is the com.mcparmory/pagerduty MCP server safe to use?

com.mcparmory/pagerduty scores 37 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the com.mcparmory/pagerduty MCP server still maintained?

com.mcparmory/pagerduty is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.