
TradeMemory Protocol MCP Server: Setup for Claude, Cursor and Other Apps
Gives Claude, Cursor and other assistants a memory of your trades, so they can recall past mistakes and keep a tamper-evident log of decisions.
TradeMemory stores your trades and decisions on your own computer and lets your assistant recall them, score its readiness to trade and verify the history has not been altered. It does not place orders by itself.
It runs locally from the Python package. A few tools reach outside: price data from Binance, optional Claude calls for strategy ideas, and a timestamp service for daily audit hashes. The project says validation output is for education and not financial advice.
Good for
- Traders who use an AI assistant to plan and review trades
- Developers building trading agents that need memory and an audit log
- Teams who need to show how an AI trading decision was made
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install tradememory-protocol MCP
Claude Code
- 1
Copy this prompt.
Add the tradememory-protocol MCP server to Claude Code. Run this command: claude mcp add tradememory-protocol -- uvx tradememory-protocol Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires uv (Python).
Built from the package data we hold. Not yet tested by us.
Tools
Records a trade in memory
Saves a trade with its reasoning and outcome into several memory layers at once, and updates running stats such as confidence, streaks and typical hold time.
Try: “Record my AAPL long at $195: earnings beat, high confidence.”
Write ·
remember_tradeFinds past trades that matter now
Ranks stored trades by outcome, how similar the conditions are, recency and your current mood. With losses first it shows losing trades in similar conditions before you act.
Try: “Before I buy, show me the losses I took in similar conditions.”
Write ·
recall_memoriesShows how each strategy is doing
Returns totals per strategy and symbol so you can see which strategies work and which do not.
Try: “How is my VolBreakout strategy performing on XAUUSD?”
Read ·
get_strategy_performanceShows one trade in full
Returns the full context and reflection recorded for a single trade ID.
Try: “Show the reflection for trade MT5-7047640363.”
Read ·
get_trade_reflectionDescribes your trading habits
Reports hold times, how you sell winners versus losers, position size spread and a Kelly comparison, from stored trades.
Try: “What do my trading habits look like for XAUUSD?”
Read ·
get_behavioral_analysisShows confidence and drawdown
Returns current confidence, risk appetite, drawdown, win and loss streaks, and a suggested action based on drawdown.
Try: “What state am I in right now?”
Read ·
get_agent_stateSaves a conditional plan
Stores a rule-based plan that waits for a trigger, such as a market regime or drawdown level, until it fires, expires or you cancel it.
Try: “Plan: if the market turns ranging, reduce size by half.”
Write ·
create_trading_planChecks which plans fire now
Compares your waiting plans with the market context you give, expires old ones and returns the matches.
Try: “Do any of my plans trigger in a volatile regime?”
Write ·
check_active_plansGives a go, reduced or skip rating
Scores whether you have enough data and confidence to trade, from sample size, memory quality, regime experience, streaks and drawdown. It advises only and places no orders.
Try: “Do I have the track record to trade VolBreakout at full size?”
Write ·
check_trade_legitimacyScores the quality of a decision
Rates the decision process, not the outcome, on regime match, sizing against Kelly, similarity to past trades, risk state and historical pattern.
Try: “Score my planned long on XAUUSD before I enter.”
Write ·
compute_dqsTests a strategy for overfitting
Runs four statistical tests on a trade log or returns file you supply. The tool says it is for education and research and is not financial advice.
Try: “Validate the strategy in this trade log CSV.”
Read ·
validate_strategyDownloads price history from Binance
Fetches OHLCV bars for a pair such as BTCUSDT and timeframe from Binance, to feed pattern discovery and backtests.
Try: “Fetch 90 days of 1h BTCUSDT bars.”
Write ·
evolution_fetch_market_dataAsks Claude to propose trading patterns
Sends price data to Claude, which returns candidate entry and exit patterns you can backtest. Uses your Anthropic API key.
Try: “Discover 5 candidate patterns on BTCUSDT 1h.”
Write ·
evolution_discover_patternsBacktests one candidate pattern
Runs a vectorized backtest of a pattern on historical data and returns Sharpe ratio, win rate, trade count, drawdown and total profit and loss.
Try: “Backtest the first pattern.”
Write ·
evolution_run_backtestRuns the full strategy evolution loop
Generates patterns with an LLM, backtests them, keeps those that hold up on unseen data and drops the rest across several rounds.
Try: “Evolve a strategy for ETHUSDT on 4h bars.”
Write ·
evolution_evolve_strategyLists past evolution runs
Returns the evolution runs from this session with graduated strategies, rejected ones, token use and backtest counts. It resets when the server restarts.
Try: “Show what evolution has run so far.”
Read ·
evolution_get_logExports tamper-evident decision records
Returns the saved Trading Decision Records with the memory context behind each decision, for one trade or filtered by strategy.
Try: “Export the audit trail for VolBreakout.”
Read ·
export_audit_trailChecks one record for tampering
Recomputes a record's SHA-256 hash and compares it with the hash stored at decision time.
Try: “Verify trade MT5-7047640363 was not altered.”
Read ·
verify_audit_hashChecks the whole record chain
Walks the hash chain from one record to another and reports whether every link matches and where it first breaks.
Try: “Verify the whole audit chain.”
Read ·
verify_audit_chainGets a day's combined audit hash
Returns the daily Merkle root over that day's records, or rebuilds and overwrites the stored one. A rebuild can submit it to an outside timestamp service.
Try: “Get the audit root for 2026-10-01.”
Write ·
get_daily_root
Read from the source code
Permissions
medium risk · 4 things to watch
Medium risk
It stores your trade history locally and cannot place orders by default, but its advice can still steer real trades. Check any go or skip rating yourself before you act.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Its ratings can steer real trades
check_trade_legitimacy and compute_dqs return go, reduced or skip style advice from your own history. They place no orders, but do not treat them as financial advice. github.com
A hash is sent to a timestamp service
README: daily audit roots are timestamped through RFC 3161 by default (a 32-byte hash, no trade data). Set TRADEMEMORY_TSA=off to stop it. github.com
Evolution tools use outside services
They read public Binance data. If you set ANTHROPIC_API_KEY they also send price data to Claude and use your key. github.com
The broker proxy is separate and optional
The optional proxy extra can forward orders to a broker through Mnemox Control. That is not part of the default install. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Talks to | api.binance.com. freetsa.org (daily audit hash, on by default). Anthropic API (only if ANTHROPIC_API_KEY is set) |
|---|---|
| Sign-in and keys | No credentials by default. ANTHROPIC_API_KEY is optional and only used by the evolution tools. |
Questions
Is the TradeMemory MCP server official?
Yes. It is published by Mnemox (mnemox-ai) from the tradememory-protocol repo, and it is the project's own server.
Can it place trades?
Not in the default install. The MCP tools record, recall, score and verify. An optional proxy extra can sit in front of a broker, but it is a separate setup.
Does it need an API key?
No. It runs with no key. ANTHROPIC_API_KEY is optional and only used by the evolution tools that call Claude.
Where is my data stored?
On your own computer, in a local SQLite file, per the README. The daily audit hash (32 bytes, no trade data) goes to a public timestamp service (freetsa.org) unless you set TRADEMEMORY_TSA=off.
Is it financial advice?
No. The strategy validation tool says it is for education and research and is not financial advice.
Does the list show all 20 tools?
Yes. The 20 tools match the README and the source of version 0.5.6.
How do I add it to Claude Desktop or Claude Code?
Use the install box above. It runs with uvx, so you need uv installed first.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
tradememory-protocol- Registry
- PyPI
- Transport
- stdio
- Auth
- None
- Version
- 0.5.6
- License
- MIT
- Last commit
- Oct 23, 2026
- Open issues
- 6
- Listed in
- Official MCP registry
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 3Hide
- README.md · github.com
- mcp_server.py · github.com
- mcp_tools.py · github.com