Ext Ops Panel
Open dashboard
Comparison

qhs vs Linkbreakers MCP

qhs is a plugin bundle for AI coding tools published by desper. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Linkbreakers MCP is an MCP server published by linkbreakers.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceqhsLinkbreakers MCP
Community marketplace desper/quick-html-sharing Listed
Version: 0.2.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.176.3
Downloads/month (npm): 2 899
Downloads/week (npm): 2 899
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

qhs vs Linkbreakers MCP
FactqhsLinkbreakers MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (quick-html-share-mcp)Remote server (mcp.linkbreakers.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)210
Licence (differs)Not statedMIT
Repository (differs)github.com/desper/quick-html-sharinggithub.com/linkbreakers-com/agent-skills
Changes in the last 7 days (differs)25
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 h ago, requires a key

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

qhs

In its own words, on Community GitHub marketplaces:

Share AI-generated HTML instantly: paste, get unguessable URL + viewer analytics. Bundles a skill (auto-triggers on share / preview / publish phrases) and the quick-html-share-mcp MCP server with 5 tools (qhs_share, qhs_edit, qhs_delete, qhs_stats, qhs_list).

Linkbreakers MCP

In its own words, on Official MCP Registry:

QR-driven customer-journey platform for tracked QR codes, short links, and analytics.

How to run each

qhs As a Claude Code plugin

Claude Code
/plugin marketplace add desper/quick-html-sharing
/plugin install qhs@quick-html-sharing

Linkbreakers MCP As a remote MCP server

Claude Code
claude mcp add --transport http linkbreakers-mcp https://mcp.linkbreakers.com --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: LINKBREAKERS_API_TOKEN (secret), Authorization header

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

Only Linkbreakers MCP 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 qhs publish no settings it asks for, so we do not compare settings.

What it can do: qhs · What it can do: Linkbreakers MCP · 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