icdwise
This server provides lookup, validation, and search of official U.S. ICD-10-CM diagnosis codes using verified government data, avoiding AI-fabricated descriptions.
lookup_icd10: Get the official description, canonical dotted form, and 3-character category for a given code (e.g.,E11.9→ "Type 2 diabetes mellitus without complications"). Returns an honest "not found" if the code isn't in the official dataset rather than guessing.validate_icd10: Check whether a code is both well-formed and exists in the official ICD-10-CM dataset — useful for catching fabricated, retired, or non-existent codes.search_icd10: Reverse lookup to find codes by condition keywords (e.g., "generalized anxiety" → F41.1). Results are sorted shortest (most general) first, with a configurable result limit (default 20).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@icdwise look up ICD-10 code E11.9"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
icdwise
Verified ICD-10-CM code lookup & validation for AI agents — official descriptions, not guesses.
Verified, trustworthy data tools for AI agents. "Qiniso" means "truth" in Zulu.
Website · npm · MCP endpoint · MCP Registry
Ask an LLM what an ICD-10-CM code means and it will answer confidently — and often wrongly: the wrong laterality, the wrong severity, the wrong condition entirely, and it will happily invent a description for a code that doesn't exist. icdwise looks the code up in the official U.S. ICD-10-CM code set and returns the real description — or an honest "not found" instead of a guess.
Asked to describe real ICD-10-CM codes, a frontier model with no tools was wrong ~38% of the time — e.g. it called
H40.1131"severe stage, right eye" (it's mild, bilateral) andT63.011A"ingested mushrooms" (it's rattlesnake venom) — and it fabricated a description for a code that doesn't exist. icdwise: the official text, or "not found." Never a guess.
Add it to Claude
Settings → Connectors → Add custom connector, and paste — no login, no key:
https://icdwise.qinisolabs.workers.dev/mcpStateless, reads no user data, requires no secrets. Prefer to run it locally over stdio? Add { "command": "npx", "args": ["-y", "icdwise"] } under mcpServers in your client config.
Related MCP server: mcp-clinicaltables
Use it as a library
npm i icdwiseimport { lookupIcd10, validateIcd10, searchIcd10 } from "icdwise";
lookupIcd10("E11.9").description; // "Type 2 diabetes mellitus without complications"
lookupIcd10("H40.1131").description; // "Primary open-angle glaucoma, bilateral, mild stage"
validateIcd10("E11.99").valid; // false — well-formed but not a real code
searchIcd10("generalized anxiety"); // → [{ code: "F41.1", description: "Generalized anxiety disorder" }, ...]Codes are accepted with or without the dot (E11.9 or E119). A well-formed code that isn't in the official set returns found: false with a clear note — it never invents a description.
Tools — 3
Tool | What it answers |
lookup_icd10 | The official description of a code (+ canonical form and 3-char category) |
validate_icd10 | Is this a real ICD-10-CM code? (well-formed and in the official set) |
search_icd10 | Reverse lookup — find the code(s) for a condition by keywords |
Data
ICD-10-CM is U.S. public-domain data (NCHS/CMS). The full code set (~74,000 codes) is bundled and generated from the official CMS release via npm run build-data <icd10cm-codes-YYYY.txt> (see scripts/build-data.mjs); every response reports the datasetVersion it used. Descriptions are the official text — the curated, versioned dataset kept current is the moat.
What it is not
Not medical advice, and not a determination of billability, coverage, or clinical appropriateness.
Not ICD-10 (WHO) or ICD-11 — this is ICD-10-CM (the U.S. Clinical Modification).
Not a guesser — unknown/retired/non-leaf codes return an honest "not found", never a fabricated description.
Architecture
A single TypeScript package exposing one MCP server over two transports — stdio (local / npx) and a Cloudflare Worker (hosted edge endpoint) — both driven by the same core.ts tool definitions, which also power the importable library.
npm install
npm run build
npm testPrivacy
This tool runs locally on your machine and is built not to collect, store, or transmit your data — no analytics, no telemetry, no account. All reference data is bundled — no network calls, and nothing leaves your device. Full policy: https://qinisolabs.github.io/privacy.html.
License
Apache-2.0. ICD-10-CM data is U.S. public domain (NCHS/CMS); see NOTICE.
Available Tools
3 toolslookup_icd10A
USE THIS to get the OFFICIAL description of an ICD-10-CM diagnosis code instead of recalling it — models confidently misstate the specifics (laterality, severity, encounter type) and invent descriptions for codes that don't exist. Returns the official description, the canonical dotted form, and its 3-character category; if the code is well-formed but not in the dataset it says so rather than guessing. Accepts codes with or without the dot (E11.9 or E119).
Inputs: code (required).
search_icd10A
USE THIS to find the ICD-10-CM code for a condition (reverse lookup) instead of guessing the code — e.g. 'type 2 diabetes' or 'generalized anxiety'. Returns official codes whose description contains all your search words, shortest (most general) first.
Inputs: query (required), limit.
validate_icd10A
USE THIS to check whether an ICD-10-CM code is real before relying on it — never assume a plausible-looking code exists. Returns whether it is well-formed AND present in the official code set, plus the description when valid. Catches fabricated or retired codes a model would otherwise accept.
Inputs: code (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: lookup retrieves description for a given code, search finds codes for a condition, and validate checks code existence. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (lookup_icd10, search_icd10, validate_icd10) using snake_case, making their actions predictable and clear.
Three tools are well-scoped for the domain of ICD-10-CM code management—lookup, search, and validate—each earning its place without redundancy or excess.
The tool set covers the fundamental operations for ICD-10-CM codes: lookup, reverse search, and validation. Minor gaps like hierarchical navigation exist, but the core workflow is complete.
Maintenance
Related MCP Connectors
ICD-10-CM / HCC medical coding tools with database-verified accuracy and denial-prevention rules.
ICD-10-GM, OPS, DRG, ZE, PEPP, DKR, SEG-4, ATC lookup for German coding, 2010-2027
WHO ICD-10/ICD-11 diagnosis codes. Lookup, search, chapters via official WHO API.
Polish ICD-10, ICD-9 PL, ICD-11 PL codes and NFZ JGP hospital grouping from official sources.
Related MCP Servers
- AlicenseAqualityDmaintenanceMedical terminology MCP server — ICD-10, MedDRA, RxNorm, CTCAE for AI agents620 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides 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.297 npmMIT

OMOPHub MCP Serverofficial
AlicenseAqualityBmaintenanceProvides AI agents with instant access to 10M+ OMOP medical vocabulary concepts for searching, mapping, and navigating clinical codes across SNOMED, ICD-10, RxNorm, LOINC, and more.11118 npm6MIT
Qinisoofficial
AlicenseAqualityCmaintenanceThe deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.561Apache 2.0