mcp-tools vs io.github.ZhongQuinnKing/caishi
mcp-tools is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑02.
mcp-tools is a plugin bundle for AI coding tools published by izumin5210. No marketplace we read lists it any more. io.github.ZhongQuinnKing/caishi is an MCP server published by ZhongQuinnKing. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.ZhongQuinnKing/caishi | |
|---|---|---|
| Community marketplace izumin5210/dotfiles | Removed on 2026-11-02 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Downloads/month (npm): 941 Downloads/week (npm): 101 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.3.0 Downloads/month (npm): 941 Downloads/week (npm): 101 Forks (GitHub): 1 Stars (GitHub): 3 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 | mcp-toolsno longer listed · | io.github.ZhongQuinnKing/caishi |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 22 | 3 |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/mcp) | On your machine (caishi-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/izumin5210/dotfiles | github.com/zhongquinnking/caishi |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-22 | 2026-10-12 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mcp-tools
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
guru-mcp io.github.mrfentmen/guru-mcp
Guru knowledge base search and collections.
-
mcp io.minnas/mcp
Share prompts and context with your team and discover community collections.
-
Build high-quality MCP servers for LLM integrations
-
Git content governance, 23 deterministic MCP tools. Hosted: docs.contentrain.io/developer/mcp-cloud
-
Source-grounded Quickshell, QML, and Qt documentation, examples, and real-world implementations.
-
Curated knowledge for AI agents — 19K chunks, 121 skills, semantic search via MCP
What each says it does
mcp-tools
Personal MCP servers (any-script-mcp, o3-search, deepwiki)
io.github.ZhongQuinnKing/caishi
Read Bilibili, Douyin, Xiaohongshu and any web page via your own logged-in Chrome.
How to run each
mcp-tools
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.ZhongQuinnKing/caishi As a local MCP server: npm package
claude mcp add --transport stdio caishi -- npx -y caishi-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.ZhongQuinnKing/caishi publish no settings it asks for, so we do not compare settings.
What it can do: mcp-tools · What it can do: io.github.ZhongQuinnKing/caishi · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.