tradememory-protocol

mnemox-ai/tradememory-protocol is ranked 10,357 among these 8 peers; remorses/kimaki is ranked 10,346.

** It is an open-source, local-first memory and brake for AI trading agents: it pulls in your fills, finds where your own history loses money, puts those losing trades in front of your agent before the next order, and can refuse an order that breaks rules you set, before it reaches the broker. Brokers now let AI agents trade over MCP, with different guardrails: Webull and tastytrade set size or buying-power limits, Interactive Brokers only lets the agent

draft an order for you to submit, and Robinhood and Public set no cap you can impose on an external agent (StockBrokers, 2026-09-30). None of them looks at how your own past trades went. Start with your own history Each closed trade is stored in memory once; running it again stores only new trades. Then it prints where your history loses money. The format, with illustrative numbers: These are descriptive statistics of your own past trades, not advice

about the next one. Hyperliquid's API serves only an address's recent fills, not its whole history, so the sooner it is synced, the more history is kept. Other venues: MT5 and Binance spot sync scripts are in , and any agent can record a trade with . Before the next order puts every losing trade ahead of the rest, the bigger losses in similar conditions first, with their size and P&L. Besides the symbol's most recent trades, it searches the symbol's

recent losing trades, so an older loss is not crowded out. The server tells connected agents to call it before proposing a trade. The default order ranks better outcomes higher (by R multiple, where one was recorded) and keeps at least 20% losses in the list. "* Claude Code / Cursor / Docker **Full walkthrough:** Getting Started (Trader Track + Developer Track) Put a brake in front of your broker (preview) The extra runs TradeMemory between your agent and your broker's MCP server (Alpaca

today). Every tool is forwarded unchanged except the order-placing ones, which Mnemox Control evaluates against a policy you own before they reach the broker. Every evaluation, allowed or refused, is recorded and chained into the audit log. An allowed order comes back with your losing trades from similar conditions first, and later fills in how each forwarded trade ended, in R when the entry carried a stop. The agent you already have keeps working; only one line of its

MCP config changes. Refused by default: symbols outside your list, orders above your notional and position limits, entries without a bracket stop, any new order after your daily-loss or drawdown limit, cancelling the protective stop of an open position, any tool the brake has not classified, and everything while you have run . Orders at or above wait for , which approves exactly the terms you read; the agent retries with the same and the same terms, and the proxy forwards

it at most once. returns the same decision without placing anything, for pre-checks and for advisory layers in other