Fetch (Reference) vs Baizhi Cloud Agent Toolkit
Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Baizhi Cloud Agent Toolkit is an MCP server published by ct-jaryn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  Fetch (Reference) |  Baizhi Cloud Agent Toolkit |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1a7a0996a565 Forks (GitHub): 11 788 Pulls (Docker Hub): 1 920 221 Stars (Docker Hub): 58 Stars (GitHub): 91 289 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.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
| Fact | Fetch (Reference) | Baizhi Cloud Agent Toolkit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 289 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 1 920 221 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 788 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/fetch) | Remote server (agent-toolkit.app.baizhi.cloud/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | Not stated |
| 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 | Responded 2 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
Fetch (Reference)
Fetches a URL from the internet and extracts its contents as markdown.
Baizhi Cloud Agent Toolkit
Web search, page extraction, visual tools and developer utilities through Baizhi Cloud.
How to run each
Fetch (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio fetch -- docker run -i --rm mcp/fetchBaizhi Cloud Agent Toolkit As a remote MCP server
claude mcp add --transport http baizhi-agent-toolkit https://agent-toolkit.app.baizhi.cloud/mcp --header "Authorization: Bearer <YOUR_BAIZHI_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Baizhi Cloud Agent Toolkit has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Baizhi Cloud Agent Toolkit publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fetch (Reference) · What it can do: Baizhi Cloud Agent Toolkit · 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.