| FMRS | 69 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 15 / 20 | 15 / 20 |
|---|
| Best for | - Individual traders who want persistent memory and a decision audit trail for their AI trading agent.
- Developers building autonomous trading agents that need to query prior context before trading.
- Compliance or risk teams that need verifiable, exportable decision records.
- Researchers studying the outcome-weighted memory (OWM) framework.
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Users expecting the MCP server to place orders, manage funds or touch wallets — it does not execute trades.
- Teams needing a rich hosted service or a fast-moving feature roadmap (the project is in maintenance mode).
- Anyone treating its outputs as trade signals or investment advice.
- Users requiring capabilities not yet shipped, such as external TSA anchoring or zkML proof of inference.
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Reads the trade decision context and trade records passed in by your agent.
- Writes and maintains memory-layer and audit-chain data locally.
- By default makes one outbound call to an RFC 3161 trusted timestamping service, sending only the 32-byte daily audit root with no trade data; disable with TRADEMEMORY_TSA=off.
- Does not access API keys, wallets or broker credentials.
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - Audit-chain maturity is limited: v0.5 does not yet include TSA timestamping and external anchoring, which the docs list as roadmap items.
- OWM empirical validation is ongoing (n=40; target n>=100 for statistical significance), so conclusions should be treated cautiously.
- The evolution engine is in a research phase, with statistical gate pass rate still being optimised.
- The default outbound timestamping call contacts a third-party service, which must be disabled for fully offline environments.
- Memory and audit data live locally, so disk tampering or loss affects verifiability and historical retention.
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 20 | 26 |
|---|