Is Pagerduty MCP Server safe to use?

Pagerduty MCP Server has an HVTrust score of 57.5/100 (Grade C), ranked #529 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pagerduty MCP Server?

Pagerduty MCP Server scores 57.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 77 GitHub stars and is categorized under MCP Servers.

Pagerduty MCP Server

PagerDuty/pagerduty-mcp-server

PagerDuty's official local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty acco

MCP Servers Python Grade C Needs review Apache-2.0

57.5/100

Rank #529 of 1320

Compare Pagerduty MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

Warning +10

Is Pagerduty MCP Server safe? Pagerduty MCP Server scores 57.5/100 (Grade C), ranked #529 of 1320 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 5.6/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 →

Ranked neighbours in MCP Servers

#243 Cyberbro MCP Server — 57.6 (C) → #244 ARC-1 — 57.6 (C) → #246 SearXNG HTTP MCP — 57.4 (C) → #247 Awesome Copilot MCP Server — 57.3 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/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.

Review Flags

[5.1] repository is archived

Compare with another agent Get email alerts for Pagerduty MCP Server View MCP Servers Report missing data

55.8

Activity sub-score · out of 100

#245

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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

24,252

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #530

Analysis

HVTrust Dimensions vs MCP Servers

57.5 / 100 · 100.0% confidence

Pagerduty MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.1 / 25

1.5 below avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.5 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

13.9 / 20

1.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

10.4 / 20

4.1 above avg 6.3

Activity Inputs

55.8 / 100

StarsRepository reach

11.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

11.9 / 25

CommunityFork signal

7.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

23%

of last 100 commits verified

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 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Pagerduty MCP Server safe?

Pagerduty MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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 5.6/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?

Actively maintained. The repository was pushed to within the last 1 day(s).

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

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

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)

2026-08-10

Rank Moved

Rank dropped 41 spots (#733 → #774)

2026-08-09

Activity Score Changed

Activity score down 6pts (50 → 44)

2026-08-08

Newly Listed

First tracked at rank #719

GitHub → PyPI: pagerduty-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON