Skip to main content
Glama
OMOPHub

OMOPHub MCP Server

Official
by OMOPHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OMOPHub MCP Server

No user-submitted related servers found.

    Related Servers

    • snowstorm-mcp-server by IHTSDO

      snowstorm-mcp-serverofficial

      IHTSDO
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to look up, search, validate, navigate hierarchies, and expand value sets for SNOMED CT clinical terminology through the Model Context Protocol.
      8
      Apache 2.0

    • ICD MCP Server

      stayce
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants instant access to WHO ICD-10 and ICD-11 classification systems for code lookup, search, autocoding, validation, and hierarchy browsing via 12 tool actions.
      2
      MIT

    • mcp-clinicaltables

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides keyless access to NIH clinical data including ICD-10/9, RxTerms, LOINC, NPI, and conditions search, allowing AI agents to query medical terminologies without authentication.
      254 npm
      MIT
    • vClinic MCP Server by v-clinic

      vClinic MCP Serverofficial

      v-clinic
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage virtual clinic data including patients, visits, diagnoses, treatments, lab/radiology orders, and search medical literature and internal knowledge base.
      -

    • Redis Graph MCP Server

      yskale
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and AI agents to query a biomedical knowledge graph stored in RedisGraph, with tools for concept search, synonym enrichment, and study variable discovery through semantic relationships.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation2/5

    search_concepts, semantic_search, and find_similar_concepts all return concepts from free-text input and overlap heavily, especially since find_similar_concepts defaults to semantic matching. explore_concept also duplicates the combined output of get_concept, get_hierarchy, and map_concept, making the granular tools harder to choose. Detailed descriptions help, but an agent would frequently need to guess which search-style tool is intended.

    Naming Consistency4/5

    Most tools follow a verb_object snake_case pattern such as search_concepts, get_concept, map_concept, and list_vocabularies. semantic_search is a noun phrase rather than a verb command, and fhir_resolve / fhir_resolve_codeable_concept place 'fhir' before the verb, but these deviations are minor and still predictable.

    Tool Count4/5

    11 tools is within the ideal 3-15 range and not excessive for an OMOP vocabulary server. However, find_similar_concepts/search_concepts/semantic_search and explore_concept/get_concept/map_concept/get_hierarchy overlap, so the set is slightly heavier than necessary even though the count is reasonable.

    Completeness5/5

    The set covers concept searching, detail retrieval, code lookup, hierarchy navigation, cross-vocabulary mappings, vocabulary metadata, and FHIR resolution—no obvious dead ends. It supports the full typical workflow of finding and resolving concepts from terms, codes, or FHIR resources. Niche relationship types or bulk operations are missing, but they appear outside the stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources