Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.dynatrace-oss/Dynatrace-mcp

NPM · @DYNATRACE-OSS/DYNATRACE-MCP-SERVER · SCANNED AUG 3

[DEPRECATED] Dynatrace MCP Server. Migrate to dynatrace-for-ai or Dynatrace Remote MCP Server.

Available components

npm · @dynatrace-oss/dynatrace-mcp-server 39
+15 this week 39 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @dynatrace-oss/dynatrace-mcp-server

# add to Claude Code
claude mcp add dynatrace-oss-dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-server
# add to Codex CLI
codex mcp add dynatrace-oss-dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dynatrace-oss-dynatrace-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dynatrace-oss/dynatrace-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dynatrace-oss-dynatrace-mcp --command npx --arg -y --arg @dynatrace-oss/dynatrace-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  dynatrace-oss-dynatrace-mcp:
    command: "npx"
    args: ["-y", "@dynatrace-oss/dynatrace-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "dynatrace-oss-dynatrace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +34
    • Malware scan: unverified → pass ▲ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Security disclosure: unverified → fail ▼ functional
    • Dependency health: unverified → 0.97 ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Licence: MIT functional
  • 1 Aug 26 0
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
  • 31 Jul 26 −42
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +23
    • Known CVEs: unverified → pass ▲ security
    • Install scripts: unverified → pass ▲ security
    • Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. security
    • Dependency health: unverified → 0.97 ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Licence: MIT functional
  • 27 Jul 26 24

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@dynatrace-oss/[email protected]

Provenance metadata_mismatch

Ecosystem: npm · Outcome: metadata_mismatch

Reason: repo_metadata_mismatch

Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/dynatrace-oss/dynatrace-mcp/.github/workflows/release.yml@refs/tags/v2.1.2
Rekor log index:
2207219402
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:796d4de3292854d51c21a211e272f9a0501e0a537d87fa04a5bed74b92d451ccade3135ed84514ff93b1158598c5bdfdd38029cd8135cce68241c750f
Discovery method:
attestation_endpoint
Dependencies 17 packages

17 packages in the resolved dependency tree · 1 stale.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.