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.
    97 npm
    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.
    43
    200 npm
    12
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for connecting Claude Desktop to FHIRfly healthcare reference data APIs, enabling lookup of drugs, providers, clinical codes, and more.
    96 npm
    MIT
  • 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).
    2
    29
    21
    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.
    2
    MIT

TDQS

A3.9/5.0

Scored across 33 tools

Disambiguation4/5

Most tools are clearly distinguished by both terminology prefix and operation (search vs lookup vs hierarchy vs validation). The main ambiguity is between the generic catalog `search`/`fetch` tools and the terminology-specific search tools, though descriptions explicitly warn that the former is a catalog index, not a data query.

Naming Consistency4/5

Almost all tools follow a predictable snake_case `terminology_action` pattern (loinc_search, rxnorm_concept, icd11_hierarchy, cid10_lookup, mesh_tree, atc_members). The generic `search`, `fetch`, `find_equivalent`, and `harmonize_terms` names break the prefix pattern but remain readable and descriptive.

Tool Count3/5

At 33 tools the surface is heavy for an agent, even accounting for the server covering seven terminologies plus cross-cutting mapping and validation. Most tools earn their place, but the total is well above the typical well-scoped range and invites cognitive overload.

Completeness4/5

Coverage is strong: search/lookup/hierarchy/details for LOINC, RxNorm, MeSH, CID-10, ICD-11, and ATC, plus mapping, batch validation, harmonization, version metadata, and generic catalog access. The main gap is the lack of a direct international ICD-10 search tool, despite ICD-10 being used in mapping and validation.

Maintenance

ActivityActive
ResponsivenessSyncing