Skip to main content
Glama

Related Servers

Alternatives to Medical Terminologies MCP

  • -
    license
    Not graded
    quality
    Not graded
    maintenance
    A FastAPI backend service that connects to Azure's Managed Chat Project using GPT-4o to provide medical chatbot functionality through a simple HTML interface.
    -
  • A
    license
    Not graded
    quality
    F
    maintenance
    Provides comprehensive medical information by querying authoritative sources including FDA drug database, WHO health statistics, PubMed literature, RxNorm nomenclature, Google Scholar, and Australia's PBS API through 22+ specialized tools.
    50
    3
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server and web application that enables natural language medical queries and patient data analysis powered by Gemini AI. It allows users to track and analyze patient biometrics, including vitals, sleep patterns, and laboratory results, through a comprehensive set of automated medical tools.
    -

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    A high-performance MCP server that gives LLMs access to 25 biomedical tools federated across 50+ upstream APIs for genes, variants, drugs, diseases, literature, clinical trials, and structural biology.
    41
    522
    12
    Apache 2.0
  • A
    license
    A
    quality
    A
    maintenance
    An MCP server that gives AI assistants access to biological and biomedical RDF databases via SPARQL at the RDF Portal, as well as selected REST APIs (NCBI E-utilities, UniProt, ChEMBL, PDB, Reactome, Rhea, MeSH, and more).
    29
    13
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that provides access to the NIH UMLS API and the NIH VSAC FHIR API. This server enables AI models to search medical terminology, look up concept definitions, explore relationships between medical concepts, map codes between different medical coding systems, and work with curated clinical value sets.
    1
    MIT

TDQS

A3.9/5.0

Scored across 31 tools

Disambiguation4/5

Tools are clearly separated by terminology and by action (search vs lookup vs hierarchy), so agents can generally pick the right one. A few potential overlaps exist (mesh_descriptor vs mesh_tree, rxnorm_concept vs rxnorm_ingredients, validate_codes vs map_icd10_to_icd11), but descriptions provide enough differentiation. No two tools appear to do the exact same thing.

Naming Consistency3/5

Within each terminology namespace, names are fairly consistent (e.g., icd11_search/lookup/hierarchy, loinc_search/details), but across terminologies the action for fetching detailed info varies: lookup, descriptor, details, and concept. There are also minor singular/plural inconsistencies (cid10_chapter vs cid10_chapters) and a misleading map_loinc_to_snomed that does not actually perform mapping.

Tool Count4/5

31 tools feels high at first glance, but the server covers eight distinct terminology systems plus cross-cutting mapping, validation, and versioning utilities. Each terminology generally gets 3-5 purpose-driven tools (search, lookup, hierarchy, specialized details), so the count is justified by the broad domain rather than padded with redundant duplicates.

Completeness3/5

The server provides solid coverage for ICD-11, CID-10, MeSH, LOINC, RxNorm, and ATC, including search, lookup, hierarchy, and specialized features. The main gap is the lack of dedicated SNOMED CT tools—SNOMED is only accessible indirectly via find_equivalent and validate_codes, with no way to retrieve full concept details or hierarchy. ICD-10 also lacks a direct international search, but mapping and validation tools partially compensate.

Maintenance

ActivityActive
ResponsivenessWithin a week