A
licenseNot graded
qualityD
maintenanceEnables AI agents to query clinical genomics databases, retrieve supporting literature, analyze population genetics, and visualize biological pathways.
18
MIT
DeepDNA MCP server
by alfonsoguv
Related Servers
Alternatives to DeepDNA MCP server
No user-submitted related servers found.
Related Servers
- 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.1628 npm12MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative sources like FDA, WHO, PubMed, RxNorm, and Google Scholar for drug information, health statistics, clinical guidelines, trials, and medical literature. It runs locally with no API keys, so data stays private while results come back with evidence grading and resilient fallbacks.56 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables real-time pharmacogenomics analysis, including variant clinical significance, drug-gene interactions, and dosing guidelines, by connecting to ClinVar, PharmGKB, gnomAD, and other databases.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative medical sources such as FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, safety data, health statistics, clinical guidelines, pediatric resources, and evidence-graded literature. Runs locally with no API keys or data leaving the machine.56 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query authoritative sources such as the FDA, WHO, PubMed, RxNorm, and ClinicalTrials.gov for drug information, health statistics, clinical guidelines, and literature with evidence grading. It runs locally with no API keys required, adding rate limiting, circuit breakers, caching, and health monitoring for reliable private access.56 npmISC
TDQS
A4.4/5.0
Scored across 2 tools
Disambiguation5/5
The two tools are cleanly separated: read_dna_file operates on a local DNA file and reports variant states, while lookup_drug_gene is a read-only query against a remote pharmacogenomic API. There is no plausible way to confuse one for the other, and each description reinforces the boundary.
Naming Consistency5/5
Both names follow the same verb_noun snake_case pattern (read_dna_file, lookup_drug_gene), with verbs drawn from the same read-verb family and concrete noun objects. No casing or convention drift.
Tool Count3/5
Two tools is on the thin side even for a narrowly scoped read-only domain, though each tool is substantive rather than trivial. A helper for listing curated genes/variants or mapping drugs to genes would round out the surface.
Completeness3/5
The core loop (read a DNA file, then fetch gene/drug guidance) is covered, but there is no way to enumerate which variants or genes the record curates, discover which drugs map to a gene, or search a record by rsID. Agents must already know the gene names to pass in, which is a notable gap.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive