Ref - Up-To-Date Docs vs OrchestKit Docs MCP
Ref - Up-To-Date Docs is an MCP server published by ref-tools. Marketplaces we read that list it: 1 (Docker MCP Catalog). OrchestKit Docs MCP is an MCP server published by yonatangross. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:8b5fcfe3e4e1 Forks (GitHub): 71 Pulls (Docker Hub): 19 085 Stars (Docker Hub): 2 Stars (GitHub): 1 180 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 10.0.0-beta.172 Forks (GitHub): 35 Stars (GitHub): 292 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 | Ref - Up-To-Date Docs | OrchestKit Docs MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 180 (better) | 292 (worse) |
| Pulls (Docker Hub) (differs) | 19 085 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 71 (better) | 35 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/ref-tools-mcp) | Remote server (orchestkit.yonyon.ai/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ref-tools/ref-tools-mcp | github.com/yonatangross/orchestkit |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 34 h 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
Ref - Up-To-Date Docs
Ref powerful search tool connets your coding tools with documentation context. It includes an up-to-date index of public documentation and it can ingest your private documentation (eg. GitHub repos, PDFs) as well.
OrchestKit Docs MCP
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
How to run each
Ref - Up-To-Date Docs As a local MCP server: Docker image
claude mcp add --env "REF_API_KEY=<YOUR_REF_API_KEY>" --transport stdio ref -- docker run -i --rm -e REF_API_KEY mcp/ref-tools-mcp
Requires: REF_API_KEY (secret)
OrchestKit Docs MCP As a remote MCP server
claude mcp add --transport http orchestkit https://orchestkit.yonyon.ai/api/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OrchestKit Docs MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Only Ref - Up-To-Date Docs has
ref_read_urlref_search_documentation
Only OrchestKit Docs MCP has
orchestkit_docs_getorchestkit_docs_search
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (OrchestKit Docs MCP as of 2026-10-14). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of OrchestKit Docs MCP publish no settings it asks for, so we do not compare settings.
What it can do: Ref - Up-To-Date Docs · What it can do: OrchestKit Docs MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.