| FMRS | 64 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 18 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Developers who want to give an LLM real-time web search and reading capability
- Researchers doing academic literature review across arXiv and SSRN
- Teams needing semantic deduplication or classification of text/image sets
- Users with a Jina API key who want one remote MCP server usable across multiple clients
| - 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 | - Fully offline or air-gapped environments with no outbound network access
- Users unwilling to obtain a Jina API key, since most tools require one for full access and unauthenticated use is rate-limited
- Latency-sensitive workflows, since tools like search_web_deep can take 2-20 seconds per call
| - 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 | - An optional or required Jina API key (Bearer token) for accessing the Reader/Embeddings/Reranker APIs and higher rate limits
- Outbound network access from the server to target URLs, search engines, and Jina's cloud APIs
| - 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 | - This is a hosted remote server at mcp.jina.ai — queries and fetched page content pass through Jina's cloud infrastructure
- API keys stored in plaintext config files or environment variables can be exposed if configs are shared or leaked
- Rate limits apply to tools used without an API key, which can bottleneck heavy usage
- Some tools (e.g. search_web_deep) have noticeably longer response times, which can affect interactive workflows
| - 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 | Cursor, LM Studio, Claude Code, Claude Desktop, OpenAI Codex, Windsurf | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 22 | 26 | 11 |
|---|