Skip to main content
Glama
berntpopp

gencc-link

by berntpopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gencc-link

No user-submitted related servers found.

    Related Servers

    • orphanet-link

      berntpopp
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables querying rare-disease data from Orphanet, including disease nomenclature, cross-references, classifications, gene associations, HPO phenotypes, epidemiology, and natural history.
      19
      MIT

    • clingen-link

      berntpopp
      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

    • mcp-mygene-info

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for querying gene annotations, full-text gene search, and species taxonomy via MyGene.info. Enables AI agents to access gene data through natural language questions.
      180 npm
      MIT

    • string-db

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for STRING-DB that enables querying protein-protein interaction networks, functional enrichment, and homology mappings.
      179 npm
      MIT

    • genefoundry

      berntpopp
      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.
      6
      MIT
    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

    A4.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear separation between browse/filter, per-gene, per-disease, and pair-level queries. Minor overlap exists between get_server_capabilities and get_gencc_diagnostics (both expose version/freshness metadata) and between resolve_identifier, search_genes, and search_diseases, though the detailed descriptions mitigate most ambiguity.

    Naming Consistency5/5

    All tools use a consistent snake_case verb_noun pattern: get_, search_, find_, resolve_, and list_. Singular/plural pairs like get_gene_curations vs get_genes_curations and get_disease_curations vs get_diseases_curations are systematic and predictable.

    Tool Count5/5

    12 tools is well-scoped for a specialized read-only GenCC data server. Each operation earns its place: search/resolve entry points, single and batch retrieval variants, a filtered browse endpoint, a pair-level deep dive, submitter lookup, and metadata/diagnostics.

    Completeness5/5

    The surface covers the full read-only workflow: resolving identifiers, searching genes and diseases, retrieving assertions by gene or disease, browsing all curations, and listing submitters. Diagnostics and capabilities support efficient client behavior, with no apparent dead-end workflow for the domain.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources