Ext Ops Panel
Open dashboard
Comparison

Sequesign vs io.github.dynatrace-oss/Dynatrace-mcp

Sequesign is an MCP server published by Sequesign. 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-10-29. 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
MarketplaceSequesignio.github.dynatrace-oss/Dynatrace-mcp
Official MCP Registry Listed
Version: 0.4.1
Downloads/month (npm): 198
Downloads/week (npm): 33
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.1.2
Downloads/month (npm): 64 896
Downloads/week (npm): 12 165
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): 308 535
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

Sequesign vs io.github.dynatrace-oss/Dynatrace-mcp
FactSequesignio.github.dynatrace-oss/Dynatrace-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)137 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub308 535
Forks (GitHub) (differs)0 (worse)27 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@sequesign/mcp)On your machine (@dynatrace-oss/dynatrace-mcp-server)
Transportstdiostdio
Tools it declares (differs)Not published18
Environment variables it asks for (differs)6, secrets among them: 35, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/sequesign/mcpgithub.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

Sequesign

In its own words, on Official MCP Registry:

Cryptographically verifiable receipts of an agent's delegated work, verified offline.

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

Sequesign As a local MCP server: npm package

Claude Code
claude mcp add --env "SEQUESIGN_AGENT_PRIVATE_KEY=<YOUR_SEQUESIGN_AGENT_PRIVATE_KEY>" --env "SEQUESIGN_API_KEY=<YOUR_SEQUESIGN_API_KEY>" --env "SEQUESIGN_TEMPLATE_REGISTRY_TOKEN=<YOUR_SEQUESIGN_TEMPLATE_REGISTRY_TOKEN>" --transport stdio sequesign -- npx -y @sequesign/mcp

Requires: SEQUESIGN_AGENT_PRIVATE_KEY (secret), SEQUESIGN_API_KEY (secret), SEQUESIGN_TEMPLATE_REGISTRY_TOKEN (secret)

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 Sequesign publish no list of tools, so we do not compare tools.

Settings each asks for

Only Sequesign asks for

  • SEQUESIGN_AGENT_PRIVATE_KEY (secret)
  • SEQUESIGN_API_KEY (secret)
  • SEQUESIGN_MODE
  • SEQUESIGN_PACKAGE_DIR
  • SEQUESIGN_TEMPLATE_REGISTRY_TOKEN (secret)
  • SEQUESIGN_TEMPLATE_REGISTRY_URL

Only io.github.dynatrace-oss/Dynatrace-mcp asks for

  • DT_ENVIRONMENT
  • DT_GRAIL_QUERY_BUDGET_GB
  • DT_PLATFORM_TOKEN
  • OAUTH_CLIENT_ID (secret)
  • OAUTH_CLIENT_SECRET (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Sequesign · 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