AlphaFold Sovereign MCP
Related Servers
Alternatives to AlphaFold Sovereign MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceUnified MCP server providing AI-agent-ready access to AlphaFold, PubMed, ChEMBL, Ensembl, and 37+ scientific databases.MIT
- FlicenseBqualityAmaintenanceBioMCP is an open-source MCP server that connects any AI assistant to 15 open bioinformatics databases with zero configuration. It provides 23 tools for literature, sequences, BLAST, structures, enrichment, annotations, genomes, interactions, variants, domains, compounds, and single-cell data.7329 PyPI14-
- AlicenseAqualityAmaintenanceA high-performance MCP server that gives LLMs access to 25 biomedical tools federated across 50+ upstream APIs for genes, variants, drugs, diseases, literature, clinical trials, and structural biology.43956 npm12Apache 2.0
- 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
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server that provides access to the AlphaFold Protein Structure Database through a rich set of tools and resources for protein structure prediction analysis.1936MIT
- FlicenseNot gradedqualityDmaintenanceAn advanced integrated MCP server platform that combines 600+ tools and multiple biomedical databases to enable comprehensive information retrieval across molecules, proteins, genes, and diseases for accelerating therapeutic research.40-
TDQS
Scored across 29 tools
Descriptions do explicit work to separate near-neighbours (get_disease_targets vs get_common_disease_targets, find_drug_repurposing_candidates vs map_disease_drug_landscape, get_protein_structure vs the four structure-interpretation tools) and local-recall tools are clearly labelled as non-live. The main residual ambiguity is the variant cluster — triage_variant_3d, generate_variant_clinical_report, and classify_variant_acmg all emit variant reports, with triage_variant_3d admitting placeholders and pointing elsewhere for AlphaMissense. A careful agent can pick correctly, but these three can be confused at a glance.
Every tool is snake_case with an action verb first (get_, query_, lookup_, search_, analyze_, score_, compute_, compare_, find_, generate_, classify_, synthesize_, export_, resolve_, map_, detect_, triage_), and resource nouns are reused consistently across the set. No camelCase or mixed convention appears.
At 29 tools this is the heavy end, though the scope genuinely spans structural analysis, MONDO/HPO ontology, Open Targets/ChEMBL drug work, variant interpretation, and a local knowledge graph. Several local-store utilities (get_knowledge_graph_stats, query_variant_database, query_protein_database, export_research_dataset) are ancillary and inflate the surface for what is largely a read-only research server.
The read/analysis surface is broad and well covered, from structure retrieval through druggability, repurposing, and disease-phenotype traversal. However, the local knowledge graph is queried and exported but never written to — the storage API the descriptions reference is not exposed, leaving a notable dead end — and there is no sequence-level comparison or ligand-level tooling.