metadome-link
Related Servers
Alternatives to metadome-link
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying Ensembl genomic data including gene lookup, sequence retrieval, homology, variation, and variant effect prediction via MCP tools.4 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables querying ClinGen curated evidence for gene-disease validity, dosage, actionability, and variant pathogenicity via MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables looking up genes, fetching sequences, predicting variant consequences, finding orthologs, and cross-database xrefs via Ensembl REST API through MCP.42 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceFederates 13 gene-related MCP backends (gnomAD, GTEx, etc.) behind a single Streamable HTTP endpoint with collision-free namespacing and search-based tool discovery.5MIT
- FlicenseAqualityDmaintenanceProvides tools to query, retrieve, and download protein structure data from the RCSB Protein Data Bank via the MCP protocol.5-
- AlicenseNot gradedqualityAmaintenanceRead-only biomedical MCP server connecting PubMed, ClinicalTrials.gov, ClinVar, gnomAD, OncoKB, Reactome, KEGG, UniProt, PharmGKB, CPIC, OpenFDA, Monarch Initiative, GWAS Catalog, and more. One command grammar for all biomedical entities — genes, variants, diseases, drugs, trials, articles, phenotypes, pathways, proteins, diagnostics, and adverse events. 27 tools. Apache-2.0 license.1Apache 2.0
TDQS
Scored across 11 tools
Tools are largely distinct with clear purposes. The async request/get pair for tolerance landscapes is well-defined, and get_tolerance_landscape vs get_position_tolerance differ by range granularity. Minor potential overlap between get_protein_domains and get_meta_domain could cause occasional misselection, but descriptions clarify.
Naming follows a consistent pattern: get_ for retrieval, request_ for initiating asynchronous operations, and resolve_ for transcript mapping. All snake_case with clear resource nouns. No mixed conventions or vague verbs.
11 tools is well-scoped for a variant tolerance analysis server. Each tool serves a distinct purpose without redundancy, and the count aligns with the domain's complexity.
The surface covers the full workflow: capabilities, diagnostics, transcript resolution, landscape retrieval (async and sync), positional tolerance, variant counts, comparison, domain annotations, and summary analysis. No obvious gaps for a read-only analysis server.