Ext Ops Panel
Open dashboard
Comparison

HTML Cloud vs Sinkto.Link

HTML Cloud is an MCP server published by html.cloud. Marketplaces we read that list it: 1 (Official MCP Registry). Sinkto.Link is an MCP server published by sinkto.link. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceHTML CloudSinkto.Link
Official MCP Registry Listed
Version: 0.5.1
Downloads/month (npm): 455
Downloads/week (npm): 42
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
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

HTML Cloud vs Sinkto.Link
FactHTML CloudSinkto.Link
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-22Not published
Where it runs (differs)On your machine (html-cloud-mcp)Remote server (www.sinkto.link/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/viljamilaurila/html-cloudNot stated
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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

HTML Cloud

In its own words, on Official MCP Registry:

Share AI-generated HTML as a private, end-to-end encrypted link. Update it later at the same link.

Sinkto.Link

In its own words, on Official MCP Registry:

Free URL shortener: manage short links, QR codes and click analytics from AI clients.

How to run each

HTML Cloud As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio html-cloud -- npx -y html-cloud-mcp

Sinkto.Link As a remote MCP server

Claude Code
claude mcp add --transport http sinkto https://www.sinkto.link/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Sinkto.Link 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: HTML Cloud · What it can do: Sinkto.Link · Compare two other plugins

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