medical-codes-mcp-server
io.github.cyanheads/medical-codes-mcp-servercyanheadsstreamable-httpv0.5.2Scanned
Offline US medical code lookup and crosswalk — ICD-10-CM/PCS, HCPCS Level II, RxNorm. Keyless.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the medical-codes-mcp-server can do
The medical-codes-mcp-server is published by the GitHub account cyanheads. It has 6 tools. It can create or change data (2 tools: medcode_check_code and medcode_map_codes), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (medcode_browse_hierarchy).
The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.5.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 2Claude Code: ask
medcode_check_codeValidate whether a US medical code exists, is current, and is billable in the active bundled release.1 finding
Why it is in this group
- The description's first verb is "validate": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "medcode_check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "validate": a word for reading.
Description, as the server wrote it Validate whether a US medical code exists, is current, and is billable in the active bundled release. Returns a discriminated status — valid_billable, valid_not_billable, valid_header, valid, or terminated — with a `whyNot` explaining non-billable and terminated cases (e.g. "valid ICD-10-CM category but not billable — submit a more specific child code"). A HCPCS code is terminated once its last valid date has passed; before then it checks as billable, with that date in `whyNot`. This is the detail a coder needs before submitting a claim. RxNorm has no billing concept, so a current RxNorm concept is `valid` with `billable: null` and no billing verdict. Auto-detects the system from the code's shape, and a code written in ICD-10-CM dotted form (`A01.00`) resolves to ICD-10-CM; pass an explicit `system` to disambiguate. A non-billable or terminated code is a successful result with a whyNot, not an error — only a code absent from the named system, or with no `system` from every bundled system, raises unknown_code, which names the other bundled system that holds the code, or every system the code's shape fits. A value in ICD-9-CM form — a dotted all-digit code (`250.00`, `00.1`) or an external-cause code (`E880.9`) — resolves in no bundled system, with or without `system`, and its miss says ICD-9-CM is not bundled; an ICD-10-PCS section value from medcode_browse_hierarchy (`0`) checked under system ICD10PCS is named as a section, not a code. A code string that also exists in another bundled system carries `alsoInSystems` naming it, since the verdict applies only to the system that answered.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
medcode_map_codesCrosswalk a US medical code or drug across systems and within a hierarchy.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 3,007 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ss directions, and a `system` other than RXNORM on the drug and class directions."
Description, as the server wrote it Crosswalk a US medical code or drug across systems and within a hierarchy. Hierarchy directions: `parents` and `children` walk a code's hierarchy one level per call — immediate parent/children only (depth-1); call iteratively for the full ancestor or descendant path. ICD-10-CM and HCPCS walk the prefix hierarchy, stepping past an ICD-10-CM level padded with the placeholder X that is not itself a code (the parent of `S82.66XA` is `S82.66`); an ICD-10-PCS three-character table row's children are the complete codes that begin with it, and a complete code's parent is its table row; RxNorm concepts have no code hierarchy. A resolvable source with no edge in the requested direction is a successful empty result with a notice, not an error. A source code string that also exists in another bundled system carries `alsoInSystems` naming it, since only the resolved system's hierarchy was walked. Drug directions (RxNorm): `name_to_rxcui` (drug name → RXCUI; one name matches ingredients, combinations, and products alike, each hit tagged with its `conceptType`), `ndc_to_rxcui` and `rxcui_to_ndc` (NDC ↔ RXCUI; NDCs accepted hyphenated in an FDA segment configuration — 4-4-2, 5-3-2, 5-4-1, or the 11-digit 5-4-2 — or as bare 10/11 digits; `ndc_to_rxcui` names the product it decoded to and its `conceptType`), `rxcui_to_ingredients` and `rxcui_to_brands` (RXCUI → ingredient/brand RXCUIs, each with the target's RxNorm name and its `conceptType` — read that before counting a combination product's ingredients). Drug-class directions (RxClass): `rxcui_to_classes` (RXCUI → its classes: pharmacologic class, mechanism of action, physiologic effect, pharmacokinetics, therapeutic category, chemical structure, the diseases it may treat, prevent, diagnose, or induce or is contraindicated with, VA class, DEA controlled-substance schedule, CDC vaccine code; a drug product also carries its ingredients' classes, naming the ingredient in `via`, while DEA schedules are recorded only on drug products and VA classes almost only there, so map a product for those) and `class_to_rxcuis` (class ID → its direct member RXCUIs, each with its RxNorm name and `conceptType`). Each class hit carries `classType`, `source` (the RxClass source asserting it), and `relation` — a `ci_` relation is a contraindication, not an indication; narrow either direction with `classType`. Every result carries `source` provenance (which system or edge answered) so a chained call (e.g. into openfda with a resolved NDC) uses the right identifier. The `children`, `name_to_rxcui`, `rxcui_to_ndc`, `rxcui_to_classes`, and `class_to_rxcuis` directions can return large sets and paginate: a `nextCursor` in the response is passed back as `cursor` (with an optional `limit` page size) to walk the full set. A field the direction does not use is rejected with `field_not_applicable`: `limit` and `cursor` on the point directions, `classType` outside the class directions, and a `system` other than RXNORM on the drug and class directions.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
medcode_browse_hierarchyWalk a US medical code system's hierarchy for discovery without a search term.Reads text others writeNo findings
Why it is in this group
- The name "medcode_browse_hierarchy" says "browse": a word for reading.
What it can reach
- untrusted-inputThe name "medcode_browse_hierarchy" says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Walk a US medical code system's hierarchy for discovery without a search term. With no `node`, returns the top-level entries (ICD-10-CM categories, HCPCS range buckets, or ICD-10-PCS first-axis values). With a `node`, returns its immediate children. ICD-10-CM and HCPCS use a prefix hierarchy (a shorter code is the parent of a longer one); ICD-10-PCS is axis-based — each of its 7 characters is an independent axis (section, body system, root operation, body part, approach, device, qualifier), but only the top-level Section axis is browsable (omit `node`): positions 2–7 are context-dependent on the preceding axis path and are not enumerable from a flat partial code, so list the complete codes in a three-character ICD-10-PCS table row with medcode_map_codes (direction children) instead. Lets an agent orient in an unfamiliar system or enumerate a category's specific codes. A large child set paginates: when the response carries a `nextCursor`, pass it back as `cursor` to fetch the next page.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
medcode_get_codeDecode one or more US medical codes to their official descriptions across ICD-10-CM (diagnoses), ICD-10-PCS (inpatient procedures), HCPCS Level II (supplies/drugs/services), and Rx…1 finding
Why it is in this group
- The name "medcode_get_code" says "get": a word for reading.
Findings
- Info
The description is 2,940 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ng it, so a single answer to a colliding code is never mistaken for the only one."
Description, as the server wrote it Decode one or more US medical codes to their official descriptions across ICD-10-CM (diagnoses), ICD-10-PCS (inpatient procedures), HCPCS Level II (supplies/drugs/services), and RxNorm (drugs, by RXCUI). Also decodes a National Drug Code (NDC) directly to its RxNorm product offline, tagged `source: "NDC"` — hyphenated in an FDA segment configuration (4-4-2, 5-3-2, 5-4-1, or the 11-digit 5-4-2) or as bare 10/11 digits; any other segment widths are malformed and stay unresolved. Auto-detects the system from each code's shape, and a code written in ICD-10-CM dotted form (`A01.00`) resolves to ICD-10-CM; pass an explicit `system` only when a value is genuinely ambiguous. Accepts 1–50 codes and returns partial success: resolved codes in `found`, unresolved in `notFound` with a per-code reason, so one bad code never fails the batch. Each reply holds `structuredContent` and the text to 24,000 bytes apiece: codes are decoded in request order, and once one has resolved, a code that would carry the reply past that budget is returned unprocessed in `deferred` with every code after it, each as sent — trimmed when its padding alone carries it past 64 characters, and cut to its first 64 trimmed characters and `…` when it is longer than that once trimmed — re-call with `codes` set to `deferred` and the same `system` and `includeHierarchy` until no `deferred` comes back. Three kinds of code are never deferred and can carry a reply past the budget: the first code that resolves, returned whole; the codes before it; and the unresolved codes after the last one that resolves, so a re-call always holds a code that resolves. Only a batch where nothing resolves fails: with ambiguous_system and `candidateSystems` when every code exists in more than one bundled system, otherwise with no_codes_found. Set `includeHierarchy` to attach each code's parent and immediate children (with a `childrenTruncated` flag when a code has more children than the cap returns — walk the full set via medcode_map_codes, or medcode_browse_hierarchy outside ICD-10-PCS); an ICD-10-PCS table row's children are the complete codes that begin with it. The resolved `system` is echoed on every result for chaining into a billability check or a medcode_map_codes parents/children walk; a bare integer that resolves nowhere is named as a possible CPT / HCPCS Level I code, which is out of scope, except a bare 10/11-digit one, which is named as an NDC no bundled drug maps to; a value in ICD-9-CM form — a dotted all-digit code (`250.00`, `00.1`) or an external-cause code (`E880.9`) — resolves in no bundled system and is named as ICD-9-CM, which is not bundled; an ICD-10-PCS section value from medcode_browse_hierarchy (`0`) looked up under system ICD10PCS is named as a section, not a code; a code string that also exists in another bundled system carries `alsoInSystems` naming it, so a single answer to a colliding code is never mistaken for the only one.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
medcode_list_systemsList the bundled US medical code systems with their release identifiers, effective dates, and code counts, and the RxClass drug-class layer the class crosswalks read, with each sou…No findings
Why it is in this group
- The name "medcode_list_systems" says "list": a word for reading.
Description, as the server wrote it List the bundled US medical code systems with their release identifiers, effective dates, and code counts, and the RxClass drug-class layer the class crosswalks read, with each source’s version. Confirms which ICD-10-CM fiscal year, ICD-10-PCS fiscal year, HCPCS Level II release, RxNorm normalized set, and RxClass sources are active before acting on any decode, search, or crosswalk result. The corpus is offline and built at package-build time — this call reports exactly which release is baked into the running server. ICD-10-CM/PCS are the US clinical modifications, not the ICD-10/ICD-11 base.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
medcode_search_codesFind US medical codes whose official descriptions match a described concept, via full-text search over the bundled index.No findings
Why it is in this group
- The name "medcode_search_codes" says "search": a word for reading.
Description, as the server wrote it Find US medical codes whose official descriptions match a described concept, via full-text search over the bundled index. Every search term must appear — matched first as a token prefix, then as a substring so inflected and compound forms are also found (a "neuropathy" search surfaces "mononeuropathy"/"polyneuropathy" siblings too, not only a standalone "neuropathy" token). An RxNorm concept matches on its drug name alone, never its term type (SBD, IN, …) — narrow by type with `chapter`. Filter by `system` (ICD10CM/ICD10PCS/HCPCS/RXNORM), `billableOnly` to exclude headers/categories and terminated HCPCS codes, and `chapter`. Use when you have a clinical description and need the code — the reverse of medcode_get_code. Results echo the resolved system per row for chaining, rank exact prefix matches ahead of substring-only matches with a deterministic tie-break, and disclose truncation with a `nextCursor`: pass it back as `cursor` to page through the full ranked set.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://medical-codes.caseyjhand.com/mcp: tools/list returned 6 tools to an anonymous client, including medcode_check_code (write), medcode_map_codes (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "medcode_check_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "validate": a word for reading.
- Infomedcode_get_code
The description is 2,940 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ng it, so a single answer to a colliding code is never mistaken for the only one."
The description is 3,007 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ss directions, and a `system` other than RXNORM on the drug and class directions."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:medcode_browse_hierarchyOnly readsinputSchema
- Changed:medcode_check_codeChanges thingsdescriptioninputSchema
- Changed:medcode_get_codeOnly readsdescriptioninputSchema
- Changed:medcode_map_codesChanges thingsinputSchema
- Changed:medcode_search_codesOnly readsinputSchema
Tools4 changed.~4 changedView diff
- Changed:medcode_browse_hierarchyOnly readsdescription
- Changed:medcode_check_codeChanges thingsdescription
- Changed:medcode_get_codeOnly readsdescription
- Changed:medcode_map_codesChanges thingsdescription
Tools3 changed.~3 changedView diff
- Changed:medcode_check_codeChanges thingsdescription
- Changed:medcode_get_codeOnly readsdescription
- Changed:medcode_search_codesOnly readsdescriptioninputSchema
Install
Pinned to version 0.5.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http medical-codes https://medical-codes.caseyjhand.com/mcpclaude mcp add --transport http medical-codes https://medical-codes.caseyjhand.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__medical-codes__medcode_get_code",
"mcp__medical-codes__medcode_search_codes",
"mcp__medical-codes__medcode_browse_hierarchy",
"mcp__medical-codes__medcode_list_systems"
],
"ask": [
"mcp__medical-codes__medcode_check_code",
"mcp__medical-codes__medcode_map_codes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as medical-codes. Review it before you use it.
Capability tags behind 1 rule
- mcp__medical-codes__medcode_browse_hierarchy untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/medical-codes-mcp-server/verify?hash=4b07975f550f32523faa33c647a86b60b02156cdc22cbf16be4ee2f0d877173c" | jq -e '.changed == false'Pinned hash 4b07975f550f, from Nov 16, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cyanheads/medical-codes-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cyanheads/medical-codes-mcp-server)Source: MCP Registry · repository. Synced Nov 16, 2026, 14:18 UTC.
medical-codes-mcp-server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the medical-codes-mcp-server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the medical-codes-mcp-server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the medical-codes-mcp-server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the medical-codes-mcp-server have?
- 6 tools: 2 write, 4 read. medcode_check_code, medcode_map_codes, medcode_get_code, medcode_search_codes, medcode_browse_hierarchy and medcode_list_systems.
Does the medical-codes-mcp-server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the medical-codes-mcp-server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the medical-codes-mcp-server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.