updated 2026-11-10 04:07 UTC

Pagerduty MCP Server

Repository

PagerDuty's official local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account directly from your MCP-enabled client.

MCP Servers Python Needs review Apache-2.0

Is Pagerduty MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.8 / 10
Provenance None
Signed commits 23%
Last push 67d ago
Compare Pagerduty MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Pagerduty MCP Server scores 50.0/100 (Grade C), ranked #1006 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 23% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pagerduty MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships Pagerduty MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/PagerDuty/pagerduty-mcp-server, Apache-2.0, last pushed 2026-09-04. 23% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Nov 2, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 10
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 10
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • PyPI pagerduty-mcp Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 5.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Pagerduty MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Pagerduty MCP Server compares in MCP Servers

  1. #566 spreadsheet-kit MCP 50.2 +0.2
  2. #567 Brainstorm MCP 50.1 +0.1
  3. #568 Pagerduty MCP Server 50.0 this agent
  4. #569 Reddit Research MCP 50.0 ±0
  5. #570 Storeshots MCP 50.0 ±0

Bars show each HVTrust score; the tick marks Pagerduty MCP Server’s 50.0.

Where the 50.0 comes from

HVTrust dimensions vs the MCP Servers average

50.0 / 100 · 100.0% confidence

Pagerduty MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.1 / 25
3.7 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.5 / 20
4.7 below avg 12.2
AdoptionLog-scaled stars · package downloads
11.0 / 20
3.4 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-17
Rank Moved
Rank dropped 11 spots (#966 → #977)
2026-10-16
Rank Moved
Rank dropped 11 spots (#955 → #966)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 67 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent
View MCP Servers Report missing data
34.8
Activity sub-score · out of 100
#568
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 67 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
79
Forks
42
Last Push
2026-09-04
67 days ago
Commits (4 wk)
0
Downloads (7d)
64,396
pypi
HN mentions (30d)
—
Open Issues
21
Rank Change
=
was #1006

Analysis

Activity Inputs

34.8 / 100
StarsRepository reach
11.4 / 30
FreshnessLast push recency
15.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.6 / 20

Common questions about Pagerduty MCP Server

Public trust evidence for Pagerduty MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Pagerduty MCP Server publish package provenance?
No published build provenance is currently detected for Pagerduty MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pagerduty MCP Server have an OpenSSF Scorecard?
Pagerduty MCP Server has an OpenSSF Scorecard score of 4.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Pagerduty MCP Server actively maintained?
Slowing down. Last push was 67 days ago — keep an eye on whether activity resumes.
What license does Pagerduty MCP Server use?
Pagerduty MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pagerduty MCP Server's commits signed?
23% of the last 100 commits to Pagerduty MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Pagerduty MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Pagerduty MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Pagerduty MCP Server?

For maintainers

HVTrust scores Pagerduty MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 25Warning Issued 4HVTrust 3Score 2Grade 2Warning Cleared 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-17
Rank Moved
Rank dropped 11 spots (#966 → #977)
2026-10-16
Rank Moved
Rank dropped 11 spots (#955 → #966)
2026-10-09
Rank Moved
Rank dropped 16 spots (#912 → #928)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-04
Rank Moved
Rank dropped 58 spots (#839 → #897)
2026-10-04
Activity Score Changed
Activity score down 6pts (46 → 40)
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-26
Rank Moved
Rank dropped 33 spots (#775 → #808)
2026-09-25
Rank Moved
Rank dropped 19 spots (#756 → #775)
2026-09-24
Rank Moved
Rank dropped 25 spots (#731 → #756)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 175 spots (#906 → #731)
2026-09-23
HVTrust Changed
HVTrust up 29.7pts (26.7 → 56.4)
2026-09-22
Newly Listed
First tracked at rank #906
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank rose 63 spots (#763 → #700)
2026-09-11
Rank Moved
Rank dropped 10 spots (#755 → #765)
2026-09-09
Rank Moved
Rank dropped 14 spots (#735 → #749)
2026-09-07
Rank Moved
Rank dropped 40 spots (#686 → #726)
2026-09-06
Rank Moved
Rank dropped 18 spots (#668 → #686)
2026-09-05
Rank Moved
Rank dropped 136 spots (#532 → #668)
2026-09-04
Warning Issued
Warning: eligibility issues detected
2026-09-03
Rank Moved
Rank dropped 68 spots (#462 → #530)
2026-09-02
Rank Moved
Rank dropped 14 spots (#448 → #462)
2026-09-01
Rank Moved
Rank dropped 11 spots (#437 → #448)
2026-08-31
Rank Moved
Rank dropped 35 spots (#402 → #437)
2026-08-30
Scorecard Added
OSSF Scorecard: 5.6/10
2026-08-30
Grade Changed
Trust grade D → C
2026-08-30
Rank Moved
Rank rose 574 spots (#976 → #402)
2026-08-30
HVTrust Changed
HVTrust up 27.1pts (31.7 → 58.8)
2026-08-29
Rank Moved
Rank dropped 48 spots (#928 → #976)
2026-08-28
Rank Moved
Rank dropped 38 spots (#890 → #928)
2026-08-27
Rank Moved
Rank dropped 23 spots (#867 → #890)
2026-08-26
Rank Moved
Rank dropped 111 spots (#756 → #867)
2026-08-25
Rank Moved
Rank rose 45 spots (#801 → #756)
2026-08-25
HVTrust Changed
HVTrust up 3.7pts (27.8 → 31.5)
2026-08-25
Activity Score Changed
Activity score up 14pts (38 → 53)
2026-08-16
Rank Moved
Rank dropped 14 spots (#787 → #801)
GitHub → PyPI: pagerduty-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/pagerduty-mcp-server.svg)](https://hvtracker.net/agents/pagerduty-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/pagerduty-mcp-server"><img src="https://hvtracker.net/badge/pagerduty-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON