Skip to main content
Glama

Related Servers

Alternatives to uniprot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to UniProt protein sequence and function knowledge base, enabling search and retrieval of protein entries, proteomes, taxonomy, and feature annotations.
      2 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides seamless access to UniProtKB protein database, enabling queries for protein entries, sequences, Gene Ontology annotations, full-text search, and ID mapping across 200+ database types.
      5
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Search UniProtKB by protein function, fetch curated records, map IDs across databases, and pull reference proteomes, taxonomy, and sequences via MCP. Supports both STDIO and Streamable HTTP transports.
      61 npm
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes the UniProt REST API to LLM clients, enabling search and retrieval of protein data via tools like search_uniprotkb, get_entry, and map_ids.
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that grounds protein research in the UniProt SPARQL endpoint, providing tools for querying proteins, sequences, variants, diseases, and more via intent-named tools and raw SPARQL.
      15
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Provides programmatic access to AlphaFold protein structure predictions and UniProt data, enabling users to retrieve protein structures, summaries, and annotations through natural language.
      3
      -

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools 1-3 all fetch data for a given entry but in different formats (structured, flatfile, sequence). They are distinct enough with clear descriptions, but an agent might briefly hesitate between fetch_entry and fetch_entry_flatfile. map_ids and search_uniprot are completely separate.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (fetch_entry, fetch_entry_flatfile, get_sequence, map_ids, search_uniprot). No mixing of styles or abbreviations.

    Tool Count5/5

    5 tools is an appropriate number for a focused UniProt server. It covers the main operations (entry retrieval, sequence, ID mapping, search) without being too minimal or overwhelming.

    Completeness4/5

    The tool set covers core UniProt workflows: retrieving entries in multiple formats, extracting sequence, ID mapping, and search. Minor gaps like batch operations or advanced query filtering exist, but these are acceptable for a basic server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues