Drop to CDN vs dropthis
Drop to CDN is an MCP server published by Nexus-JPF. Marketplaces we read that list it: 1 (Official MCP Registry). dropthis is an MCP server published by dropthis-dev. 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 |  Drop to CDN | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Downloads/month (npm): 154 Downloads/week (npm): 22 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.37.0 Downloads/month (npm): 236 Downloads/week (npm): 77 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 | Drop to CDN | dropthis |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-server-droptocdn) | Remote server (mcp.dropthis.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nexus-jpf/mcp-server-droptocdn | github.com/dropthis-dev/dropthis-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 410 (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
Drop to CDN
Upload files and get instant public CDN URLs from Claude Desktop, Cursor, and other MCP hosts.
dropthis
Publish HTML, files, or a URL to a permanent public URL, then update it — from any MCP agent.
How to run each
Drop to CDN As a local MCP server: npm package
claude mcp add --env "DROPTOCDN_API_KEY=<YOUR_DROPTOCDN_API_KEY>" --transport stdio droptocdn -- npx -y mcp-server-droptocdnRequires: DROPTOCDN_API_KEY (secret)
dropthis As a remote MCP server
claude mcp add --transport http dropthis-mcp https://mcp.dropthis.app/mcpRequires: DROPTHIS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only dropthis 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 Drop to CDN asks for
DROPTOCDN_API_KEY (secret)DROPTOCDN_API_URL
Only dropthis asks for
DROPTHIS_API_KEY (secret)DROPTHIS_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Drop to CDN · What it can do: dropthis · 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.