Medical Terminologies MCP

Find Equivalents Across Terminologies

find_equivalent

Read-onlyIdempotent

Ranked unified search for equivalent terms across multiple medical terminologies.

Use this tool to:

Find the same concept in different coding systems
Compare how terminologies represent a concept
Support terminology mapping and data integration

Searches across: ICD-11, LOINC, RxNorm, and MeSH. Set target_terminologies to limit which are searched, or set source_terminology to exclude one (e.g. when you already have a code from that terminology and want equivalents elsewhere). The two combine: source is subtracted from targets. limit caps candidates per terminology (default 5, max 10).

Every candidate carries match_score (lexical similarity to the search term, 0-1) and rank (global position across all searched terminologies) — both computed by this server, since upstreams don't expose comparable relevance scores. Candidates from different terminologies whose titles are lexically identical are clustered in groups — a strong same-concept signal (absence of a group is NOT evidence of non-equivalence).

Searches upstreams in English. For official pt-BR content, use the dedicated tools: icd11_search/mesh_search accept language: "pt", and cid10_search is natively Portuguese.

Input Schema

TableJSON Schema

Name	Required	Description
`term`	Yes	Medical term to search (e.g., "diabetes", "aspirin")
`limit`	No	Maximum candidates returned PER terminology (1-10, default 5). This is a cap, not a page: the live fan-out has no stable cursor across five upstreams, so raise the limit instead of paging.
`source_terminology`	No	If set, this terminology is excluded from the search. Use this when the term came from this terminology and you want equivalents in the others. Combines with target_terminologies by subtraction (source is removed from the target list).
`target_terminologies`	No	Limit the search to these terminologies. If omitted, all five are searched.

Output Schema

TableJSON Schema

Name	Required	Description
`term`	Yes
`groups`	Yes
`ranking`	Yes
`results`	Yes
`provenance`	Yes	One provenance block per upstream source that contributed to this response (licenses are never merged; each block carries the origin diagnostics of ITS source)
`attribution`	Yes	Canonical source URLs of this response (attribution list)
`source_terminology`	Yes
`searched_terminologies`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / properties / provenance / items / properties / notices / description

Previous value: -"Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none"New value: +"Caveats the source publishes about the data, verbatim (license statements are not repeated here; see the info://licenses resource). Absent when there is none"

Changed8 schema fields changedOct 8, 2026

changedOutput schema / properties / provenance / description

Previous value: -"One provenance block per upstream source that contributed to this response (contract v1.1; licenses are never merged; each block carries the origin diagnostics of ITS source)"New value: +"One provenance block per upstream source that contributed to this response (licenses are never merged; each block carries the origin diagnostics of ITS source)"

changedOutput schema / properties / provenance / items / description

Previous value: -"Bloco de proveniência (contrato v1.2): fonte, URL, competência, extração, diagnóstico de origem, citação e licença; e, só quando a resposta junta partes de origens ou momentos distintos, de onde veio cada parte"New value: +"Bloco de proveniência: fonte, URL, competência, extração, diagnóstico de origem, citação e licença; e, só quando há o que dizer, de onde veio cada parte, avisos da fonte, o que o servidor calculou e se o dado ainda pode mudar"

addedOutput schema / properties / provenance / items / properties / derivation_note

Added value: +{
+  "description": "What this server computed; present together with derived",
+  "type": "string"
+}

addedOutput schema / properties / provenance / items / properties / derived

Added value: +{
+  "description": "Present (true) only when this server computed the value (e.g. a ranking or summary statistics) instead of passing on what the source returned",
+  "type": "boolean"
+}

changedOutput schema / properties / provenance / items / properties / field_sources / description

Previous value: -"Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"New value: +"Present only when the response joins parts from different origins or extraction instants: for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses"

addedOutput schema / properties / provenance / items / properties / notices

