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.

DimensionOpenMetadataGoverned data context and business semantics for AI assistants and agents.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS51 / 100 · D75 / 100 · B
Reliability7 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation11 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • Data teams with an OpenMetadata deployment
  • AI assistants and agents that need governed data context
  • Organizations performing discovery across semantics, lineage, quality, policies, and business terms
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without an OpenMetadata deployment
  • Use cases that only require direct access to a raw database or files
  • Browser automation, cloud storage, or general collaboration workflows
  • 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
  • Access to the target OpenMetadata deployment's /mcp endpoint is required
  • Authentication is required through OAuth 2.0 with PKCE and the existing SSO provider, or through Basic Auth
  • The available metadata and data-quality operations are controlled by OpenMetadata authentication, authorization, roles, and policies
  • 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
  • The connection may expose permission-controlled metadata, lineage, quality, policy, and memory content from the deployment
  • Accounts with write permissions may update descriptions, tags, owners, and other metadata, or create glossary terms, lineage, and quality tests
  • Semantic-search results or memories may contain internal organizational knowledge and should be governed accordingly
  • 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 Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011