MCP.Market

quant-swarm MCP server

online · 100% uptime
by blink1217·io.github.blink1217/quant-swarm·v0.5.0

Risk-first pre-trade checks, PIT data, leakage audits, and a Shadow Tournament vs a live champion.

A98/100grade A
What users say
No reviews yet
Be the first
Safety scan
A98/100

full report

Adoption
Growing

0 stars74 downloads/wk

Reviews

Write one

Nobody has reviewed quant-swarm yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

quant-swarm tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan62 source files scanned; 62 source files scanned25/25
  • Live reliabilityremote reachable in 187ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 98/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How quant-swarm compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
98/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
219 ms
faster than 60% of 30,031 servers
Downloads a week
74
more than 55% of 12,191 servers with a package

Install quant-swarm in Claude Code, Cursor or VS Code

claude mcp add --transport http quant-swarm https://swarm-mcp-503318750546.europe-west1.run.app/mcp/data
Add to Cursor

What the publisher says

From the quant-swarm repository's README, as published. We do not edit it. Read it on GitHub

quant-swarm

Risk-first pre-trade checks that gate live capital — point-in-time data, invariant and leakage audits, regime probes — plus the Shadow Tournament: score your strategy genome against a live, self-evolving trading swarm's champion on identical market paths.

<!-- mcp-name: io.github.blink1217/quant-swarm -->

Built by a Principal Quantitative Technologist

Authored by the Principal Quantitative Technologist at The 1.21 Initiative — the same code path that gates live promotion and execution decisions in the trading swarm. Every tool exists because production trading systems fail in two repeatable ways: lookahead leakage in research and an oversized position in production. quant-swarm ships the checkers that prevent both, so you can audit your own work with the exact logic that guards deployed capital.

Your backtest is static. The swarm is not.

Behind this package is a swarm that does not hand-tune strategies. A champion genome runs live; every cycle the swarm breeds challengers (tier-capped mutations), replays champion and challenger on the identical episode-seed matrix across five labelled market regimes (high-vol, drawdown, chop, melt-up, gap-heavy), and records the paired outcome in an ELO ledger. A surrogate prior pre-scores candidates so expensive replays are spent where they matter. Nothing is promoted on a single good backtest: promotion requires MINEPISODES=20 paired episodes, a Wilcoxon-significant delta, a positive worst-regime margin (maximin, not mean), a deflated-Sharpe margin against the monotonic count of every trial ever attempted, and a PBO cap. This is the champion/challenger, self-play-style loop popularised by AlphaZero-style systems, applied honestly to markets — with the two things that do not* transfer stated plainly: the market does not react to us, so there is no true self-play, and there is no learned dynamics model or tree search; selection is done by paired replay, ELO and statistical gates.

Replay is only half of it. Every Sunday the swarm also runs a forward league: each league genome — the champion, the top-ELO challengers, contributed genomes, and a planner entrant whose weekend moves are chosen by a learned model — seals its positions for the coming week from Friday's causal features, and the SHA-256 commitment is stored before the week happens. The next cycle marks every sealed position against the realised closes (net of each genome's own cost model), ranks the field on the identical real week, and updates ELO on that. Sealed forecasts cannot be overfit to the week that follows; that is the swarm's ground truth, and it feeds a replay buffer where every position is decomposed into its component moves (screen, entry, size, weekend) so credit is assigned per move and regime, not to the strategy as a blob. The forward league started on 2026-09-02; the first realised settlements land mid-September, and the swarm runs untouched for eight weeks to collect them.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

quant-swarm: common questions

Is quant-swarm MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the quant-swarm safety report
How do I install quant-swarm?
It runs remotely at swarm-mcp-503318750546.europe-west1.run.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does quant-swarm need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is quant-swarm maintained?
The last commit was 29 days ago (2026-10-06). The latest release is v0.5.0.
Is quant-swarm up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of quant-swarm?
Servers from other publishers that do the same job: MCP for Adobe Premiere Pro MCP server.
How does quant-swarm compare with other MCP servers?
safety score 98/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 219 ms (faster than 60% of 30,031 servers). Full comparison.

Alternatives to quant-swarm

Same job from other publishers: the closest match first, then the best rated.

  • MCP for Adobe Premiere Pro
    Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.
    A