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.

DimensionApple Health MCP ServerQuery your Apple Health export locally with SQLBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS67 / 100 · C75 / 100 · B
Reliability11 / 2010 / 20
Security and permissions15 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Users who want health data to stay local rather than pass through a third-party server
  • Users who already have an Apple Health CSV export from Simple Health Export CSV
  • Quantified-self practitioners who are comfortable with SQL and DuckDB
  • Claude Desktop users working from a trusted MCP client
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who only have the native Apple Health export.xml and have not converted it to CSV
  • Users who do not want query results potentially sent to the model provider configured in their MCP client
  • Anyone treating health reports as medical advice or diagnosis
  • Users who need persistent incremental import or a database reused across processes
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read the Apple Health CSV export files in the directory given by HEALTH_DATA_DIR
  • DuckDB processes data in memory, bounded by MAX_MEMORY_MB
  • The server itself makes no network requests and does not upload the export; however, query results returned to your MCP client may be sent to that client's configured model provider
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Every tool can reach the whole configured history, so only start this server from an MCP client you trust with that data
  • Health data is sensitive; once query results are sent to a model provider they leave the local environment
  • The first request that needs a table loads that table's full CSV history, with no date window
  • Tables are held in memory; an export that does not fit within MAX_MEMORY_MB fails with an explicit error instead of spilling to disk
  • Device overlap can produce duplicate-looking measurements, so queries may need to account for sourceName
  • Health reports summarize recorded data and are not medical advice
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools311