Ext Ops Panel
Open dashboard
Comparison

han-reporting vs Diagrams MCP Server

han-reporting is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Diagrams MCP Server is an MCP server published by mohammad-emad-dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplacehan-reportingDiagrams MCP Server
Community marketplace testdouble/han Listed
Version: 2.2.2
Forks (GitHub): 28
Stars (GitHub): 342
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.11.0
Downloads/month (npm): 785
Downloads/week (npm): 172
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.11.0
Downloads/month (npm): 785
Downloads/week (npm): 172
Forks (GitHub): 0
Stars (GitHub): 1
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

han-reporting vs Diagrams MCP Server
Facthan-reportingDiagrams MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)342 (better)1 (worse)
Forks (GitHub) (differs)28 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleOn your machine (diagrams-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/testdouble/hangithub.com/mohammad-emad-dev/diagrams-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-11-082026-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

han-reporting

In its own words, on Community GitHub marketplaces:

Reporting and summary skills for the Han suite. Turns feature specifications into plain-language stakeholder summaries (also called executive or business summaries) with diagrams, for sharing with non-technical stakeholders before implementation kicks off.

Diagrams MCP Server

In its own words, on Official MCP Registry:

Local-first MCP server for PlantUML and Mermaid diagrams with drift detection.

How to run each

han-reporting As a Claude Code plugin

Claude Code
/plugin marketplace add testdouble/han
/plugin install han-reporting@han

Diagrams MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio diagrams-mcp-server -- npx -y diagrams-mcp-server

Commands 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

The marketplaces of han-reporting publish no settings it asks for, so we do not compare settings.

What it can do: han-reporting · What it can do: Diagrams MCP Server · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built