Ext Ops Panel
Open dashboard
Comparison

MCPower Security Proxy vs io.github.dynatrace-oss/Dynatrace-mcp

MCPower Security Proxy is an MCP server published by MCPower-Security. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dynatrace-oss/Dynatrace-mcp is an MCP server published by dynatrace-oss. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-09. 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

Where each is published
MarketplaceMCPower Security Proxyio.github.dynatrace-oss/Dynatrace-mcp
Official MCP Registry Listed
Version: 0.0.91
Downloads/month (PyPI): 270
Downloads/week (PyPI): 41
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 2.1.2
Downloads/month (npm): 81 032
Downloads/week (npm): 28 084
Forks (GitHub): 27
Stars (GitHub): 137
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:df93c6f1912a
Forks (GitHub): 27
Pulls (Docker Hub): 312 298
Stars (Docker Hub): 0
Stars (GitHub): 137
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

MCPower Security Proxy vs io.github.dynatrace-oss/Dynatrace-mcp
FactMCPower Security Proxyio.github.dynatrace-oss/Dynatrace-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (worse)137 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub312 298
Forks (GitHub) (differs)1 (worse)27 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcpower-proxy)On your machine (@dynatrace-oss/dynatrace-mcp-server)
Transportstdiostdio
Tools it declares (differs)Not published18
Environment variables it asks for (differs)Not published5, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/mcpower-security/mcpower-proxygithub.com/dynatrace-oss/dynatrace-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

MCPower Security Proxy

In its own words, on Official MCP Registry:

Security proxy that automatically wraps MCP servers with real-time monitoring and policy enforcement

io.github.dynatrace-oss/Dynatrace-mcp

In its own words, on Official MCP Registry:

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

How to run each

MCPower Security Proxy As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcpower-proxy -- uvx mcpower-proxy

io.github.dynatrace-oss/Dynatrace-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "DT_ENVIRONMENT=<YOUR_DT_ENVIRONMENT>" --transport stdio dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-server

Requires: DT_ENVIRONMENT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of MCPower Security Proxy publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of MCPower Security Proxy publish no settings it asks for, so we do not compare settings.

What it can do: MCPower Security Proxy · What it can do: io.github.dynatrace-oss/Dynatrace-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built