Skip to main content
Glama

Related Servers

Alternatives to biodatafinder

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Searches and fetches research datasets across Zenodo, DataCite (Dryad/Figshare/Dataverse/OSF), NCBI omics archives (GEO/SRA/BioProject), and the literature (PubMed/OpenAIRE) through one normalized model — deduplicating by DOI, expanding organism queries with NCBI Taxonomy synonyms, and bridging papers to the datasets they produced. Resolves citations and open-access full text, and downloads files.
      6
      73 PyPI
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables unified access to 110 life science APIs and databases, including genomics, proteomics, chemistry, literature, and clinical data. Users can query genes, proteins, compounds, pathways, and more through natural language.
      3
      MIT
    • 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
      5,541 PyPI
      1
      Apache 2.0
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables evidence-traceable annotation of human and mouse single-cell data by resolving ontology terms, searching versioned marker and reference-atlas indexes, ranking and auditing candidate cell types, and exporting sealed decision bundles with provenance.
      1
      -

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_datasets finds datasets, get_dataset retrieves metadata for a specific one, and list_sources enumerates available sources. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same verb_noun snake_case convention (search_datasets, get_dataset, list_sources). The naming pattern is consistent and predictable.

    Tool Count5/5

    With 3 tools, the server is lean but well-scoped for its purpose of searching and retrieving biodata metadata. Each tool earns its place and the count falls within the ideal 3-15 range.

    Completeness5/5

    The tool set covers the core lifecycle of dataset discovery: listing sources, searching across them, and fetching full metadata. There are no obvious gaps or dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues