fix(mcp): update pagerduty-mcp to v1.0.0, add mock_env for scan (#735)

* chore(deps): update dependency pagerduty-mcp to v1

* fix(mcp): add mock_env for pagerduty-mcp security scan

pagerduty-mcp v1 creates the PagerDuty client eagerly at startup
(ApplicationContextStrategy.__init__ -> create_pd_client()), raising
RuntimeError without PAGERDUTY_USER_API_KEY set. This prevented
mcp-security-scan from connecting to the server at all. Add a mock
credential so the scanner can launch and enumerate tools, matching
the existing pattern used by pinecone-mcp/launchdarkly-mcp-server/etc.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Author: 3 people

uvx/pagerduty-mcp/spec.yaml

@@ -11,13 +11,21 @@ metadata:
 
 spec:
   package: "pagerduty-mcp"
-  version: "0.17.0"
+  version: "1.0.0"
 
 provenance:
   repository_uri: "https://github.com/PagerDuty/pagerduty-mcp-server"
   repository_ref: "refs/heads/main"  # Using main branch as the primary development branch
 
 security:
+  # Mock env vars allow security scanning without real credentials. pagerduty-mcp
+  # v1 creates the PagerDuty client eagerly at startup and raises RuntimeError
+  # without an API key, which previously prevented the scanner from connecting
+  # to the server at all.
+  mock_env:
+    - name: PAGERDUTY_USER_API_KEY
+      value: "mock-pagerduty-api-key-for-scanning"
+      description: "PagerDuty API key — mock value for security scanning"
   allowed_issues:
     - code: "AITech-8.2"
       reason: "Data leak risk acceptable - incident management requires sharing operational data with responders and creating public status updates. Write operations are disabled by default, requiring explicit opt-in with --enable-write-tools flag."