CaVa MCP server — read-only agentive access to OMOP vocab, cohorts, and clinical vocabularies.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cava-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# cava-mcp **cava-mcp** is an atomic, read-only MCP (Model Context Protocol) tool library for navigating the OMOP vocabularies. It exposes OMOP vocabulary lookups, embedding similarity search, cohort concept references, and system status as typed MCP tools that any MCP client can call — including [cava-datahub](https://github.com/AustralianCancerDataNetwork/cava-datahub), Claude Code, and autonomous agents. Read-only. No patient-level data. No write operations. ## What it exposes | Group | Tools | |---|---| | **Concept** | `concept_get`, `concept_by_code`, `concept_ancestors`, `concept_descendants`, `concept_relationships`, `concept_equivalency_path`, `concept_path`, `concept_map_to_standard`, `concept_neighbors` | | **Resolver** | `concept_ground` (with `parent_ids`, scoring fields, and `grounding_explanation`) | | **Search** | `concept_search_exact`, `concept_search_fulltext`, `concept_navigate_to_standard` | | **Embedding** | `embedding_index_status`, `embedding_neighbours`, `embedding_search`, `embedding_encode` | | **Cohort** | `cohort_find_concept_references` | | **System** | `system_status`, `system_vocabulary_catalogue` | Tools are registered conditionally — if an adapter is not configured, its tools are simply not registered. `system_status` and `system_vocabulary_catalogue` are always registered so clients can always query adapter availability. ## Quick start ```bash uv venv uv sync --extra dev --extra embedding-tools uv run cava-mcp --config config/cava-mcp.example.yaml --describe ``` Start the server: ```bash uv run cava-mcp --config config/cava-mcp.example.yaml ``` ## Example config ```yaml omop_graph: db_url: "postgresql+psycopg://user:pass@localhost:5432/omop" vocab_schema: omop_vocab omop_emb: enabled: true backend_type: pgvector db_url: "postgresql+psycopg://user:pass@localhost:5432/omop" default_model_name: qwen3-embedding:0.6b api_base: "http://localhost:11434/v1" api_key: "ollama" ``` ## Install matrix | Use ca…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.