strchive-link
Related Servers
Alternatives to strchive-link
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query clinical genomics databases, retrieve supporting literature, analyze population genetics, and visualize biological pathways.18MIT
- AlicenseAqualityBmaintenanceEnables AI agents to retrieve cited pharmacogenomic and gene-variant information, including drug–gene guidance from CPIC/DPWG and rsID lookups, so responses can quote curated sources instead of relying on memory. A local package also lets users read raw DNA files on their own computer without sending the file data to the remote service.2278 PyPIMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to query genetic variant data, gene constraints, and population genetics information from the gnomAD (Genome Aggregation Database) through its GraphQL API. Supports searching for genes and variants, retrieving constraint scores, analyzing population frequencies, and accessing genomic coverage data.910MIT
- AlicenseNot gradedqualityDmaintenanceProvides programmatic access to curated SNP data by trait, enabling LLM-powered applications to search, interpret, and discover genetic variants.MIT
- AlicenseAqualityDmaintenanceEnables AI-driven pharmacogenomic analysis by querying structured genetic variant, drug response, and disease risk data. Supports natural language questions about medications, traits, and health risks based on user genome data, with privacy-first local execution.1625 npm12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up approved human genes by official symbol, fuzzy-search symbols, names and aliases, and reverse-map external database identifiers (Entrez, Ensembl, UniProt, OMIM, RefSeq, UCSC) back to canonical gene records with full annotations and cross-references.128 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly different object: server metadata (get_server_capabilities), data provenance (get_diagnostics), catalog search (search_loci), single-record fetch (get_locus), and a derived comparison (compare_repeat_length). The search/fetch pair is a standard, well-understood split, and compare_repeat_length is explicitly distinguished from get_locus as a descriptive comparison rather than a record dump. No two tools appear interchangeable.
All five names follow a strict snake_case verb_noun pattern (get_*, search_*, compare_*), with the verb accurately signaling the operation type. No camelCase or stylistic mixing.
Five tools is a tight, well-earned surface for a read-only locus lookup service: discovery, diagnostics, search, fetch, and one analytical helper. Nothing appears redundant or missing at the count level.
The read-only lifecycle for the domain is well covered: enumerate/search, retrieve full record, interpret an observation against ranges, plus provenance and capability discovery. Minor gaps remain, such as querying loci by genomic coordinate/region or comparing multiple loci or samples in one call, which an agent would have to loop over manually.