com.mcparmory/pagerduty
PagerDuty
Is the com.mcparmory/pagerduty MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-10.
Manage incidents, on-call schedules, escalation policies, and alert notifications
alive probed 2026-11-15 · unchanged since 2026-11-10
- Run it
- uvx mcparmory-pagerduty@1.0.2 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- PagerDuty 4.1.7
- Capabilities
- logging, prompts, resources, tools
- Instructions
- none
- Of a 1M window
- 17.7 % of a 1M context window
- Count
- 177k tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 180k. The o200k_base estimate is 102k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/mcparmory/registry
- Registry
- active, updated 2026-05-12 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.73×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| create_service | 5 610 | 3 246 | 3 % |
| update_service | 5 527 | 3 198 | 3 % |
| preview_schedule | 3 278 | 1 897 | 2 % |
| update_cache_variable_for_global_orchestration | 2 848 | 1 648 | 2 % |
| update_cache_variable_for_service_orchestration | 2 843 | 1 645 | 2 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- com.mcparmory/netlicensing · alive
- com.mcparmory/notion · crashed on start
- com.mcparmory/opencage-geocoding · alive
- com.mcparmory/outline · alive
- com.mcparmory/parallel · alive
- com.mcparmory/pdfco · alive
- com.mcparmory/perigon · alive
- com.mcparmory/perplexity · alive
Servers that mention pagerduty.
- Release Radar MCP by usefulapi io.usefulapi/release-radar · timeout
- io.github.PagerDuty/pagerduty-mcp · crashed on start
- io.github.NotHarshhaa/devops-mcp · alive
- PagerDuty MCP io.github.Servosity/pagerduty-mcp · needs env
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 06:52 | alive | 3.7 s | 342 | 177k | 102k |
| 2026-10-20 06:39 | alive | 14.4 s | 342 | 102k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.