TradeMemory Protocol
TradeMemory Protocol is a tool/service by Mnemox AI, open source (MIT), last active 2026-09-08 (active), Sato Score 71 of 100 as of 2026-09-14.
Decision audit trail and persistent memory for AI trading agents, with tamper-evident recall.
Last release Sep 8, 2026 · Last commit Aug 11, 2026 · ★ 1,412
Overview
Decision audit trail and persistent memory for AI trading agents, with tamper-evident recall.
Sato Score
71/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 20/20
- Interface verifiability
- 0/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 13/15
- Independent verification
- 3/10
Install — we ran this on Sep 14, 2026 and the entry step did not complete — the commands below are the project's own, and they may simply have moved on
Runtime: python
entry: entry probe failed: WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. | [notice] A new release of pip is a
ran: python -c "import tradememory_protocol"
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-09-14. What a deploy spec is →
Observed record — 63 daily checks since 2026-07-14
- Succeeded
- 63
- 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. 49 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. Rates spanning that date mix two definitions. Since then: 100%.
Last 30 days — to 2026-09-14, 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 serverfrom project docs · 2026-06-25
- Works with
- Claude, MT5, Smithery, Claude Code, Cursor, Dockerfrom project docs · 2026-07-14
- Last checked
- 2026-09-14
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.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.
- Sep 14, 2026Verified: deploy spec
- Sep 8, 2026New release published
- Sep 1, 2026Sato Score tier: Medium → HighScore 68 → 71.
- Jul 28, 2026New release published
- Jul 14, 2026Enriched: pricing url, supported integrations
- Jul 14, 2026Auto-enriched: has pricing
- Jun 30, 2026Sato Score tier: High → MediumScore 73 → 63.
- Jun 25, 2026Enriched: supported integrations, marketplace notes
- Jun 25, 2026Auto-enriched: creator name, creator profile url, website url, tags +2 more
- Jun 25, 2026Sato Score tier: Medium → HighScore 65 → 73.
Compared with
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.
Is this your project?
Prove you control the domain and you can correct this page — description, links, tags, chains. Claiming proves control, not verification: it doesn't change the Sato Score or mark anything as audited.
Claim this listing →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-09-14.
- Which chains does TradeMemory Protocol support?
- Sato Hub has no confirmed chain list for TradeMemory Protocol as of 2026-09-14; treat chain support as unknown.
- Is TradeMemory Protocol still maintained?
- The most recent public activity Sato Hub observed was on 2026-09-08 (last commit 2026-08-11, last release 2026-09-08), which Sato Hub labels "Active". 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"]}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (uvx tradememory-protocol).
- Is TradeMemory Protocol verified on Sato Hub?
- No independent verification is on record for TradeMemory Protocol; its verification status is "Unverified" and its Sato Score is 71 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this page
Sato Hub. "TradeMemory Protocol — Sato Hub." Sato Hub, updated 2026-09-14, accessed 2026-09-15. https://satohub.ai/resources/tradememory-protocolData last refreshed 2026-09-14; 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
One email a week — the agents, tools, and infrastructure that actually shipped, and why they matter.