com.htmlradar/share vs Snapy.host
com.htmlradar/share is an MCP server published by htmlradar.com. Marketplaces we read that list it: 1 (Official MCP Registry). Snapy.host is an MCP server published by snapy.host. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  com.htmlradar/share |  Snapy.host |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.0 Downloads/month (npm): 1 052 Downloads/week (npm): 79 Not marked · First seen |
Listed Version: 1.1.2 Downloads/month (npm): 848 Downloads/week (npm): 31 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 | com.htmlradar/share | Snapy.host |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.htmlradar.com/mcp) | On your machine (snapy-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
com.htmlradar/share
Send a web page to specific people, control who opens it, see how it was read, and update it.
Snapy.host
Publish text or HTML to Snapy.host and get a shareable link that shows who opened it.
How to run each
com.htmlradar/share As a remote MCP server
claude mcp add --transport http share https://mcp.htmlradar.com/mcpRequires: HTMLRADAR_API_KEY (secret)
Snapy.host As a local MCP server: npm package
claude mcp add --env "SNAPY_API_KEY=<YOUR_SNAPY_API_KEY>" --transport stdio snapy -- npx -y snapy-mcpRequires: SNAPY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.htmlradar/share 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
Only com.htmlradar/share asks for
HTMLRADAR_API_KEY (secret)
Only Snapy.host asks for
SNAPY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: com.htmlradar/share · What it can do: Snapy.host · 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.