Dynatrace Managed MCP

An MCP server for self-hosted Dynatrace Managed platform

MCP Servers TypeScript Listed Apache-2.0

Is Dynatrace Managed MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.8 / 10
Provenance Attested
Signed commits 38%
Last push 3d ago
Compare Dynatrace Managed MCP
Suggest a correction

In detail: Dynatrace Managed MCP scores 83.9/100 (Grade A), ranked #97 of 1325 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 7.8/10; 38% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Dynatrace Managed MCP compares in MCP Servers

  1. #35 ClickHouse 84.1 +0.2
  2. #36 Better Godot MCP 84.0 +0.1
  3. #37 Dynatrace Managed MCP 83.9 this agent
  4. #38 Better Notion MCP 83.9 ±0
  5. #39 iMessage MCP 83.7 −0.2

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

Where the 83.9 comes from

HVTrust dimensions vs the MCP Servers average

83.9 / 100 · 100.0% confidence

Dynatrace Managed MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.1 / 25
8.8 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
15.1 / 17
2.9 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
7.6 above avg 12.1
AdoptionLog-scaled stars · package downloads
7.3 / 20
in line with avg 7.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
63.7
Activity sub-score · out of 100
#37

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-09-26 06:32 UTC · Repo last pushed 3 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
31
Forks
12
Last Push
2026-09-23
3 days ago
Commits (4 wk)
96
Downloads (7d)
602
npm
HN mentions (30d)
—
Open Issues
16
Rank Change
▼1
was #96

Analysis

Activity Inputs

63.7 / 100
StarsRepository reach
9.0 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
24.8 / 25
CommunityFork signal
5.2 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
7.8 / 10
OpenSSF Scorecard · scanned Sep 24, 2026
Signed Commits
38%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 8
SAST 10
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 5

Common questions about Dynatrace Managed MCP

Public supply-chain signals for Dynatrace Managed MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Dynatrace Managed MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Dynatrace Managed MCP publish package provenance?
Yes. Dynatrace Managed MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Dynatrace Managed MCP have an OpenSSF Scorecard?
Dynatrace Managed MCP has an OpenSSF Scorecard score of 7.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 Dynatrace Managed MCP actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Dynatrace Managed MCP use?
Dynatrace Managed MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dynatrace Managed MCP's commits signed?
38% of the last 100 commits to Dynatrace Managed 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 Managed 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
high confidence
Declared
Declared plugin/integration 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 Managed 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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-09
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-04
Tool Surface Changed
Detected tool/plugin surface changed: none → declared

Maintain Dynatrace Managed MCP?

For maintainers

HVTrust scores Dynatrace Managed 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.

Reputation Timeline

Signal history
Rank 15HVTrust 5Grade 5Listed 2Surface 2Surface 2Scorecard 1Delisted 1Provenance 1MCP 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
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 → A
2026-09-23
Rank Moved
Rank rose 509 spots (#602 → #93)
2026-09-23
HVTrust Changed
HVTrust up 50.5pts (33.7 → 84.2)
2026-09-22
Newly Listed
First tracked at rank #602
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 539 spots (#621 → #82)
2026-09-05
HVTrust Changed
HVTrust up 28.7pts (55.0 → 83.7)
2026-09-04
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-04
Grade Changed
Trust grade A → C
2026-09-04
Rank Moved
Rank dropped 560 spots (#61 → #621)
2026-09-04
HVTrust Changed
HVTrust down 29.0pts (84.0 → 55.0)
2026-09-02
Grade Changed
Trust grade C → A
2026-09-02
Rank Moved
Rank rose 443 spots (#501 → #58)
2026-09-02
HVTrust Changed
HVTrust up 28.1pts (56.5 → 84.6)
2026-08-31
Rank Moved
Rank dropped 16 spots (#476 → #492)
2026-08-30
Rank Moved
Rank rose 10 spots (#486 → #476)
2026-08-29
Rank Moved
Rank dropped 19 spots (#467 → #486)
2026-08-26
Scorecard Added
OSSF Scorecard: 7.9/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 81 spots (#532 → #451)
2026-08-26
HVTrust Changed
HVTrust up 11.0pts (45.0 → 56.0)
2026-08-22
Rank Moved
Rank rose 10 spots (#550 → #540)
2026-08-19
Rank Moved
Rank dropped 12 spots (#532 → #544)
2026-08-17
Rank Moved
Rank rose 15 spots (#553 → #538)
2026-08-16
Rank Moved
Rank dropped 18 spots (#535 → #553)
2026-08-13
Rank Moved
Rank dropped 12 spots (#521 → #533)
2026-08-12
Rank Moved
Rank rose 11 spots (#532 → #521)
2026-08-10
Rank Moved
Rank dropped 19 spots (#513 → #532)
2026-08-08
Newly Listed
First tracked at rank #512

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/dynatrace-managed-mcp.svg)](https://hvtracker.net/agents/dynatrace-managed-mcp)
HTML:
<a href="https://hvtracker.net/agents/dynatrace-managed-mcp"><img src="https://hvtracker.net/badge/dynatrace-managed-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.3 · Raw JSON