Skip to main content
Glama

Related Servers

Alternatives to uniprot-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.8/5.0

    Scored across 41 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week