Skip to main content
Glama
berntpopp
by berntpopp

Related Servers

Alternatives to metadome-link

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Ensembl genomic data including gene lookup, sequence retrieval, homology, variation, and variant effect prediction via MCP tools.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying ClinGen curated evidence for gene-disease validity, dosage, actionability, and variant pathogenicity via MCP tools.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables looking up genes, fetching sequences, predicting variant consequences, finding orthologs, and cross-database xrefs via Ensembl REST API through MCP.
      42 npm
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Federates 13 gene-related MCP backends (gnomAD, GTEx, etc.) behind a single Streamable HTTP endpoint with collision-free namespacing and search-based tool discovery.
      5
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Provides tools to query, retrieve, and download protein structure data from the RCSB Protein Data Bank via the MCP protocol.
      5
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-only biomedical MCP server connecting PubMed, ClinicalTrials.gov, ClinVar, gnomAD, OncoKB, Reactome, KEGG, UniProt, PharmGKB, CPIC, OpenFDA, Monarch Initiative, GWAS Catalog, and more. One command grammar for all biomedical entities — genes, variants, diseases, drugs, trials, articles, phenotypes, pathways, proteins, diagnostics, and adverse events. 27 tools. Apache-2.0 license.
      1
      Apache 2.0

    TDQS

    C2.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools are largely distinct with clear purposes. The async request/get pair for tolerance landscapes is well-defined, and get_tolerance_landscape vs get_position_tolerance differ by range granularity. Minor potential overlap between get_protein_domains and get_meta_domain could cause occasional misselection, but descriptions clarify.

    Naming Consistency5/5

    Naming follows a consistent pattern: get_ for retrieval, request_ for initiating asynchronous operations, and resolve_ for transcript mapping. All snake_case with clear resource nouns. No mixed conventions or vague verbs.

    Tool Count5/5

    11 tools is well-scoped for a variant tolerance analysis server. Each tool serves a distinct purpose without redundancy, and the count aligns with the domain's complexity.

    Completeness5/5

    The surface covers the full workflow: capabilities, diagnostics, transcript resolution, landscape retrieval (async and sync), positional tolerance, variant counts, comparison, domain annotations, and summary analysis. No obvious gaps for a read-only analysis server.

    Maintenance

    ActivityActive
    ResponsivenessResponsive