Ext Ops Panel
Open dashboard
Comparison

io.github.dynatrace-oss/Dynatrace-mcp vs EV Load Check

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). EV Load Check is an MCP server published by pindotcom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
Marketplaceio.github.dynatrace-oss/Dynatrace-mcpEV Load Check
Official MCP Registry 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
Listed
Version: 0.1.0
No figure published
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:df93c6f1912a
Forks (GitHub): 27
Pulls (Docker Hub): 313 442
Stars (Docker Hub): 0
Stars (GitHub): 137
Not marked · First seen
Not listed

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

io.github.dynatrace-oss/Dynatrace-mcp vs EV Load Check
Factio.github.dynatrace-oss/Dynatrace-mcpEV Load Check
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)137No figure on GitHub
Pulls (Docker Hub) (differs)313 442No figure on Docker Hub
Forks (GitHub) (differs)27No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@dynatrace-oss/dynatrace-mcp-server)Remote server (ev-load-check.permitev.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)18Not published
Environment variables it asks for (differs)5, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/dynatrace-oss/dynatrace-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago

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

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.

EV Load Check

In its own words, on Official MCP Registry:

NEC-based screening for a home EV charger: panel capacity, wire sizing, voltage drop, GA incentives.

How to run each

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

EV Load Check As a remote MCP server

Claude Code
claude mcp add --transport http ev-load-check https://ev-load-check.permitev.com/mcp

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

Only EV Load Check has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of EV Load Check publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of EV Load Check publish no settings it asks for, so we do not compare settings.

What it can do: io.github.dynatrace-oss/Dynatrace-mcp · What it can do: EV Load Check · 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