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.

DimensionHealthcare 3DMCP server for Healthcare & Medical 3D visualization — anatomy viewers, molecular structures, DICOM medical imaging, surgical planning, dental scanning.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS35 / 100 · D75 / 100 · B
Reliability3 / 2010 / 20
Security and permissions5 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation7 / 2017 / 20
Setup experience8 / 2014 / 20
Best for
  • AI-assisted development for rapid healthcare 3D visualization
  • Developers integrating medical 3D features into their apps
  • Tool development for medical education, surgical planning, etc.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • General-purpose 3D scene development (use main SceneView MCP)
  • Standalone apps requiring real-time rendering or high-performance interaction (this server assists code generation, not direct rendering)
  • Non-medical domain users
  • 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
  • Requires network access to download package from npm
  • May access local file system to read DICOM or other files (depending on tool implementation)
  • No explicit special permissions required
  • 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
  • AI-generated code may contain compilation or runtime errors, requiring human review
  • Involves medical data; ensure privacy compliance and avoid leaking patient information
  • Dependency on npm package poses supply chain risks; update regularly
  • 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
Tools011