dynatrace-mcp@0.1.0
CAUTION· not startedPublisher claims: "Enables Cursor's agent to query Dynatrace Managed and SaaS through the classic API v2 using API-token authentication, with read-only-by-default tools for logs, problems, events, entities, metrics, security problems, and SLOs. It also provides composite root-cause-analysis and service-debugging workflows, with optional opt-in write and Grail DQL tools." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso corp.example, dynatrace.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Prompting user to enter sensitive credentials. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
s = load_settings({"DT_BASE_URL": BASE, "DT_API_TOKEN": TOKEN, "DT_PROXY": "http://u:p@proxy:3128"})Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ConfigError("DT_API_TOKEN contains whitespace; paste the token value only.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.normalize_base_url("https://user:[email protected]/e/env-1")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."aws AKIAABCDEFGHIJKLMNOP": "AKIAABCDEFGHIJKLMNOP",Fix: Never read or enumerate credential locations; accept a documented environment variable instead.out = subprocess.run([sys.executable, "-m", "dynatrace_mcp.server", "--version"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Prompting user to enter sensitive credentials≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Unclaimed publisher≈ +8 on the totalClaim iamshades: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- URL with embedded credentials≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- AWS access key pattern detected≈ +2 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.