| FMRS | 58 / 100 · C | 77 / 100 · B | 75 / 100 · B |
| Reliability | 7 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
| Best for | - Users who already have an NWC-compatible Lightning wallet and want an LLM to act on it
- Developers integrating bitcoin payment capability into MCP-capable clients like Claude, Goose, Cline, or Windsurf
| - 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 | - Users who don't use the bitcoin Lightning Network or lack an NWC wallet
- Use with weaker models — the README notes a capable model (e.g. Claude 3.7 Sonnet) is required or the server may not function correctly
| - 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 | - Requires an NWC connection secret, which grants the server the ability to act on your wallet's funds
- In hosted/remote mode, this secret is transmitted to the Alby server as a Bearer header or URL parameter
| - 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 | - If the NWC connection secret leaks, anyone holding it can control the associated wallet's funds
- Passing the secret via a URL query parameter risks it being logged in browser history, server logs, or proxies
- Relying on a weaker model may lead to unintended or incorrect payment actions
| - 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 Desktop, Claude Web, Claude Code, Goose Desktop, Goose CLI, Cline, Windsurf, N8N | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
| Tools | 0 | 26 | 11 |