# @dynatrace-oss/dynatrace-managed-mcp-server

Model Context Protocol (MCP) server for Dynatrace Managed (self-hosted)

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.1.1
- **Author:** Dynatrace
- **License:** Apache-2.0
- **npm:** @dynatrace-oss/dynatrace-managed-mcp-server
- **Source:** https://github.com/dynatrace-oss/dynatrace-managed-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 48 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T03:07:01.193Z
- **Version scanned:** 1.0.1
- **CVEs:** none found by OSV at scan time

## Tools

18 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `dynatrace_managed_list_entity_types`
- `dynatrace_managed_get_entity_type_details`
- `dynatrace_managed_discover_entities`
- `dynatrace_managed_get_entity_details`
- `dynatrace_managed_get_entity_relationships`
- `dynatrace_managed_get_environments_info`
- `dynatrace_managed_list_events`
- `dynatrace_managed_get_event_details`
- `dynatrace_managed_query_logs`
- `dynatrace_managed_list_available_metrics`
- `dynatrace_managed_query_metrics_data`
- `dynatrace_managed_get_metric_details`
- `dynatrace_managed_list_problems`
- `dynatrace_managed_get_problem_details`
- `dynatrace_managed_list_security_problems`
- `dynatrace_managed_get_security_problem_details`
- `dynatrace_managed_list_slos`
- `dynatrace_managed_get_slo_details`

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40dynatrace-oss%2Fdynatrace-managed-mcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40dynatrace-oss%2Fdynatrace-managed-mcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40dynatrace-oss%2Fdynatrace-managed-mcp-server
- HTML page: https://forgeregistry.com/registry/%40dynatrace-oss%2Fdynatrace-managed-mcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.