updated 2026-11-10 04:07 UTC

Dynatrace MCP

Repository by dynatrace-oss

MCP server for Dynatrace Observability

MCP Servers TypeScript Needs review MIT

Is Dynatrace MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10
Provenance Attested
Signed commits 98%
Last push 76d ago
Advisories None known
Compare Dynatrace MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Dynatrace MCP scores 72.5/100 (Grade B), ranked #319 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.1/10; 98% of recent commits are signed; no published advisory affects its latest release (@dynatrace-oss/dynatrace-mcp-server); last pushed 2026-08-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dynatrace MCP 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 Dynatrace MCP 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 Signed

    github.com/dynatrace-oss/dynatrace-mcp, MIT, last pushed 2026-08-26. 98% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protectionn/a
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @dynatrace-oss/dynatrace-mcp-server 2.1.2. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 5.3/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 Dynatrace MCP’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 Dynatrace MCP compares in MCP Servers

  1. #187 Funplay Cocos MCP 72.6 +0.1
  2. #188 Zigbee2MQTT MCP 72.5 ±0
  3. #189 Dynatrace MCP 72.5 this agent
  4. #190 Hunch MCP 72.5 ±0
  5. #191 iCloud MCP 72.5 ±0

Bars show each HVTrust score; the tick marks Dynatrace MCP’s 72.5.

Where the 72.5 comes from

HVTrust dimensions vs the MCP Servers average

72.5 / 100 · 100.0% confidence

Dynatrace MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.8 / 25
8.0 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
6.9 / 20
5.3 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
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-11-08
Rank Moved
Rank rose 22 spots (#335 → #313)
2026-11-07
Rank Moved
Rank rose 10 spots (#345 → #335)
2026-11-02
Rank Moved
Rank dropped 23 spots (#310 → #333)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 76 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.1
Activity sub-score · out of 100
#189
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 B 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 76 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
137
Forks
27
Last Push
2026-08-26
76 days ago
Commits (4 wk)
0
Downloads (7d)
26,895
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼2
was #317

Analysis

Activity Inputs

34.1 / 100
StarsRepository reach
12.8 / 30
FreshnessLast push recency
14.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.7 / 20

Common questions about Dynatrace MCP

Dynatrace MCP 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 Dynatrace MCP publish package provenance?
Yes. Dynatrace MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Dynatrace MCP have an OpenSSF Scorecard?
Dynatrace MCP has an OpenSSF Scorecard score of 5.1/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 Dynatrace MCP actively maintained?
Slowing down. Last push was 76 days ago — keep an eye on whether activity resumes.
What license does Dynatrace MCP use?
Dynatrace MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dynatrace MCP's commits signed?
98% of the last 100 commits to Dynatrace MCP 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
high confidence
Implemented
Dynatrace MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies 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
high confidence
Match
Published package metadata matches the tracked repo
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 Dynatrace MCP'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
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Dynatrace MCP?

For maintainers

HVTrust scores Dynatrace MCP 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 32HVTrust 5Grade 5Warning Issued 4Warning Cleared 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1
2026-11-08
Rank Moved
Rank rose 22 spots (#335 → #313)
2026-11-07
Rank Moved
Rank rose 10 spots (#345 → #335)
2026-11-02
Rank Moved
Rank dropped 23 spots (#310 → #333)
2026-11-01
Rank Moved
Rank rose 19 spots (#329 → #310)
2026-10-30
Rank Moved
Rank dropped 26 spots (#301 → #327)
2026-10-27
Rank Moved
Rank rose 32 spots (#319 → #287)
2026-10-25
Rank Moved
Rank dropped 28 spots (#289 → #317)
2026-10-11
Rank Moved
Rank rose 20 spots (#280 → #260)
2026-10-09
Rank Moved
Rank dropped 29 spots (#249 → #278)
2026-10-07
Rank Moved
Rank rose 17 spots (#259 → #242)
2026-10-05
Warning Issued
Warning: eligibility issues detected
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-25
Rank Moved
Rank dropped 20 spots (#217 → #237)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 797 spots (#1010 → #213)
2026-09-23
HVTrust Changed
HVTrust up 50.9pts (24.7 → 75.6)
2026-09-22
Newly Listed
First tracked at rank #1010
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 24 spots (#182 → #206)
2026-09-17
Rank Moved
Rank dropped 20 spots (#162 → #182)
2026-09-12
Rank Moved
Rank rose 10 spots (#156 → #146)
2026-09-11
Warning Issued
Warning: eligibility issues detected
2026-09-11
Rank Moved
Rank dropped 14 spots (#142 → #156)
2026-09-07
Rank Moved
Rank dropped 11 spots (#128 → #139)
2026-09-05
Grade Changed
Trust grade C → B
2026-09-05
Rank Moved
Rank rose 630 spots (#757 → #127)
2026-09-05
HVTrust Changed
HVTrust up 28.7pts (50.9 → 79.6)
2026-09-04
Grade Changed
Trust grade B → C
2026-09-04
Rank Moved
Rank dropped 651 spots (#106 → #757)
2026-09-04
HVTrust Changed
HVTrust down 27.7pts (78.6 → 50.9)
2026-09-02
Grade Changed
Trust grade C → B
2026-09-02
Rank Moved
Rank rose 544 spots (#649 → #105)
2026-09-02
HVTrust Changed
HVTrust up 27.5pts (51.1 → 78.6)
2026-09-01
Rank Moved
Rank dropped 22 spots (#627 → #649)
2026-08-31
Scorecard Added
OSSF Scorecard: 5.3/10
2026-08-31
Grade Changed
Trust grade D → C
2026-08-31
Rank Moved
Rank rose 151 spots (#778 → #627)
2026-08-31
HVTrust Changed
HVTrust up 7.4pts (43.7 → 51.1)
2026-08-30
Rank Moved
Rank dropped 28 spots (#750 → #778)
2026-08-29
Rank Moved
Rank dropped 51 spots (#699 → #750)
2026-08-28
Rank Moved
Rank dropped 23 spots (#676 → #699)
2026-08-27
Rank Moved
Rank dropped 20 spots (#656 → #676)
2026-08-26
Rank Moved
Rank dropped 81 spots (#575 → #656)
2026-08-24
Rank Moved
Rank dropped 12 spots (#560 → #572)
2026-08-23
Rank Moved
Rank dropped 10 spots (#550 → #560)
2026-08-22
Rank Moved
Rank rose 10 spots (#560 → #550)
2026-08-19
Rank Moved
Rank rose 24 spots (#573 → #549)
2026-08-13
Rank Moved
Rank dropped 28 spots (#541 → #569)
GitHub → npm: @dynatrace-oss/dynatrace-mcp-server

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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