Skip to main content
Glama
musharna

data-aggregator-mcp

by musharna

Related Servers

Alternatives to data-aggregator-mcp

  • A
    license
    A
    quality
    A
    maintenance
    ▎ Provides 32 tools for plant-genomics locus lookup across 11 free public backends (Ensembl Plants, Phytozome, UniProtKB, Europe PMC, QuickGO, NCBI BLAST, Gramene, KEGG, STRING-DB, ATTED-II, BAR). Takes a TAIR-style locus plus optional organism and returns gene metadata, functional/pathway annotation, interactions, co-expression, and literature — in single-locus, batch, and cross-source synthesis.
    56
    7
    MIT

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables users to search multiple public life-science data repositories (GEO, ENA, CELLxGENE, PRIDE, DataCite) with a single query, returning a unified ranked list of datasets with ontology-expanded terms and per-source error reporting.
    3
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to keylessly search open research datasets by full-text query and fetch full metadata plus download links for a dataset by DOI.
    351 npm
    MIT
  • A
    license
    B
    quality
    A
    maintenance
    Enables searching and downloading academic papers from 14 platforms including arXiv, PubMed, Google Scholar, Web of Science, Springer, and Sci-Hub with unified data format and intelligent rate limiting.
    21
    747 npm
    186
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables searching for academic papers and preprints across multiple platforms including Semantic Scholar, arXiv, PubMed, and CrossRef. It provides access to research records, DOI lookups, and journal metadata through a unified interface deployed on Cloudflare Workers.
    -

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool occupies a distinct phase of the data lifecycle: list_sources (source metadata), search (fan-out discovery), resolve (full record), operate (remote tabular inspection), fetch (download), and relate (join hints). The descriptions explicitly state boundaries (e.g. resolve returns the full record, fetch returns paths, relate is HINTS ONLY), so an agent can pick the right tool without confusion.

Naming Consistency4/5

All names are lowercase snake_case and verb-oriented (search, resolve, fetch, operate, relate), giving a predictable pattern. The only minor deviation is list_sources, a two-word verb_noun form among single verbs, but it remains readable and consistent in style.

Tool Count5/5

Six tools is well-scoped for a multi-repo data aggregation server; each tool maps to a necessary capability (source listing, search, resolve, fetch, inspect, relate) with no redundant or filler entries. Nothing feels thin or bloated.

Completeness5/5

The surface covers the full workflow from source awareness (list_sources) through discovery (search), record retrieval (resolve), file download (fetch), remote inspection (operate), and cross-dataset linkage (relate). No obvious dead ends for the stated aggregation purpose; relate being hints-only is an explicit design choice rather than a gap.

Maintenance

ActivityActive
ResponsivenessSlow