biomcp and registry
BioMCP provides the protocol specification and reference implementation for biomedical model context servers, while BioContextAI Registry serves as a discovery and registration system for those servers—making them complements that work together in a provider/discovery relationship.
About biomcp
genomoncology/biomcp
BioMCP: Biomedical Model Context Protocol
Implements a unified CLI and MCP server that federates queries across 20+ biomedical APIs (PubMed, ClinVar, UniProt, cBioPortal, etc.) with a single grammar—`search`, `get`, and cross-entity pivots eliminate API-specific syntax. Supports local study analytics (cohort, survival, co-occurrence) from cBioPortal datasets with native SVG/PNG charts, plus progressive disclosure via composable sections and batch enrichment via g:Profiler. Deploys as a standalone binary, PyPI tool, Claude Desktop MCP server, or remote HTTP service with automatic reconnection and health probes.
About registry
biocontext-ai/registry
The BioContextAI Registry for biomedical MCP servers
Maintains a curated registry of Model Context Protocol (MCP) servers for biomedical applications, with automated schema validation and JSON export to power the BioContextAI discovery UI. Servers must meet specific criteria including biomedical focus, free academic access, OSI-approved licensing, and MCP compliance, ensuring quality through pre-commit hooks and standardized `meta.yaml` metadata. Integrates with the MCP ecosystem to enable AI agents to access specialized biomedical tools and research services.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work