Dockhold vs Artifacts
Dockhold is an MCP server published by dockhold.eu. Marketplaces we read that list it: 1 (Official MCP Registry). Artifacts is an MCP server published by kuyazee. 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
| Marketplace |  Dockhold |  Artifacts |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 1 065 Downloads/week (npm): 33 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 6 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 | Dockhold | Artifacts |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 6 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.dockhold.eu/mcp) | On your machine (ghcr.io/kuyazee/artifacts:latest) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dockhold/mcp | github.com/kuyazee/artifacts |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | 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
Dockhold
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Artifacts
Self-hosted artifact publishing: POST HTML/JSX/Markdown/zip, get an unguessable URL on your domain
How to run each
Dockhold As a remote MCP server
claude mcp add --transport http dockhold https://api.dockhold.eu/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Artifacts
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: ARTIFACTS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dockhold 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 Dockhold asks for
DOCKHOLD_REF
Only Artifacts asks for
ARTIFACTS_API_KEY (secret)BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dockhold · What it can do: Artifacts · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.