VeyraX vs 万机阁 Wanjige — 中文 AI 工具市场
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). 万机阁 Wanjige — 中文 AI 工具市场 is an MCP server published by chenwengui23. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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 |  VeyraX |  万机阁 Wanjige — 中文 AI 工具市场 |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 615 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Downloads/month (npm): 708 Downloads/week (npm): 674 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.2 Downloads/month (npm): 708 Downloads/week (npm): 674 Forks (GitHub): 0 Stars (GitHub): 1 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 | VeyraX | 万机阁 Wanjige — 中文 AI 工具市场 |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 48 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 18 615 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/veyrax/veyrax-mcp | github.com/chenwengui23/wanjige-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 | Responded 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
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
万机阁 Wanjige — 中文 AI 工具市场
Chinese MCP tool marketplace: 15,552 callable tools for weather, stocks, FX, docs and calculations.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
万机阁 Wanjige — 中文 AI 工具市场
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: WANJIGE_API_KEY (secret), Accept header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only 万机阁 Wanjige — 中文 AI 工具市场 has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of 万机阁 Wanjige — 中文 AI 工具市场 publish no list of tools, so we do not compare tools.
Settings each asks for
Only VeyraX asks for
VEYRAX_API_KEY (secret)
Only 万机阁 Wanjige — 中文 AI 工具市场 asks for
WANJIGE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: VeyraX · What it can do: 万机阁 Wanjige — 中文 AI 工具市场 · 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. 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.