zizhenghua-mcp vs TILLA - market data on one clock
zizhenghua-mcp is an MCP server published by Zizhenghua. Marketplaces we read that list it: 1 (PyPI (MCP servers)). TILLA - market data on one clock is an MCP server published by TillaCrypto. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  zizhenghua-mcp |  TILLA - market data on one clock |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 1.1.0 Downloads/month (PyPI): 115 Downloads/week (PyPI): 116 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.3 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 | zizhenghua-mcp | TILLA - market data on one clock |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | On your machine (zizhenghua-mcp) | Remote server (mcp.tillacrypto.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/zizhenghua/quant-data-mcp | github.com/tillacrypto/tilla |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-13 | 2026-10-31 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 46 h ago returned HTTP 406 |
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
zizhenghua-mcp
MCP Server for Quant Data API - A-share market data, backtest, and AI strategy generation
TILLA - market data on one clock
Aligned market data for AI agents: crypto, stocks, FX and macro on one clock. Local or hosted.
How to run each
zizhenghua-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
TILLA - market data on one clock As a remote MCP server
claude mcp add --transport http tilla-mcp https://mcp.tillacrypto.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: TILLA_API_KEY (secret), X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TILLA - market data on one clock 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
The marketplaces of zizhenghua-mcp publish no settings it asks for, so we do not compare settings.
What it can do: zizhenghua-mcp · What it can do: TILLA - market data on one clock · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.