| FMRS | 59 / 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 | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Users who already maintain a local Hyperresearch markdown vault and want other MCP clients to reuse the same notes
- Researchers who want their desktop AI client to read existing local material instead of re-searching the web every time
- Individual researchers or small teams who care about portability (plain markdown, git-friendly, JSON exportable)
| - 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 want zero setup and only the built-in Claude Code skill without maintaining a local vault
- Users who cannot install Python 3.11+ or run local command-line tools
- Users expecting the server to guarantee factual accuracy — the README states the lint gate catches structural failures only and factual accuracy remains the user's call
- Users who need paywalled content but have not completed a local login
| - 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 | - Read and write the vault directory in the working tree (such as research/notes markdown files)
- Create and rebuild the SQLite index file; hyperresearch sync reconstructs it from markdown
- Make outbound network requests to fetch external URLs via tools such as fetch_url
- If embeddings are enabled, reach the configured embedding provider (voyage, openai; the default none needs no API keys)
- Local file-write permission required to create and update notes
| - 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 | - Fetched web content is untrusted input: the README says fetched bodies are served inside <untrusted-source> fences and treated as data, and clients should keep the same stance to avoid being steered by embedded instructions
- Write tools (create_note, update_note) modify local vault files directly, so misuse can corrupt the note collection; keeping the vault under git is advisable for rollback
- Fetching external URLs exposes requests to third-party sites, potentially revealing the research topic or IP
- Scraping paywalled or login-gated sites is subject to those sites' terms, and login session credentials are the user's own responsibility
- Claims in the README such as the DeepResearch-Bench leaderboard position and 250+ sources are the project's own statements and a forward-looking projection; third-party validation is pending and should not be treated as proof of quality
| - 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 | 13 | 26 | 11 |
|---|