ToolsMCP
pagerduty
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- mcparmory.com
- Prerequisites
- Install mcparmory-pagerduty from pypi (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.2 · updated
- Official links
Publisher’s description
Manage incidents, on-call schedules, escalation policies, and alert notifications
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.2, registry status active. 2 packages (pypi, oci)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- mcparmory.com
- Version observed
- 1.0.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.mcparmory%2Fpagerduty/versions/1.0.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Investigate errors and incidents | Publisher description mentions “pagerduty”, “incidents”, “alert”. | No connection check or task run. Capability is as described by the publisher. | Rule observability matched: “pagerduty”, “incidents”, “alert”. Rule observability. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
mcparmory-pagerduty(pypi, stdio)ghcr.io/mcparmory/pagerduty:1.0.2(oci, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.mcparmory/pagerduty
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.