Back to search
100
MCP live MCP 2025-11-25 http

omophub

mcp.omophub.com

Access OHDSI standardized medical vocabularies — search concepts, navigate hierarchies, and map between clinical coding systems like SNOMED CT, ICD-10, RxNorm, and LOINC.

Watch this dependency Share evidence report
Uptime
100.0%
3 direct probes · 30d
Response
586ms
last probe
Tools
11
callable
Resources
1
readable
Prompts
2
available
Primary URL
https://mcp.omophub.com/mcp
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
11 tools, 1 resources, 2 prompts returned.
pass 3 or more catalogue items 10/10
14 items in total; 3 or more earns these points.
pass Describes itself 10/10
170 characters; more than 30 earns these points.

Tools · 11

search_concepts

Search for medical concepts across OHDSI standardized vocabularies by name, synonym, or clinical term. Returns matching concepts with IDs, names, vocabulary, domain, and standard status. Use this when…

semantic_search

Search for medical concepts using natural language with neural embeddings. Unlike keyword search, semantic search understands clinical meaning — 'heart attack' finds 'Myocardial infarction', 'high blo…

find_similar_concepts

Find medical concepts similar to a reference concept, name, or natural language query. Supports three algorithms: 'semantic' (neural embeddings — best for meaning, and the default), 'lexical' (text ma…

get_concept

Get detailed information about a specific OMOP concept by its numeric concept_id. Returns the concept name, vocabulary, domain, concept class, standard status, valid dates, and synonyms. Use this when…

get_concept_by_code

Look up an OMOP concept using a vocabulary-specific code and vocabulary ID. Both parameters are required to avoid ambiguity - the same code can exist in multiple vocabularies (e.g., 'E11' exists in bo…

explore_concept

Get a comprehensive view of a medical concept in one call: detailed info, ancestors/descendants hierarchy, and cross-vocabulary mappings. Use this instead of calling get_concept + get_hierarchy + map_…

map_concept

Find mappings FROM a source concept TO equivalent concepts in other vocabularies. The concept_id you provide is always the SOURCE — results show what it maps TO. Returns cross-vocabulary mappings with…

get_hierarchy

Navigate the vocabulary hierarchy for a concept. Use direction='up' for ancestors (broader terms like 'Diabetes mellitus' → 'Metabolic disease'), direction='down' for descendants (narrower terms, esse…

list_vocabularies

List all available medical vocabularies in the OMOP standardized vocabulary system with concept counts and metadata. Use this to understand what terminology systems are available (SNOMED CT, ICD-10-CM…

fhir_resolve

Resolve a FHIR coded value (system URI + code) to its OMOP standard concept and CDM target table. Supports text-only input via semantic search fallback and optional Phoebe recommendations. Examples: s…

fhir_resolve_codeable_concept

Resolve a FHIR CodeableConcept with multiple codings. Picks the best match per OHDSI vocabulary preference (SNOMED > RxNorm > LOINC > CVX > ICD-10). Falls back to the text field via semantic search if…

Resources · 1

vocabulary-list omophub://vocabularies

Prompts · 2

phenotype-concept-set

Build a concept set for a clinical phenotype definition. Guides the AI through searching for concepts, exploring hierarchies, and assembling a complete concept set.

code-lookup

Look up and validate a medical code. Resolves a vocabulary-specific code to its OMOP concept and shows mappings.

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://mcp.omophub.com/mcp

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "omophub": {
      "url": "https://mcp.omophub.com/mcp",
      "transport": "http"
    }
  }
}