| FMRS | 37 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 3 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 4 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Developers comfortable with Go and the Alpaca API who want to experiment with AI-driven options strategies in a paper trading sandbox
- Engineers interested in an example architecture for wiring Claude Code to a custom trading backend via MCP
| - 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
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| Not for | - Anyone wanting to trade real money in production — the author explicitly warns to use paper trading only
- Users who need active maintenance or updates, since this repo is deprecated and development has moved to OpenProphet
- Users without an Alpaca trading account and API keys, or unfamiliar with compiling and running a Go backend
| - 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)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| Required permissions | - Alpaca API keys (permission to place/cancel orders and read positions and account balance)
- Optional Gemini API key for AI-based news cleaning and summarization
- Local filesystem write access for the SQLite database and activity_logs/decisive_actions logs
- Outbound network access to Alpaca, Google News, MarketWatch, and Gemini services
| - 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
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| Risks and side effects | - Misconfiguring a live (non-paper) Alpaca endpoint can result in real financial losses; the author provides no warranty
- The project is marked deprecated by its author and no longer receives updates or fixes — review the code yourself before relying on it
- AI-generated trading decisions may be flawed and should be reviewed before execution
- Alpaca and Gemini API keys are stored in plaintext in the .env file and must be protected from exposure
| - 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
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Code | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 32 | 26 | 11 |
|---|