{"slug": "pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2", "title": "PagerDuty MCP (io.github.Servosity/pagerduty-mcp@0.1.2)", "summary": "PagerDuty MCP (io.github.Servosity/pagerduty-mcp@0.1.2), a server that lets AI agents operate PagerDuty via the Model Context Protocol, was published to the official MCP registry on 2026-08-27, according to the mcpindex tracking index. The index's semantic screen found no manipulation pattern in the server's description, but the deterministic conformance probe has not yet been run, and the index advises caution because the screen reads only the description, not live behavior.", "body_md": "[← Index](/leaderboard)\n\n# PagerDuty MCP\n\nOperate PagerDuty from your AI agent via MCP.\n\nThe current version, v0.1.2, was published to the official MCP registry on 2026-08-27. It is distributed through a declared package, filed under Monitoring & Logs by this index, and declares 2 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context.\n\n## Using PagerDuty MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?\n\nMCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that).\n\nRewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less\n\n```\nuv tool install mcpindex-gate && mcpindex-config-wire\n```\n\n[method](/methodology)\n\nSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.\n\n`mcpindex.integrity.description`\n\npassINFOevidence“No malicious instructions found”via static_description\n\n- - Semantic screen only - the deterministic conformance probe has not run on this server\n- - Confidence is reported but not yet calibrated (v1)\n- - Screen reads the tool description, not the live behavior\n- - advisory\n- - registry description only no input schema\n- - screen model 8b\n- - Still current: the description we screened is unchanged, re-checked against the registry\n- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not\n\nSemantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.\n\nOwn this server? [Screen its description →](/screen)\n\n## That verdict was true at screening time (snapshot 2026-08-27).\n\nContracts can change after screening, with no version bump. The gate pins PagerDuty MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.\n\n[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)\n\nRelated: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)\n\nPeople vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.\n\n```\n[Independent trust record for PagerDuty MCP](https://mcpindex.ai/server/io-github-servosity-pagerduty-mcp) - screening verdict, registry provenance, and contract drift monitoring.\nIndependent trust record for PagerDuty MCP - screening verdict, registry provenance, and contract drift monitoring.\n```\n\nA live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.\n\n```\n[](https://mcpindex.ai/server/io-github-servosity-pagerduty-mcp)\n![\"mcpindex](\"https://mcpindex.ai/api/v1/badge/io-github-servosity-pagerduty-mcp\")
\n```\n\n`PAGERDUTY_API_KEY`\n\nSet the PAGERDUTY_API_KEY credential for the PagerDuty MCP server.\n\n`PAGERDUTY_BASE_URL`\n\nBase URL for the PagerDuty API. Leave the prefilled default unless your account uses a different regional or self-hosted host.\n\n[methodology](/methodology)\n\n[Labbyai.dinglebear/labby](/server/ai-dinglebear-labby)\n\nRust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.\n\n[Ledgyapp.ledgy/ledgy](/server/app-ledgy-ledgy)\n\nLog, query, and edit expenses, budgets, and accounts in Ledgy from any MCP-compatible AI assistant.\n\n[io.github.Shreyas-Profile/tor-mcpio.github.Shreyas-Profile/tor-mcp](/server/io-github-shreyas-profile-tor-mcp)\n\nRoute HTTP requests through the Tor network. Rotating exit IPs, .onion support, no body logging.", "url": "https://wpnews.pro/news/pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2", "canonical_source": "https://mcpindex.ai/server/io-github-servosity-pagerduty-mcp", "published_at": "2026-08-27 01:28:53+00:00", "updated_at": "2026-08-27 02:19:44.801942+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents"], "entities": ["PagerDuty", "mcpindex", "MCP registry"], "alternates": {"html": "https://wpnews.pro/news/pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2", "markdown": "https://wpnews.pro/news/pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2.md", "text": "https://wpnews.pro/news/pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2.txt", "jsonld": "https://wpnews.pro/news/pagerduty-mcp-io-github-servosity-pagerduty-mcp-0-1-2.jsonld"}}