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

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

+11 this week 53 Trust /100

Last scanned (3 hours ago)

Scores higher than 56% of PyPI servers

Category Monitoring and Observability

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, 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 (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 3 categories

Categories scored 0 because our sandbox 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 →

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.

  • 5 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −5
    • Stability: pass → 0.67 functional
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 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
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 45 packages
Packages resolved 45
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
update_cache_variable_external_data ~164

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
cache_variable_datastringyes–
cache_variable_idstringyes–
idstringyes–

No output schema declared.

No examples provided.

update_cache_variable_for_global_orchestration ~147

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
cache_variable–yes–
cache_variable_idstringyes–
idstringyes–

No output schema declared.

No examples provided.

update_cache_variable_for_service_orchestration ~143

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
cache_variable–yes–
cache_variable_idstringyes–
service_idstringyes–

No output schema declared.

No examples provided.

update_change_event ~115

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
change_eventobjectyes–
idstringyes–

No output schema declared.

No examples provided.

update_custom_shift ~234

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
assignmentsarray––
custom_shift_idstringyes–
end_timestring––
idstringyes–
start_timestring––

No output schema declared.

No examples provided.

update_escalation_policy ~130

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
escalation_policyobjectyes–
idstringyes–

No output schema declared.

No examples provided.

update_event_orchestration_feature_enablement ~160

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
enabledbooleanyes–
feature_namestringyes–
idstringyes–

No output schema declared.

No examples provided.

update_event_orchestration_integration ~144

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
integration_idstringyes–
labelstringyes–

No output schema declared.

No examples provided.

update_extension ~96

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
extensionobjectyes–
idstringyes–

No output schema declared.

No examples provided.

update_incident ~497

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
assignmentsarray––
conference_numberstring––
conference_urlstring––
escalation_levelinteger––
escalation_policyobject––
idstringyes–
incidentTypestringyes–
priorityobject––
resolutionstring––
serviceIdstringyes–
serviceTypestringyes–
statusstring––
titlestring––
urgencystring––

No output schema declared.

No examples provided.

update_incident_alert ~224

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
alert_idstringyes–
idstringyes–
incidentIdstringyes–
statusstring––

No output schema declared.

No examples provided.

update_incident_alerts ~176

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
alertsarrayyes–
idstringyes–

No output schema declared.

No examples provided.

update_incident_business_service_impact ~137

No description provided.

NameTypeReqDescription
Acceptstringyes–
business_service_idstringyes–
idstringyes–
relationstringyes–

No output schema declared.

No examples provided.

update_incident_custom_field_values ~83

No description provided.

NameTypeReqDescription
custom_fieldsarrayyes–
idstringyes–

No output schema declared.

No examples provided.

update_incident_note ~155

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
contentstringyes–
idstringyes–
note_idstringyes–

No output schema declared.

No examples provided.

update_incident_type ~183

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
descriptionstring––
display_namestring––
enabledboolean––
type_id_or_namestringyes–

No output schema declared.

No examples provided.

update_incident_type_custom_field ~279

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
default_valuestring––
descriptionstring––
display_namestring––
enabledboolean––
field_idstringyes–
field_optionsarray––
type_id_or_namestringyes–

No output schema declared.

No examples provided.

update_incident_type_custom_field_option ~195

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
data_typestringyes–
field_idstringyes–
field_option_idstringyes–
type_id_or_namestringyes–
valuestringyes–

No output schema declared.

No examples provided.

update_incidents ~178

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
incidentsarrayyes–

No output schema declared.

No examples provided.

update_log_entry_channel ~174

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
detailsstringyes–
idstringyes–
typestringyes–

No output schema declared.

No examples provided.

update_maintenance_window ~124

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
maintenance_windowobjectyes–

No output schema declared.

No examples provided.

update_rotation_event ~520

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
effective_sincestring––
effective_untilstring––
end_timeDate_timestringyes–
end_timeTime_zonestringyes–
event_idstringyes–
idstringyes–
membersarrayyes–
recurrencearray––
rotation_idstringyes–
shifts_per_memberinteger––
start_timeDate_timestringyes–
start_timeTime_zonestringyes–
typestringyes–

No output schema declared.

No examples provided.

update_schedule ~162

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
descriptionstring––
idstringyes–
time_zonestring––

No output schema declared.

No examples provided.

update_schedule_override ~251

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
end_timestring––
idstringyes–
override_idstringyes–
start_timestring––
typestringyes–
user_idstring––

No output schema declared.

No examples provided.

update_service ~138

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
serviceobjectyes–

No output schema declared.

No examples provided.

update_service_custom_field ~220

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
descriptionstring––
display_namestring––
enabledboolean––
field_idstringyes–
field_optionsarray––

No output schema declared.

No examples provided.

update_service_custom_field_values ~134

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
custom_fieldsarrayyes–
idstringyes–

No output schema declared.

No examples provided.

update_service_feature_enablement ~160

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
enabledbooleanyes–
feature_namestringyes–
idstringyes–

No output schema declared.

No examples provided.

update_service_integration ~150

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
integration–yes–
integration_idstringyes–

No output schema declared.

No examples provided.

update_service_orchestration_active_status ~160

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
activeboolean––
service_idstringyes–

No output schema declared.

No examples provided.

update_sre_memory ~123

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
contentstringyes–
idstringyes–

No output schema declared.

No examples provided.

update_standard ~113

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
bodyobject––
idstringyes–

No output schema declared.

No examples provided.

update_status_page_post ~279

No description provided.

NameTypeReqDescription
Acceptstringyes–
ends_atstring––
idstringyes–
post_idstringyes–
post_typestringyes–
starts_atstring––
status_pageIdstringyes–
titlestringyes–
typestringyes–

No output schema declared.

No examples provided.

update_status_page_post_postmortem ~183

No description provided.

NameTypeReqDescription
Acceptstringyes–
idstringyes–
messagestringyes–
notify_subscribersbooleanyes–
postIdstringyes–
post_idstringyes–

No output schema declared.

No examples provided.

update_status_page_post_update ~327

No description provided.

NameTypeReqDescription
Acceptstringyes–
idstringyes–
impacted_servicesarrayyes–
messagestringyes–
notify_subscribersbooleanyes–
postIdstringyes–
post_idstringyes–
post_update_idstringyes–
reported_atstring––
severityIdstringyes–
statusIdstringyes–
typestringyes–
update_frequency_msinteger––

No output schema declared.

No examples provided.

update_team ~111

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
teamobjectyes–

No output schema declared.

No examples provided.

update_template ~167

No description provided.

NameTypeReqDescription
descriptionstring––
email_bodystring––
email_subjectstring––
idstringyes–
messagestring––
template_typestring––

No output schema declared.

No examples provided.

update_user ~140

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
userobjectyes–

No output schema declared.

No examples provided.

update_user_contact_method ~151

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
contact_method–yes–
contact_method_idstringyes–
idstringyes–

No output schema declared.

No examples provided.

update_user_notification_rule ~143

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
notification_ruleobjectyes–
notification_rule_idstringyes–

No output schema declared.

No examples provided.

update_webhook_subscription ~216

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
activeboolean––
descriptionstring––
eventsarray––
filterIdstring––
idstringyes–
oauth_client_idstring––

No output schema declared.

No examples provided.

update_workflow_integration_connection ~338

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
appsarray––
configurationobject––
external_idstring––
external_id_labelstring––
idstringyes–
integration_idstringyes–
is_defaultboolean––
namestringyes–
scopesarray––
secretsobjectyes–
service_urlstring––
teamsarray––

No output schema declared.

No examples provided.

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
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 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.mcparmory/pagerduty MCP server under?

com.mcparmory/pagerduty declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.