M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionHyperresearch MCP ServerA deep research agent for Claude Code that turns every page it reads into a persistent, searchable vault.Hevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS59 / 100 · C77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance11 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 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
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)
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
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
Supported clientsClaude Desktop, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools1326