| FMRS | 49 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 12 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Teams building autonomous agents on MCP that need an authority control plane
- Security and platform engineering teams that need exact-action approval and verifiable evidence
- Enterprise deployments that bind human or institutional authorization to one exact executable action
| - 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 | - Projects expecting a replacement for OAuth/OIDC, workload identity, or policy engines
- Users expecting the server itself to be an auditor, accredited certifier, or settlement rail
- Deployments that do not place Gate on the credential-owning path yet expect preventive control
| - 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 | - EP_API_KEY is the key needed for write and live action-guard operations (optional; public receipt lookup may work without it)
- The server runs as a local stdio process and can read the environment variables configured for it
- Enabling EP_INCLUDE_REGISTRY_TOOLS exposes additional registry and reputation tool interfaces
| - 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 | - Preventive control holds only under complete mediation; paths that bypass the enforcement point are unconstrained
- Without EP_API_KEY, write operations and live action guarding may be unavailable
- Admission is not execution and execution is not effect; unknown results must be reconciled, not blindly retried
- Environment switches that broaden the advertised tool set widen the exposed surface
- The referenced IETF documents are individual Internet-Drafts, not RFCs or IETF endorsement
| - 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 Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|