VeyraX vs Dynatrace
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Dynatrace is a plugin bundle for AI coding tools published by Dynatrace. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  VeyraX |   Dynatrace |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 434 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 8.0.1 Forks (GitHub): 36 Stars (GitHub): 164 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 7.0.0 Forks (GitHub): 36 Stars (GitHub): 164 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | VeyraX | Dynatrace |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 48 (worse) | 164 (better) |
| Pulls (Docker Hub) (differs) | 18 434 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (worse) | 36 (better) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/veyrax) | Installs as a plugin bundle |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 35 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/dynatrace/dynatrace-for-ai |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
Dynatrace
Dynatrace observability skills: DQL query patterns, application and infrastructure monitoring, log analysis, problem investigation, and incident response workflows, with the Dynatrace MCP server for live platform access.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
Dynatrace As a Claude Code plugin
/plugin install dynatrace@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Dynatrace publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Dynatrace publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: Dynatrace · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.