mcp server
com.quanttogo/quanttogo-mcp
Macro-factor quantitative signal source for US and China stock markets via MCP.
Description as published by the maintainer. Source
- version 0.2.2
- active
active — Most recent push to the repository was 2026-08-03.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 7 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-03 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 1 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Package downloads | 103 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 0.2.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-03-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
VARRD — Statistically Validated Trading Edges + AI Research Engine
— last commit 2026-05-04, shares algorithmic-trading, quantitative-finance
Validated trading edges across futures, equities, crypto. Live signals, full audit trail.
-
io.github.Coinversaa/mcp-server
— last commit 2026-07-07, shares algorithmic-trading, trading-signals
Crypto intelligence for AI agents. Hyperliquid trader analytics, cohorts, and live market data.
-
AlgoVault — Crypto Quant Trade Calls
— last commit 2026-08-06, shares trading-signals
The Brain Layer for AI Trading Agents — quant calls + cross-venue arb across perp venues via MCP.
-
CPZAI
— last commit 2026-07-31, shares algorithmic-trading
Build, backtest, and deploy quantitative trading strategies from your AI agent.
These share tags the maintainers applied themselves, such as algorithmic-trading, quantitative-finance, trading-signals. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agent, algorithmic-trading, macro-factors, mcp, mcp-server, model-context-protocol, quantitative-finance, quantitative-trading, trading-signals.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab