Skip to main content
Glama
dna-seq

just-prs-mcp

by dna-seq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to just-prs-mcp

No user-submitted related servers found.

    Related Servers

    • literature-search-mcp

      PHoenixs57
      A
      license
      A
      quality
      B
      maintenance
      A standalone MCP server that searches multiple scholarly metadata providers (PubMed, Europe PMC, bioRxiv, Crossref, OpenAlex, Semantic Scholar, arXiv), deduplicates results, and returns ranked literature with optional open-access full-text retrieval from Europe PMC.
      3
      1
      Apache 2.0

    • 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

    • mcp-gwas-catalog

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying the GWAS Catalog (EBI/NHGRI), a curated catalog of genome-wide association studies. It enables AI agents to search and retrieve study data via natural language or direct tool calls.
      2 npm
      MIT

    • opentargets-mcp

      nickzren
      A
      license
      B
      quality
      D
      maintenance
      MCP server that exposes the Open Targets Platform GraphQL API as a set of tools for querying biomedical data such as targets, diseases, drugs, and genetic evidence.
      68
      150 PyPI
      19
      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.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target a distinct action-resource pair: search, info, compute, post-process, report, and job handling are clearly separated. The main ambiguity is between compute_prs_batch and compute_prs_by_trait, which both handle multiple scores, though their descriptions clarify the one-genome-vs-many-genomes distinction.

    Naming Consistency4/5

    The majority of tools follow a snake_case verb_noun pattern (compute_prs, list_genomes, build_prs_prompt, compare_genomes). A few noun-style names (best_performance, vcf_metainfo, percentile, absolute_risk, score_info, trait_info) break the pattern, but the overall convention remains predictable.

    Tool Count3/5

    At 20 tools, this is on the heavy side and spans a very wide pipeline from catalog search to VCF normalization to reporting. The count is defensible for the domain, but some tools like percentile, absolute_risk, and assess_quality are narrowly scoped and could conceivably be folded into compute/interpretation results.

    Completeness5/5

    The tool surface covers the full PRS lifecycle: discovery, input preparation, computation, interpretation, comparison, reporting, and async job recovery. There are no obvious dead ends — job IDs feed prs_job_status, result paths feed compare_genomes/build_prs_prompt/plot_trait_panel, and computed z-scores feed absolute_risk.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources