MCP.Market

vike-cli MCP server

by vike-io·io.github.vike-io/vike-trader·v0.1.0

Backtest, validate and execute trading strategies behind a mandatory two-call preview gate.

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed vike-cli yet.

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

vike-cli tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

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

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How vike-cli compares

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

Safety score
73/100
higher than 38% of 48,243 servers

Install vike-cli in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

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

vike

A Rust trading platform: a live execution core, a backtest and research harness, a desktop charting shell, and bridges to fourteen venues.

This repository is a source mirror. It carries the code and nothing else — no CI workflows, no operator runbooks, no history. Each publish is one commit. The development repository is private; what you see here is what the released binaries are built from.

What is in the box

Running it

Container images carry every headless tool as one binary with a symlink per tool:

docker pull vikeio/vike-tradehub:latest      # Docker Hub
docker pull ghcr.io/vike-io/vike-tradehub    # GHCR

The command-line tool installs from the release without a toolchain (Linux and Windows; any other target compiles from the clone — crates/vike-cli/Cargo.toml's [package.metadata.binstall] says why):

cargo binstall --git https://github.com/vike-io/vike-trader vike-cli

On Windows with no Rust at all, download the executable from the release — it needs nothing installed and no toolchain:

curl.exe -L -o vike-cli.exe https://github.com/vike-io/vike-trader/releases/latest/download/vike-cli.exe
.\vike-cli.exe --version

Verify it against the release's own manifest before running it:

curl.exe -L -o SHA256SUMS https://github.com/vike-io/vike-trader/releases/latest/download/SHA256SUMS
(Get-FileHash vike-cli.exe -Algorithm SHA256).Hash.ToLower()   # compare with the vike-cli.exe line

⚠ Neither path updates itself. cargo binstall records the install under a crate version that never moves, so a re-install needs --force; a downloaded executable is replaced by downloading it again.

⚠ On Windows the standalone backtest ENGINE is not published, so data, backtest --local and sweep --local are unavailable until you build one. The remote path needs no engine: vike-cli backtest run --addr HOST:PORT runs on a vike-datahub server instead.

From source:

cargo build --workspace                      # no native dependencies on default features
cargo run -p vike-app                        # the desktop shell (live feed; needs internet)

For an agent (Claude Code, Cursor, any MCP client), the skills install straight from this repo:

npx skills add vike-io/vike-trader           # every procedure under skills/, one SKILL.md each

A fresh install has no market data — two commands fix that

vike-cli init                # example strategies, indicators and run profiles under user_data/
vike-cli data seed-demo      # a SYNTHETIC demo tape, written under the venue id `demo`
vike-cli backtest run --local --profile user_data/profiles/backtest.toml \
                  --script user_data/strategies/rhai/sma_cross/sma_cross.rhai

Shortened. The full README is on GitHub.

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

vike-cli: common questions

Is vike-cli MCP server safe?
Mostly: it is graded B (73/100). Read the vike-cli safety report
Does vike-cli need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is vike-cli maintained?
The last commit was 20 days ago (2026-10-16). The latest release is v0.1.0.