Backtest360 vs io.github.beee003/vynn-mcp
Backtest360 is an MCP server published by backtest360.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.beee003/vynn-mcp is an MCP server published by beee003. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-26. 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 |  Backtest360 |  io.github.beee003/vynn-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.0 Downloads/month (PyPI): 278 Downloads/week (PyPI): 35 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (PyPI): 70 Downloads/week (PyPI): 32 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | Backtest360 | io.github.beee003/vynn-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.backtest360.com/mcp) | On your machine (vynn-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/backtest360/backtest360-mcp | github.com/beee003/vynn-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 22 h ago, requires a key | no remote endpoint we check |
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
Backtest360
MCP server exposing the Backtest360 engine API as tools for AI agents.
io.github.beee003/vynn-mcp
Self-improving AI workflows with backtesting, prompt optimization, and scheduling
How to run each
Backtest360 As a remote MCP server
claude mcp add --transport http backtest360 https://mcp.backtest360.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: BACKTEST360_API_KEY (secret), X-API-Key header
io.github.beee003/vynn-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio vynn-mcp -- uvx vynn-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Backtest360 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 io.github.beee003/vynn-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Backtest360 · What it can do: io.github.beee003/vynn-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.