Skip to main content
Glama
josefdc

UniProt MCP Server

by josefdc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to UniProt MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-uniprot

      pipeworx-io
      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

    • @cyanheads/uniprot-mcp-server

      cyanheads
      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

    • mcp-alphafold

      zeinab-sheikhi
      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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetch_entry retrieves structured data, fetch_entry_flatfile provides flatfile formats, get_sequence focuses on sequence metadata, map_ids handles identifier mapping, and search_uniprot performs searches. There is no overlap or ambiguity between these functions.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern (e.g., fetch_entry, get_sequence, map_ids, search_uniprot), but fetch_entry_flatfile deviates slightly by including an extra descriptor. Overall, the pattern is readable and predictable.

    Tool Count5/5

    With 5 tools, this server is well-scoped for the UniProt domain. Each tool serves a specific, essential function without redundancy, making the count appropriate for typical use cases like data retrieval, mapping, and searching.

    Completeness4/5

    The toolset covers core operations for UniProt access: fetching entries in different formats, getting sequences, mapping IDs, and searching. A minor gap might be the lack of update or delete tools, but these are likely unnecessary for a read-only biological database, so agents can work effectively with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources