uniprot-mcp
Related Servers
Alternatives to uniprot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server providing advanced access to the UniProt protein database.2621MIT
- AlicenseNot gradedqualityCmaintenanceUnified MCP server providing AI-agent-ready access to AlphaFold, PubMed, ChEMBL, Ensembl, and 37+ scientific databases.MIT
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server providing advanced access to the ChEMBL chemical database.2789MIT

SPOKEAgentofficial
AlicenseAqualityBmaintenanceA structure-aware MCP server for querying the SPOKE biomedical knowledge graph, enabling entity resolution, schema introspection, path finding, and safe Cypher queries for biomedical knowledge inference.5Apache 2.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.1937MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server for querying multi-omic personal health data (genome, labs, wearables) with an honesty contract and progressive disclosure skills.1AGPL 3.0
TDQS
Scored across 41 tools
Most tools target clearly distinct UniProt resources or operations, and descriptions explicitly route between search/get pairs and specialized resolvers. Some overlap remains among the feature-subset tools, cross-reference resolvers versus uniprot_get_cross_refs, and uniprot_target_dossier versus its component tools, but the descriptions usually make the intended choice clear.
All tools use the uniprot_ prefix and snake_case, and most follow a predictable verb_noun pattern such as get_entry, search_keywords, resolve_pdb, or compute_properties. A few deviate into noun-first or compound forms like features_at_position, taxonomy_search, target_dossier, and provenance_verify, but the convention remains readable and mostly stable.
At 41 tools the surface is well beyond the typical 3-15 range and includes many convenience wrappers, paired search/get tools, feature-subset views, and specialized resolvers for the same entry data. UniProt is a broad domain, but the set feels bloated rather than tightly scoped.
The read-only UniProt domain is covered extensively: entries, search, batch fetch, ID mapping, taxonomy, keywords, subcellular locations, UniRef, UniParc, proteomes, citations, cross-references, sequence, features, variants, disease, GO, AlphaFold, evidence, and provenance. Only minor niche lookups are absent, such as a full taxonomy record by ID, and these are not central to the main workflows.