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

OCI · GHCR.IO/MCPARMORY/PAGERDUTY:1.0.2 · 2 COMPONENTS

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

0 this week 24 Trust /100

Last scanned (1 hour ago)

Scores higher than 36% of OCI 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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 4 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Provenance: unverified → fail ▼ security
    • Stability: pass → 0.97 functional
  • 30 Oct 26 0
    • Provenance: fail → unverified ▼ security
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 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.

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 oci/ghcr.io/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 oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

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
add_and_remove_tags_for_entity ~205

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
addarray––
entity_typestringyes–
idstringyes–
removearray––

No output schema declared.

No examples provided.

add_automation_action_team ~116

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
teamobjectyes–

No output schema declared.

No examples provided.

add_escalation_policy_to_team ~149

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
escalation_policy_idstringyes–
idstringyes–

No output schema declared.

No examples provided.

add_incident_status_update_subscribers ~136

No description provided.

NameTypeReqDescription
Acceptstringyes–
idstringyes–
subscribersarrayyes–

No output schema declared.

No examples provided.

add_note_to_incident ~159

No description provided.

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

No output schema declared.

No examples provided.

add_service_to_incident_workflow_trigger ~114

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
serviceIdstring––

No output schema declared.

No examples provided.

add_subscribers_to_business_service ~118

No description provided.

NameTypeReqDescription
Acceptstringyes–
idstringyes–
subscribersarrayyes–

No output schema declared.

No examples provided.

add_user_to_team ~171

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
rolestring––
user_idstringyes–

No output schema declared.

No examples provided.

associate_automation_action_with_service ~148

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
serviceobjectyes–

No output schema declared.

No examples provided.

associate_runner_with_team ~127

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
teamobjectyes–

No output schema declared.

No examples provided.

associate_service_dependencies ~127

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
relationshipsarray––

No output schema declared.

No examples provided.

cancel_incident_responder_requests ~175

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
requester_idstringyes–
responder_request_targetsarrayyes–

No output schema declared.

No examples provided.

check_account_ability ~122

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–

No output schema declared.

No examples provided.

create_automation_action ~127

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
action–yes–

No output schema declared.

No examples provided.

create_automation_runner ~120

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
runner–yes–

No output schema declared.

No examples provided.

create_business_service ~150

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
descriptionstring––
idstring––
point_of_contactstring––

No output schema declared.

No examples provided.

create_cache_variable_for_global_orchestration ~135

No description provided.

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

No output schema declared.

No examples provided.

create_cache_variable_for_service_orchestration ~122

No description provided.

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

No output schema declared.

No examples provided.

create_custom_shifts ~154

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
custom_shiftsarrayyes–
idstringyes–

No output schema declared.

No examples provided.

create_escalation_policy ~144

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstring––
escalation_policyobjectyes–

No output schema declared.

No examples provided.

create_event_orchestration ~177

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
descriptionstring––
idstring––

No output schema declared.

No examples provided.

create_extension ~113

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
extensionobjectyes–

No output schema declared.

No examples provided.

create_incident ~469

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
assignmentsarray––
conference_numberstring––
conference_urlstring––
detailsobject––
escalation_policyobject––
incident_keystring––
priorityobject––
serviceobjectyes–
titlestringyes–
typestringyes–
urgencystring––

No output schema declared.

No examples provided.

create_incident_status_update ~215

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
html_messagestring––
idstringyes–
messagestringyes–
subjectstring––

No output schema declared.

No examples provided.

create_incident_type ~215

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
descriptionstring––
display_namestringyes–
enabledboolean––
namestringyes–
parent_typestringyes–

No output schema declared.

No examples provided.

create_incident_type_custom_field ~317

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
data_typestringyes–
default_valuestring––
descriptionstring––
display_namestringyes–
enabledboolean––
field_optionsarray––
field_typestringyes–
namestringyes–
type_id_or_namestringyes–

No output schema declared.

No examples provided.

create_incident_type_custom_field_option ~182

No description provided.

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

No output schema declared.

No examples provided.

create_incident_workflow_instance ~154

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
incidentIdstringyes–
incident_workflow_instanceIdstring––

No output schema declared.

No examples provided.

create_integration_for_event_orchestration ~164

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–
labelstringyes–

No output schema declared.

No examples provided.

create_maintenance_window ~147

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
maintenance_windowobjectyes–

No output schema declared.

No examples provided.

create_post_update_for_status_page_post ~333

No description provided.

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

No output schema declared.

No examples provided.

create_postmortem_for_status_page_post ~219

No description provided.

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

No output schema declared.

No examples provided.

create_rotation_event ~538

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
effective_sincestringyes–
effective_untilstring––
end_timeDate_timestringyes–
end_timeTime_zonestringyes–
idstringyes–
membersarrayyes–
namestringyes–
recurrencearrayyes–
rotation_idstringyes–
shifts_per_memberinteger––
start_timeDate_timestringyes–
start_timeTime_zonestringyes–
typestringyes–

No output schema declared.

No examples provided.

create_rotation_for_schedule ~139

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
bodyobject––
idstringyes–

No output schema declared.

No examples provided.

create_schedule ~186

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
descriptionstring––
namestringyes–
teamsarray––
time_zonestringyes–

No output schema declared.

No examples provided.

create_schedule_overrides ~156

No description provided.

NameTypeReqDescription
X-EARLY-ACCESSstringyes–
idstringyes–
overridesarrayyes–

No output schema declared.

No examples provided.

create_service ~189

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
serviceobjectyes–

No output schema declared.

No examples provided.

create_service_custom_field_option ~161

No description provided.

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

No output schema declared.

No examples provided.

create_service_integration ~119

No description provided.

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

No output schema declared.

No examples provided.

create_status_page_post ~293

No description provided.

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

No output schema declared.

No examples provided.

create_status_page_subscription ~244

No description provided.

NameTypeReqDescription
Acceptstringyes–
channelstringyes–
contactstringyes–
idstringyes–
status_pageIdstringyes–
subscribable_objectIdstring––
typestringyes–

No output schema declared.

No examples provided.

create_status_update_template ~150

No description provided.

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

No output schema declared.

No examples provided.

create_tag ~119

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
tagobjectyes–

No output schema declared.

No examples provided.

create_team ~116

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
teamobjectyes–

No output schema declared.

No examples provided.

create_user ~135

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
Fromstringyes–
userobjectyes–

No output schema declared.

No examples provided.

create_user_contact_method ~147

No description provided.

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

No output schema declared.

No examples provided.

create_user_notification_subscriptions ~122

No description provided.

NameTypeReqDescription
Acceptstringyes–
idstringyes–
subscribablesarrayyes–

No output schema declared.

No examples provided.

create_workflow_integration_connection ~376

No description provided.

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

No output schema declared.

No examples provided.

delete_automation_action ~98

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–

No output schema declared.

No examples provided.

delete_automation_actions_runner ~100

No description provided.

NameTypeReqDescription
Acceptstringyes–
Content-Typestringyes–
idstringyes–

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 container image, launched with docker run --rm -i ghcr.io/mcparmory/pagerduty:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mcparmory/pagerduty:1.0.2

# add to Claude Code
claude mcp add com-mcparmory-pagerduty -- docker run --rm -i ghcr.io/mcparmory/pagerduty:1.0.2
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 container image (ghcr.io/mcparmory/pagerduty:1.0.2).

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

com.mcparmory/pagerduty scores 24 out of 100 on VerifyMCP. 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.