BioMCP
Related Servers
Alternatives to BioMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEmpowers AI agents with direct access to the official ClinicalTrials.gov database, enabling programmatic searching, retrieval, and analysis of clinical study data through a Model Context Protocol interface.71,180 npm97Apache 2.0
- AlicenseCqualityCmaintenanceEvidence-grounded biomedical retrieval and summarization through the Model Context Protocol, enabling queries for biomedical evidence with citation-backed results.2MIT
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol server that enables advanced PubMed literature search, citation formatting, and research analysis through natural language interactions.1210MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to resolve genes, diseases, chemicals, variants and species to normalized ids, search ~36M PubMed abstracts and PMC full texts by free text or entity, and retrieve the machine-extracted relations between them with the supporting sentences and PMIDs. Supports auditing individual relations with full evidence passages and pulling per-article entity annotations with character offsets.MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates Taiwan-specific medical data including ICD-10 codes, FDA drug databases, and nutrition information into the Model Context Protocol. It enables AI models to query clinical guidelines, verify medical codes, and convert health data into FHIR R4 standardized formats.MIT
- AlicenseNot gradedqualityAmaintenanceA unified biomedical graph database that integrates 50+ primary data sources — genes, proteins, compounds, diseases, pathways, and clinical data — into a single queryable graph with billions of cross-reference edges. Its native MCP server gives LLMs direct access to structured, authoritative biomedical data, complementing their reasoning with reliable identifiers and up-to-date database content.20AGPL 3.0
TDQS
Scored across 35 tools
The tool set has clear domain separation (articles, trials, variants, etc.) but significant overlap exists between general and specialized tools. For example, 'fetch' overlaps with all the individual getters (article_getter, trial_getter, etc.), and 'search' overlaps with domain-specific searchers (article_searcher, trial_searcher, etc.). Descriptions help clarify, but agents may struggle to choose between overlapping tools.
Most tools follow a consistent verb_noun pattern (e.g., article_getter, trial_searcher, variant_getter), with verbs like 'get', 'search', and 'fetch'. However, there are deviations: 'think' and 'fetch' are single words, and 'alphagenome_predictor' uses a noun_verb pattern. Overall, naming is mostly predictable but not perfectly uniform.
With 35 tools, the count is excessive for a single server, leading to redundancy and complexity. Many tools could be consolidated (e.g., merging getters and searchers into fewer tools with parameters). This large number may overwhelm agents and increase the risk of misselection, especially given the overlapping functionalities.
The tool set provides comprehensive coverage across biomedical domains, including articles, trials, variants, genes, drugs, diseases, FDA data, and NCI resources. Each domain has both search and fetch capabilities, with detailed lifecycle support. No obvious gaps are present; the surface is well-rounded for biomedical research tasks.