Ext Ops Panel
Open dashboard
Comparison

han-reporting vs StoriesOnBoard - structured specifications for AI Agents

han-reporting is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). StoriesOnBoard - structured specifications for AI Agents is an MCP server published by storiesonboard.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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-reportingStoriesOnBoard - structured specifications for AI Agents
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: 1.0.0
No figure published
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 StoriesOnBoard - structured specifications for AI Agents
Facthan-reportingStoriesOnBoard - structured specifications for AI Agents
Marketplaces that list it11
Stars (GitHub) (differs)342No figure on GitHub
Forks (GitHub) (differs)28No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.storiesonboard.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/testdouble/hanNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-11-082026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 22 h ago, requires authentication

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.

StoriesOnBoard - structured specifications for AI Agents

In its own words, on Official MCP Registry:

Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.

How to run each

han-reporting As a Claude Code plugin

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

StoriesOnBoard - structured specifications for AI Agents As a remote MCP server

Claude Code
claude mcp add --transport http storiesonboard https://api.storiesonboard.com/mcp

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

Only StoriesOnBoard - structured specifications for AI Agents 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

Neither one's marketplaces publish the settings it asks for.

What it can do: han-reporting · What it can do: StoriesOnBoard - structured specifications for AI Agents · 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. 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