tradememory vs io.github.beee003/vynn-mcp
tradememory is a plugin bundle for AI coding tools published by mnemox-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-29. 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 |  tradememory |  io.github.beee003/vynn-mcp |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.5.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (PyPI): 70 Downloads/week (PyPI): 32 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 | tradememory | io.github.beee003/vynn-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (tradememory-protocol) | On your machine (vynn-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 9 | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/mnemox-ai/tradememory-plugin | github.com/beee003/vynn-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
tradememory
Persistent memory + autonomous strategy evolution for AI traders. Records every trade with full context across 5 memory layers (episodic, semantic, procedural, strategic, affective). Outcome-weighted recall ranks past trades by P&L relevance. Evolution Engine discovers new strategies from raw price data using LLM-powered pattern discovery + vectorized backtesting. 15 MCP tools, 5 slash commands, 3 domain knowledge skills. 200+ trading MCP servers execute. None remember. TradeMemory does.
io.github.beee003/vynn-mcp
Self-improving AI workflows with backtesting, prompt optimization, and scheduling
How to run each
tradememory As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tradememory@claude-communityio.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.
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: tradememory · What it can do: io.github.beee003/vynn-mcp · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.