com.mcparmory/pagerduty
PYPI · MCPARMORY-PAGERDUTY · 2 COMPONENTS · SCANNED OCT 10
Manage incidents, on-call schedules, escalation policies, and alert notifications
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- 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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 147 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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: 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.
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
claude mcp add com-mcparmory-pagerduty -- uvx mcparmory-pagerduty
{
"mcpServers": {
"com-mcparmory-pagerduty": {
"command": "uvx",
"args": [
"mcparmory-pagerduty"
]
}
}
} {
"servers": {
"com-mcparmory-pagerduty": {
"command": "uvx",
"args": [
"mcparmory-pagerduty"
]
}
}
} codex mcp add com-mcparmory-pagerduty -- uvx mcparmory-pagerduty
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-pagerduty": {
"type": "local",
"command": [
"uvx",
"mcparmory-pagerduty"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-pagerduty --command uvx --arg mcparmory-pagerduty
mcp_servers:
com-mcparmory-pagerduty:
command: "uvx"
args: ["mcparmory-pagerduty"] {
"McpServers": {
"com-mcparmory-pagerduty": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-pagerduty"
]
}
}
} assistant mcp add com-mcparmory-pagerduty -t stdio -c uvx -a mcparmory-pagerduty
{
"mcpServers": {
"com-mcparmory-pagerduty": {
"command": "uvx",
"args": [
"mcparmory-pagerduty"
]
}
}
} 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.
- 29 Sept 26 0
- Provenance: unverified → fail ▼ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- 28 Sept 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 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
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 9 Oct 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 →
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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
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 28 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 October 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 6 October 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.