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.

DimensionMirobody MCP ServerThe AI-native health data engine — collect, translate, reason with agents.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS54 / 100 · D75 / 100 · B
Reliability9 / 2013 / 20
Security and permissions11 / 2012 / 20
Maintenance13 / 2016 / 20
Documentation12 / 2017 / 20
Setup experience9 / 2017 / 20
Best for
  • Developers and health-data teams that need to standardize heterogeneous lab reports and wearable data
  • Teams that want a self-hosted, Apache-2.0, FHIR-oriented health-data stack
  • Users plugging health-data tools into MCP clients such as Claude Desktop or Cursor
  • Offline terminology and unit resolution with no network and no key
  • 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 a purely hosted, zero-deployment product
  • Users expecting local GPU inference — reasoning relies on a hosted model provider
  • Use as an official diagnostic or licensed clinical decision-making system
  • Document extraction and agent Q&A without configuring any model API key
  • 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 health documents and device data the user uploads or imports (labs, wearables, genomics)
  • Access user health records, including records shared in a care circle (gated by the per-row health_access field)
  • Call the configured hosted model provider's API (key kept in .env, e.g. OPENROUTER_API_KEY)
  • Serve agent tools to MCP clients, gated per user
  • 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
  • Health data is highly sensitive personal information; an exposed self-hosted deployment leaks medical records
  • Care-circle sharing: an invited member still decides via health_access on their own row, and any route that forgets the check must answer 403 instead of handing over a record
  • SEED_DEMO_DATA is on by default and should be set to false before a deployment holds real data
  • Documents and photos are sent to the configured hosted model provider, and scanned pages reach a vision model — assess data residency and compliance
  • The project is not a local LLM; assuming full offline operation can fail without network access
  • Model provider API keys written into .env must be protected from commits or leaks
  • 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 clientsClaude Desktop, CursorClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools011