validar-codigo-medico

io.github.encodiPublished by GitHub account encodiv1.0.1Updated Oct 25, 2026

Validates ICD-10-CM against the real FY2026 catalog (NCHS/CDC) and CPT by structure/category.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

A remote MCP server that lets an assistant validate ICD-10-CM codes against the official FY2026 catalog and check CPT code structure.

What you can do
Validate medical codes: check ICD-10-CM codes against the bundled FY2026 NCHS/CDC billable catalog and return the official short description, or check CPT codes for valid structure and category (I, II, III) and estimate the area by numeric range. Each call is stateless, with no database or persistent state between calls.
When to use it
Useful when an assistant needs to confirm that a diagnosis or procedure code is well formed or exists in the official ICD-10-CM catalog, for example while drafting or reviewing clinical or billing text. It is not a substitute for a certified professional coder.
Requirements
A remote endpoint over streamable HTTP; no local runtime, account or API key is declared. Each call is billed, so the client must be able to complete an x402 payment in USDC on Base mainnet and retry.
Before you install
Charges real money per call: $0.02 USDC on Base mainnet, paid inside the MCP request rather than by header. CPT results cover format only, with no per-code descriptions, because the CPT catalog is AMA-licensed. Output is structural or catalog validation, not medical or billing advice.

Installation

In SourceWeft

  1. Open validar-codigo-medico in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.encodi%2Fvalidar-codigo-medico/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "validar-codigo-medico": {
      "type": "http",
      "url": "https://validar-codigo-medico.encodari.workers.dev/mcp"
    }
  }
}

README

validar-codigo-medico

[validar-codigo-medico MCP server]

Remote MCP server (Cloudflare Workers) with one tool that validates medical codes against real data:

  • validate_medical_code — system: "icd10" does a real lookup against the official billable ICD-10-CM code catalog (FY2026, NCHS/CDC, public domain as a work of the U.S. government) and returns the official short description. system: "cpt" validates the real structure of a CPT code (Category I: 5 digits; Category II: 4 digits + F; Category III: 4 digits + T) and estimates its area by public numeric range — it doesn't include per-code descriptions, because the CPT catalog is owned by the AMA and requires a paid license (it can't be redistributed).

No database, no persistent state between calls: each call builds a fresh McpServer (see createServer() in src/index.ts). The ICD-10-CM catalog (~6MB, 74,719 codes) is bundled into the Worker itself as static data (src/tools/data/icd10cm.ts) and parsed once per isolate into an in-memory Map — see src/tools/codigoMedico.ts.

Why CPT has no descriptions

The CPT (Current Procedural Terminology) description catalog is owned by the American Medical Association and requires a paid license to redistribute its content — unlike ICD-10-CM, which is a work of the U.S. government and therefore public domain. That's why this tool validates a CPT code's real format (regex + numeric range, publicly available information about the code's structure) but doesn't offer the procedure's description: that requires an AMA-licensed codebook.

Billing (x402)

Charges per call via x402 — real USDC payment on Base mainnet, against the Coinbase Developer Platform (CDP) facilitator. The payment travels inside the MCP JSON-RPC itself (_meta), not as an HTTP header; see src/payments.ts.

ToolPrice
validate_medical_code$0.02 USDC

An unpaid tools/call returns isError: true with the accepts (network, amount, payTo) the client needs to pay and retry — not an unexplained exception.

Structure

src/  index.ts             # registers the tool in the McpServer and exposes the MCP HTTP handler  payments.ts          # x402 billing on Base mainnet via the CDP facilitator  tools/    codigoMedico.ts       # pure logic for validate_medical_code (testable without Workers)    codigoMedico.test.ts    data/      icd10cm.ts          # bundled FY2026 ICD-10-CM catalog (generated, do not edit by hand)scripts/  dev-node.ts           # dev server that runs the handler in plain Node, no wrangler  gen-icd10-data.mjs    # regenerates tools/data/icd10cm.ts from a new CMS/NCHS order file

Updating the ICD-10-CM catalog

When NCHS publishes a new version (new fiscal year or addenda):

  1. Download the "Code Descriptions" zip from https://ftp.cdc.gov/pub/health_statistics/nchs/publications/ICD10CM/<YEAR>/.
  2. Unzip it and locate icd10cm-codes-<YEAR>.txt.
  3. node scripts/gen-icd10-data.mjs <path-to-txt> src/tools/data/icd10cm.ts.

Running it locally

⚠️ Note on wrangler dev: the real Cloudflare Workers runtime (workerd) requires macOS 13.5+. If your Mac has an older version, wrangler dev (and npm run dev) will fail. This project includes a plain-Node shim that runs the exact same fetch() handler without needing workerd.

1. Install dependencies

bash
npm install

2. Run the unit tests

bash
npm test

3a. If your wrangler dev works (macOS 13.5+, Linux, Windows)

bash
npm run dev

3b. If wrangler dev fails because of the macOS version

bash
npm run dev:node

Starts at http://localhost:8787/mcp, reading CDP credentials from ~/.mcp-tools-factory-credentials.env (shared across all tools in this factory).

4. Test with curl

bash
# 1) initializecurl -s -X POST http://localhost:8787/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl-test","version":"0.0.1"}}}'
# 2) tools/listcurl -s -X POST http://localhost:8787/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'
# 3) tools/call — validate_medical_code (ICD-10-CM)curl -s -X POST http://localhost:8787/mcp \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"validate_medical_code","arguments":{"system":"icd10","codes":["A00.0","Z21","does-not-exist"]}}}'

Responses come as Server-Sent Events (event: message + data: {...}); the data: line is the usual JSON-RPC response.

Deploy and listings

Deployed at https://validar-codigo-medico.encodari.workers.dev/mcp (Cloudflare Workers). Published on the official MCP registry, Smithery, mcp.so, and with an open PR to awesome-mcp-servers.

What it doesn't do (yet)

  • Doesn't include per-code CPT descriptions (see "Why CPT has no descriptions" above).
  • Charges on Base mainnet with real money. To switch back to testnet (Base Sepolia, eip155:84532) during development, change NETWORK in src/payments.ts.
  • No database or persistent state between calls (beyond the billing config and the ICD-10-CM catalog Map, cached in memory per isolate).
  • Not medical or billing advice: this is a structural/catalog validation, not a substitute for a certified professional coder.

Source: README.md at commit 6a10b7b

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts