Skip to main content
Glama

Related Servers

Alternatives to encode-toolkit

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      A
      maintenance
      BioMCP 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.
      73
      23 PyPI
      12
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Unified genomic track, peak, and sequence retrieval tool for ENCODE, ChIP-Atlas, ReMap, GEO, and SRA/ENA with unified metadata, resolved DOI/PMID provenance, and direct FASTQ download without SRA toolkit.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables scRNA-Seq analysis through natural language, providing tools for data preprocessing, clustering, and biological visualization. It supports both predefined function execution and a flexible code mode powered by a Jupyter backend for automated single-cell transcriptomics workflows.
      16
      BSD 3-Clause
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for searching and accessing RNA sequencing datasets from the European Nucleotide Archive (ENA), supporting bulk, single-cell, and spatial transcriptomics with advanced filtering and download capabilities.
      11
      1
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with clear usage guidance (e.g., encode_list_files vs encode_search_files vs encode_download_files). However, a few pairs like encode_get_metadata vs encode_get_facets and encode_get_references vs encode_get_citations are close enough that an agent could misselect without careful reading, though descriptions mitigate this.

    Naming Consistency5/5

    All tools follow a consistent 'encode_verb_noun' snake_case pattern (e.g., encode_search_experiments, encode_download_files, encode_log_derived_file). There are no mixed camelCase or inconsistent verb styles, making the naming highly predictable.

    Tool Count4/5

    20 tools is slightly above the typical 3-15 range, but the server spans a wide domain: ENCODE search, file download, local tracking, provenance, references, citations, and credentials. Each tool has a distinct role, so the count feels reasonable rather than bloated.

    Completeness3/5

    Core operations are well covered: search/get experiments, list/search/download files, track experiments, and export data. However, there is no delete/untrack for tracked experiments, no unlink for references, and no delete for derived files—create and read exist but update/delete are missing, which is a notable lifecycle gap.

    Maintenance

    ActivityNo data
    ResponsivenessWithin a week