mitomap-link
Related Servers
Alternatives to mitomap-link
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables MCP clients to annotate and classify single human genetic variants in any notation, returning an auditable points-based ACMG verdict with its criteria, gnomAD frequencies, in-silico predictors, ClinVar data, and per-transcript consequences. It is read-only, requires no account or API key, and keeps answers compact while linking back to the source.6MIT- AlicenseNot gradedqualityBmaintenanceEnables querying ClinGen curated evidence for gene-disease validity, dosage, actionability, and variant pathogenicity via MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceLook up variant allele frequencies by ancestry, gene loss-of-function constraint, gene variant lists, and sequencing coverage over gnomAD — with ClinVar significance joined in — via MCP.253 npm1Apache 2.0
- AlicenseAqualityBmaintenanceMCP server that provides tools for querying the Human Phenotype Ontology (HPO) including term lookup, hierarchy exploration, cross-ontology mappings, and gene-phenotype-disease associations, all grounded in a local SQLite database for fast offline lookups.171MIT
- AlicenseAqualityBmaintenanceMCP server that provides tools to query harmonized gene-disease validity data from the Gene Curation Coalition, supporting consensus and conflict detection for gene-disease assertions.12MIT
- AlicenseNot gradedqualityBmaintenanceFederates 13 gene-related MCP backends (gnomAD, GTEx, etc.) behind a single Streamable HTTP endpoint with collision-free namespacing and search-based tool discovery.7MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: capability discovery, data-release diagnostics, single-allele lookup, and filtered search. The boundary between get_variant (exact allele resolution across notation formats) and search_variants (locus/disease/position filtering) is explicitly drawn in the descriptions, so an agent can pick correctly.
All four names follow a strict snake_case verb_noun pattern (get_server_capabilities, get_diagnostics, get_variant, search_variants). The verb choice also matches the operation type (get for single-target retrieval, search for filtered queries).
Four tools is on the lean side but appropriate for a narrow read-only reference-data server; each tool maps to a real need. The capabilities tool is somewhat meta and could arguably fold into documentation, keeping it just short of ideal scoping.
The core lifecycle for a read-only variant reference—discovery, version/health verification, exact lookup, and filtered search with pagination—is covered with no obvious dead ends. The main gap is batch/multi-allele lookup, which agents would have to loop over get_variant to achieve.