vike-cli MCP server
Backtest, validate and execute trading strategies behind a mandatory two-call preview gate.
B73/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody 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.9 · 2026-09-20 · 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 1 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
Install directly
The registry entry has no remote endpoint or installable package.
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 2 days ago (2026-09-19). The latest release is v0.1.0.