Added value: +{
+  "description": "Notices the source publishes alongside the data (license statements, caveats), verbatim. Absent when there is none",
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

changedOutput schema / properties / provenance / items / properties / retrieval / description

Previous value: -"Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"New value: +"Origin diagnostics of THIS source in this call: requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"

addedOutput schema / properties / provenance / items / properties / revision

Added value: +{
+  "additionalProperties": false,
+  "description": "Whether the data can still change at the source: current = the version in force, the source may revise it; provisional = preliminary; final = will not change. Absent when unknown",
+  "properties": {
+    "note": {
+      "description": "O específico da fonte: o que revisa, quando, por quê",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "current = versão vigente, a fonte pode revisá-la; provisional = preliminar, incompleta ou sujeita a mudança (não compare como se fosse fechada); final = não muda mais, declarado pela fonte",
+      "enum": [
+        "current",
+        "provisional",
+        "final"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "note"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 6, 2026

changedOutput schema / properties / provenance / items / description

Previous value: -"Bloco de proveniência (contrato v1.1): fonte, URL, competência, extração, diagnóstico de origem, citação e licença"New value: +"Bloco de proveniência (contrato v1.2): fonte, URL, competência, extração, diagnóstico de origem, citação e licença; e, só quando a resposta junta partes de origens ou momentos distintos, de onde veio cada parte"

addedOutput schema / properties / provenance / items / properties / field_sources

Added value: +{
+  "description": "Present only when the response joins parts from different origins or extraction instants (contract v1.2): for each group of fields, its URL, extraction instant and whether it came from cache. Absent in single-origin responses",
+  "items": {
+    "additionalProperties": false,
+    "description": "Proveniência de um grupo de campos da resposta: de onde veio e quando foi extraído",
+    "properties": {
+      "data_vintage": {
+        "description": "Vintage/competência da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "dataset_id": {
+        "description": "Identificador do conjunto da sub-fonte",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fields": {
+        "description": "Campos do payload atribuídos a esta sub-fonte",
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "retrieved_at": {
+        "description": "ISO-8601 da extração desta sub-fonte na origem",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "served_from_cache": {
+        "description": "true se esta sub-fonte veio do cache do servidor (retrieved_at é o da extração original); false se foi buscada nesta chamada; null se o servidor não distingue",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "source_url": {
+        "description": "URL canônica da sub-fonte que originou estes campos",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fields",
+      "source_url",
+      "dataset_id",
+      "data_vintage",
+      "retrieved_at"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

Changed7 schema fields changedOct 4, 2026

changedInput schema / properties / source_terminology / enum

Previous value: -[
-  "icd11",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh"
-]New value: +[
+  "icd11",
+  "loinc",
+  "rxnorm",
+  "mesh"
+]

changedInput schema / properties / target_terminologies / items / enum

Previous value: -[
-  "icd11",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh"
-]New value: +[
+  "icd11",
+  "loinc",
+  "rxnorm",
+  "mesh"
+]

changedOutput schema / properties / groups / items / properties / members / items / properties / terminology / enum

Previous value: -[
-  "icd11",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh"
-]New value: +[
+  "icd11",
+  "loinc",
+  "rxnorm",
+  "mesh"
+]

changedOutput schema / properties / groups / items / properties / terminologies / items / enum

Previous value: -[
-  "icd11",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh"
-]New value: +[
+  "icd11",
+  "loinc",
+  "rxnorm",
+  "mesh"
+]

removedOutput schema / properties / results / properties / snomed

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "error": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "found": {
-      "type": "boolean"
-    },
-    "items": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "type": "string"
-          },
-          "match_score": {
-            "maximum": 1,
-            "minimum": 0,
-            "type": "number"
-          },
-          "rank": {
-            "maximum": 9007199254740991,
-            "minimum": 1,
-            "type": "integer"
-          },
-          "title": {
-            "type": "string"
-          },
-          "uri": {
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "required": [
-          "code",
-          "title",
-          "uri",
-          "match_score",
-          "rank"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "found",
-    "error",
-    "items"
-  ],
-  "type": "object"
-}

changedOutput schema / properties / searched_terminologies / items / enum

Previous value: -[
-  "icd11",
-  "snomed",
-  "loinc",
-  "rxnorm",
-  "mesh"
-]New value: +[
+  "icd11",
+  "loinc",
+  "rxnorm",
+  "mesh"
+]

changedOutput schema / properties / source_terminology / anyOf

Previous value: -[
-  {
-    "enum": [
-      "icd11",
-      "snomed",
-      "loinc",
-      "rxnorm",
-      "mesh"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "icd11",
+      "loinc",
+      "rxnorm",
+      "mesh"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed4 schema fields changedSep 27, 2026

changedOutput schema / properties / provenance / description

Previous value: -"One provenance block per upstream source that contributed to this response (contract v1.0; licenses are never merged)"New value: +"One provenance block per upstream source that contributed to this response (contract v1.1; licenses are never merged; each block carries the origin diagnostics of ITS source)"

addedOutput schema / properties / provenance / items / description

Added value: +"Bloco de proveniência (contrato v1.1): fonte, URL, competência, extração, diagnóstico de origem, citação e licença"

addedOutput schema / properties / provenance / items / properties / retrieval

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "anomalies": {
+          "description": "Anomalias superadas até o sucesso, somadas por classe, em ordem fixa; [] se nenhuma",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "count": {
+                "description": "Ocorrências desta classe na chamada",
+                "maximum": 9007199254740991,
+                "minimum": 1,
+                "type": "integer"
+              },
+              "kind": {
+                "description": "Classe da anomalia (vocabulário fechado do contrato)",
+                "enum": [
+                  "timeout",
+                  "network",
+                  "http_4xx",
+                  "http_5xx",
+                  "rate_limited",
+                  "malformed_body"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "count"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "attempts": {
+          "description": "Tentativas somadas, incluindo as repetidas (>= requests)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "requests": {
+          "description": "Idas distintas à origem que compõem esta resposta (fatias, páginas)",
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "unstable": {
+          "description": "true se houve repetição (attempts > requests) ou alguma anomalia",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "requests",
+        "attempts",
+        "anomalies",
+        "unstable"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Origin diagnostics of THIS source in this call (contract v1.1): requests made to the upstream, attempts summed across retries, anomalies worked around (kind + count); unstable=true when any anomaly happened. null when nothing was measured (bundled dataset, or response served entirely from cache)"
+}

changedOutput schema / properties / provenance / items / required

Previous value: -[
-  "source",
-  "source_url",
-  "data_vintage",
-  "retrieved_at",
-  "citation",
-  "license"
-]New value: +[
+  "source",
+  "source_url",
+  "data_vintage",
+  "retrieved_at",
+  "retrieval",
+  "citation",
+  "license"
+]

Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds context they cannot: match_score/rank are computed by this server rather than upstreams, lexical-title clustering signals same-concept, absence of a group is explicitly NOT evidence of non-equivalence, the search is English-only, and limit is a cap because there is no stable cursor. These are non-obvious behavioral traits an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then a bulleted use-case block, then a scoped paragraph covering parameters and ranking semantics, then a routed language note. Dense but every sentence carries distinct information; nothing is redundant boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists and return values need not be described, the definition still explains the meaning of match_score, rank, and groups plus the important caveat about absent groups, and it maps the language limitation to the right sibling tools. Complete for an agent to invoke and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the interaction rule (source is subtracted from targets), the default/max for limit, and why limit should not be used for paging. This adds genuine meaning beyond the per-field schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Ranked unified search for equivalent terms') and immediately differentiates itself from the single-terminology siblings by naming the four upstreams it unifies (ICD-11, LOINC, RxNorm, MeSH). An agent can tell this is a cross-terminology mapping tool rather than another search tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Enumerates three concrete use cases (find same concept, compare representations, support mapping/integration) and explicitly routes pt-BR queries to alternatives ('icd11_search'/'mesh_search' with language:"pt", 'cid10_search'). The source_terminology note also states exactly when to use it ('when you already have a code from that terminology').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Medical Terminologies MCP tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.