| FMRS | 55 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 8 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Indie hackers who want competitor intelligence callable directly by an agent
- Growth teams benchmarking against competitors
- Investors doing quick pre-DD intelligence gathering
- Founders preparing a launch in a crowded market
| - 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 | - Teams requiring fully offline or self-hosted deployment with no data sent to third-party services
- Self-hosted setups that cannot supply third-party API keys (such as DataForSEO, Apify, Product Hunt, and LLM providers)
- Users expecting non-public internal data (this tool works from public signals only)
- Clients that only support local stdio MCP processes and not remote HTTP MCP
| - 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 a valid Analook access token (Bearer token) for remote MCP authentication
- Analysis depends on third-party data-source API keys (DataForSEO, Apify, Product Hunt, TeamoRouter, DeepSeek)
- Server-side use of Supabase for auth, credits, and report storage
| - 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 | - Reports are generated by third-party LLM and data services and may contain inaccurate or outdated information; verify key conclusions manually
- Results are inferred from public signals, and business-model or revenue estimates are ranges and hypotheses only
- Requests are sent to the remote service https://www.analook.com/mcp/, so data-transfer and compliance requirements should be assessed
- A leaked token may allow others to consume your account credits
- The repository declares no license metadata (the README states MIT); confirm authorization before commercial use
| - 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, Cursor | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 5 | 26 | 11 |
|---|