Dynatrace vs MailProbe
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). MailProbe is an MCP server published by mailprobe.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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 |   Dynatrace |  MailProbe |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 8.0.1 Forks (GitHub): 37 Stars (GitHub): 166 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 7.0.0 Forks (GitHub): 37 Stars (GitHub): 166 Not marked · First seen |
Listed Version: 1.1.1 Downloads/month (npm): 707 Downloads/week (npm): 668 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.1.1 Downloads/month (npm): 707 Downloads/week (npm): 668 Forks (GitHub): 0 Stars (GitHub): 0 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 | Dynatrace | MailProbe |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 166 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 37 (better) | 0 (worse) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 35 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/dynatrace/dynatrace-for-ai | github.com/jamalofski/mailprobe-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
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.
MailProbe
Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.
How to run each
Dynatrace As a Claude Code plugin
/plugin install dynatrace@claude-plugins-officialMailProbe As a remote MCP server
claude mcp add --transport http mailprobe https://mailprobe.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: MAILPROBE_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only MailProbe has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Dynatrace publish no settings it asks for, so we do not compare settings.
What it can do: Dynatrace · What it can do: MailProbe · Compare two other plugins
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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.