TradeMemory Protocol
Decision audit trail and persistent memory for AI trading agents, with tamper-evident recall.
- Sato Score79
TradeMemory Protocol is an open-source developer tool by Mnemox AI, with last code activity on 2026-10-23 (Active). Latest release on 2026-10-02. Sato Score 79/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-30. How the score works →
See how to install TradeMemory Protocol →Last commit Oct 23, 2026 · Last release Oct 2, 2026 (v0.5.6) · ★ 1,431
Listed from mnemox.ai on 2026-06-16. Install: reproduced by Sato Hub on 2026-10-26. Evidence →
Next step
Watch TradeMemory Protocol
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on mnemox-ai/tradememory-protocol before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Decision audit trail and persistent memory for AI trading agents, with tamper-evident recall.
Sato Score
79/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 20/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 13/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.5.6 · as of 2026-10-02- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from mnemox.ai on 2026-06-16. Install: reproduced by Sato Hub on 2026-10-26.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | mnemox.ai | as of 2026-10-30 |
| Verification status | Unverified — not independently reviewed | self-reported | mnemox.ai | as of 2026-10-30 |
| Recent activity | last release 2026-10-02 · last commit 2026-10-23 | observed | github.com/mnemox-ai/tradememory-protocol | 2026-10-30 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/mnemox-ai/tradememory-protocol | 2026-10-26 |
| Website answers | answered (HTTP 307) | observed | mnemox.ai | 2026-10-30 |
| Daily check record | 90 of 90 daily checks since 2026-08-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-29 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-10-02 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-10-02 |
| Built by | Mnemox AIconfidence 0.85 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Creator profile | https://github.com/mnemox-aiconfidence 0.85 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Deploys as | pip, MCP serverconfidence 0.90 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Works with | Claude, MT5, Smithery, Claude Code, Cursor, Dockerconfidence 0.75 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-07-14 |
| Agent types | MCP, Memoryconfidence 0.80 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Tags | memory, mcp, trading, audit-trail, ai-agentsconfidence 0.85 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Website | https://mnemox.ai/tradememory/confidence 0.85 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-25 |
| Repository | https://github.com/mnemox-ai/tradememory-protocolconfidence 0.90 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-16 |
| Category | Developer Toolconfidence 0.90 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-16 |
| Short description | text setconfidence 0.90 | self-reported | github.com/mnemox-ai/tradememory-protocol | as of 2026-06-16 |
| Sato Score | 79/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-30 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Oct 26, 2026
Runtime: python
pip install tradememory-protocol
claude mcp add tradememory -- uvx tradememory-protocol
# or claude_desktop_config.json: {"mcpServers": {"tradememory": {"command": "uvx", "args": ["tradememory-protocol"]}}}claude mcp add satohub-tradememory-protocol -- uvx tradememory-protocol
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-10-26. What a deploy spec is →
Observed record — 91 daily checks since 2026-08-01
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 31 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-30, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Agent types
- MCP, Memory
- Open source
- Yes
- Deploys as
- pip, MCP server
- Works with
- Claude, MT5, Smithery, Claude Code, Cursor, Docker
- Last checked
- 2026-10-30
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where TradeMemory Protocol fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets
Recent Activity
All news →Releases and posts from TradeMemory Protocol, pulled from its GitHub and X.
tradememory-protocol v0.5.6 — sync your own history, losses first
TradeMemory now pulls in your own fills, shows where your history loses money, and puts those losing trades in front of your agent before the next order. pip install -U tradememory-protocol # Hyperliquid: public fills, no key needed tradememory sync hyperliquid --address 0xYourAddress # Alpaca: read-only calls with your own keys, kept in a local file tradememory sync alpaca --env-file ~ /.secrets/
tradememory-protocol v0.5.5 — SPA path containment security hotfix
Security hotfix for the dashboard SPA catch-all route (GitHub issue #13 ). SPA static path is now bounded to dashboard/dist — the catch-all in server.py checked containment with a plain string startswith , which has no path-component boundary: a sibling directory whose name merely shares the prefix ( dist-x/ ) passed the check. Containment is now Path.is_relative_to in a dedicated _resolve_static_
tradememory-protocol v0.5.4 — anchoring integrity hotfix
Same-day hotfix for three critical gaps an adversarial review found in the v0.5.3 anchoring path: Rebuilds no longer destroy existing anchors — tsa_token is preserved when the recomputed root is identical, dropped only when the underlying data actually changed. TSA rejections can no longer masquerade as anchors — PKIStatus is now verified; explicit rejections raise instead of being stored as proof
tradememory-protocol v0.5.3 — anchored audit by default + decision instrumentation
Highlights Anchored audit, on by default. Daily Merkle roots now get an RFC 3161 TimeStampToken from an independent Time Stamp Authority automatically ( TRADEMEMORY_TSA=off to opt out). Only a 32-byte hash leaves your machine — never trade data. New POST /audit/root/{date} endpoint, and daily_reflection.py anchors yesterday's root as part of the daily loop. decision_events instrumentation. Every p
Listing History
Recorded changes to TradeMemory Protocol's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 26, 2026Verified: deploy spec
- Oct 2, 2026New release published
- Sep 8, 2026New release published
- Sep 1, 2026Sato Score tier: Medium → HighScore 68 → 71.
- Aug 2, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: pricing url, supported integrations
- Jul 14, 2026Auto-enriched: has pricing
- Jun 25, 2026Enriched: supported integrations, marketplace notes
- Jun 25, 2026Auto-enriched: creator name, creator profile url, website url, tags +2 more
- Jun 16, 2026Edited: category, github url, description short
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about TradeMemory Protocol
- Is TradeMemory Protocol open source?
- Yes. TradeMemory Protocol is open source under the MIT license; the repository is https://github.com/mnemox-ai/tradememory-protocol. Checked as of 2026-10-30.
- Which chains does TradeMemory Protocol support?
- Sato Hub has no confirmed chain list for TradeMemory Protocol as of 2026-10-30; treat chain support as unknown.
- Is TradeMemory Protocol still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-23 (last commit 2026-10-23, last release 2026-10-02), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run TradeMemory Protocol?
- python. Install: pip install tradememory-protocol. Entry: claude mcp add tradememory -- uvx tradememory-protocol # or claude_desktop_config.json: {"mcpServers": {"tradememory": {"command": "uvx", "args": ["tradememory-protocol"]}}}. Sato Hub reproduced this install in a container on 2026-10-26. It runs as an MCP server (uvx tradememory-protocol).
- Is TradeMemory Protocol verified on Sato Hub?
- Sato Hub holds one earned check for TradeMemory Protocol: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 79 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "TradeMemory Protocol — Sato Hub." Sato Hub, updated 2026-10-30, accessed 2026-10-30. https://satohub.ai/resources/tradememory-protocolData last refreshed 2026-10-30; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.