ASMHunter vs Dynatrace MCP

A side-by-side look at the ASMHunter and Dynatrace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

A
ASMHunterMonitoring
Drive ASMHunter attack-surface monitoring from an AI agent: recon, scans, findings, reports.12EmergingAuth: not declared
Dynatrace MCP logoDynatrace MCPMonitoring · Local subprocess (stdio)Leverage AI-driven observability, security, and automation to analyze anomalies, logs, traces, events, metrics.36FairAuth: oauth 2.0

Verdict: choose ASMHunter for monitoring work; choose Dynatrace MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose ASMHunter when

  • You need dedicated capabilities in the Monitoring domain.
Explore ASMHunter

Dynatrace MCP logoChoose Dynatrace MCP when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You have the keys it needs: DT_ENVIRONMENT, DT_MCP_TOKEN_STORAGE, DT_GRAIL_QUERY_BUDGET_GB.
Explore Dynatrace MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
ASMHunter
Dynatrace MCP logoDynatrace MCP
CategoryMonitoringMonitoring
Quality signal12/100 · Emerging36/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsNone listedDT_ENVIRONMENTDT_MCP_TOKEN_STORAGEDT_GRAIL_QUERY_BUDGET_GB
Verified ownerCommunity listingCommunity listing
GitHub stars—137
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

ASMHunter tools

No tool names declared yet. Check the project README from the listing page.

Dynatrace MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

ASMHunter

No confirmed install command for ASMHunter yet — follow the setup steps linked from its listing page rather than a guessed package name.

Dynatrace MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dynatrace-oss-dynatrace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dynatrace-oss/dynatrace-mcp-server"
      ],
      "env": {
        "DT_ENVIRONMENT": "YOUR_DT_ENVIRONMENT_HERE",
        "DT_MCP_TOKEN_STORAGE": "YOUR_DT_MCP_TOKEN_STORAGE_HERE",
        "DT_GRAIL_QUERY_BUDGET_GB": "YOUR_DT_GRAIL_QUERY_BUDGET_GB_HERE"
      }
    }
  }
}

Frequently asked questions

ASMHunter is categorized under Monitoring and uses an install path we have not confirmed yet. Dynatrace MCP belongs to Monitoring and uses a local stdio subprocess. Pick ASMHunter for monitoring work and Dynatrace MCP for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. ASMHunter has no confirmed install command yet — follow its own setup instructions.

ASMHunter has no declared pricing — check the project's own site. Dynatrace MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add asmhunter and dynatrace-oss-dynatrace-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ASMHunter has a quality signal of 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Dynatrace MCP has 36/100 (Fair) with 5 views, 0 installs and 137 GitHub stars.