DesktopManager Windows Verification vs JProfiler
DesktopManager Windows Verification is an MCP server published by EvotecIT. Marketplaces we read that list it: 1 (Official MCP Registry). JProfiler is an MCP server published by ej-technologies. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-21. 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 |  DesktopManager Windows Verification |  JProfiler |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Forks (GitHub): 7 Stars (GitHub): 107 Not marked · First seen |
Listed Version: 16.2.1 Downloads/month (npm): 480 Downloads/week (npm): 128 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 16.2.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | DesktopManager Windows Verification | JProfiler |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 107 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (https://github.com/EvotecIT/DesktopManager/releases/download/desktopmanager-windows-verification-v0.2.1/desktopmanager-mcp-win-x64.mcpb) | On your machine (@ej-technologies/jprofiler-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | SEE LICENSE IN https://www.ej-technologies.com/jprofiler/license |
| Repository (differs) | github.com/evotecit/desktopmanager | github.com/ej-technologies/jprofiler-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 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
DesktopManager Windows Verification
Inspect and verify Windows x64 desktop apps through a local, read-only-by-default MCP server.
JProfiler
Java profiling with AI agent integration. Profile CPU, memory, JDBC, HTTP and more.
How to run each
DesktopManager Windows Verification
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
JProfiler As a local MCP server: npm package
claude mcp add --transport stdio jprofiler-mcp -- npx -y @ej-technologies/jprofiler-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: DesktopManager Windows Verification · What it can do: JProfiler · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.