orphanet-link
Related Servers
Alternatives to orphanet-link
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP 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
- AlicenseAqualityAmaintenanceMCP 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
- AlicenseAqualityFmaintenanceMCP server for Brazilian ICD-10 (CID-10) that enables search, lookup, hierarchy navigation, statistics, and validation of disease codes from official DATASUS data.61,258 npm1MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server for MARRVEL that enables AI agents to access genetics databases and variant analysis tools for rare disease research.20-
- AlicenseNot gradedqualityDmaintenanceMCP server for clinical and pharmaceutical data, enabling search of ClinicalTrials.gov, PubMed, FDA, and ICH guidelines without API keys.19 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server for searching and accessing RNA sequencing datasets from the European Nucleotide Archive (ENA), supporting bulk, single-cell, and spatial transcriptomics with advanced filtering and download capabilities.111Apache 2.0
TDQS
Scored across 19 tools
Most tools map to clearly distinct data facets, but get_disease can return xrefs, natural history, and other fields that have dedicated tools, and map_cross_ontology overlaps with get_disease's xrefs. The overlap is documented in descriptions, so an agent can still disambiguate, but it is not always obvious which tool is primary.
Tool names follow a consistent snake_case verb_noun pattern: get_disease_*, resolve_*, find_diseases_by_*, search_diseases, and batch variants extend the same pattern predictably. This makes the toolset easy to navigate and guess.
19 tools is on the heavy side for an MCP server, and some redundancy exists: get_disease can compose several facets that also have dedicated tools, and resolve_disease_batch/get_disease_batch add convenience but also surface area. The count is defensible for the breadth of Orphanet data, but feels slightly over-scoped.
The toolset covers the core Orphanet domain thoroughly: disease resolution and search, full disease records with genes/phenotypes/prevalence/natual-history/disability, reverse lookups by gene and phenotype, classification closure, external cross-reference mapping in both directions, and batch operations. There are no obvious dead ends or missing critical operations for a read-only data server.