| FMRS | 57 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - AI agent developers needing broad crypto context — prices, DeFi, wallets, security — from multiple providers in one place
- Teams doing crypto due diligence with Claude, Cursor, VS Code, or other remote-HTTP-MCP clients
- Integrators who want one API key instead of separate upstream provider credentials
| - 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 who need to self-host or modify the MCP server source (the server is closed-source and managed)
- Users seeking unlimited free usage (credit-based pricing applies)
- General-purpose tasks unrelated to crypto
| - 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 | - Hive API key (Authorization Bearer or X-API-Key header, optional secret)
- Optional upstream provider keys (COINGECKO_PRO_API_KEY, ALCHEMY_API_KEY, HELIUS_API_KEY, MORALIS_API_KEY, TENDERLY_API_KEY, GOPLUS_APP_KEY/SECRET, CODEX_API_KEY, etc.)
| - 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 | - Credit-based billing: each tool call consumes credits and rate limits apply
- Security scores are not investment advice; honeypot/rugpull results may be incomplete or lag
- On-chain text (token names, memos) should be treated as untrusted input with prompt-injection risk
- Data may come from cached or degraded sources; check provenance and freshness labels in responses
- Leaked API keys can be abused; keep keys server-side and rotate them
| - 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, VS Code, Windsurf, Gemini CLI | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 6 | 26 |
|---|