✓Model Context Protocol server

Verzi Health Warrant: Medicare warrants as agent tools.

Ask an AI agent "is this DME claim supported?" and get a cited, as-of answer with a receipt. The same warranted record behind the API and the SDK, exposed as MCP tools your agent calls directly.

Get a key Connect an agent

Endpoint https://mcp.verzi.health/mcp/ · Streamable HTTP · auth X-API-Key

What it is

Three doors to one room. MCP is the agent door.

The /v1 API is the single source of truth. The SDK and the MCP server are derived from it, never hand-maintained in parallel. An MCP call is an API call through a different door. The answer is the same warrant: the fact, its source, the version in force, and a hash you can replay. Built for RCM and medical-coding engineers and AI-agent builders.

API

Any integrator, over HTTP

The source of truth. Every endpoint takes as_of; every envelope returns meta.as_of. →

SDK

A developer writing code

Deterministic, typed access, generated from the same /v1 contract. For billing and RCM vendors. →

MCPyou are here

An agent, tool-calling

Claude, Cursor, or a vendor's AI calls the warrant as a tool and reads the receipt.

The warrant

One claim line, four blocks, each with its own receipt.

For one HCPCS code, provider, payer, and date of service, the warrant tool returns one block per question. Each block carries its own fact and its own receipt: the version id, the source file id, and the sha256 you can replay. When a source does not cover the line, the block returns an honest gap, not a guess. There is no cross-warrant boolean, the chart is the customer's layer.

W0Provider standing

Was the supplier, and the ordering physician, allowed to bill that day? Enrollment, PECOS, NPI, state license, OIG exclusion, accreditation.

receipt version_id · file_id · sha256

W1Fee schedule

What did Medicare allow for this item, this ZIP, that quarter? The DMEPOS fee cell, resolved by rurality or competitive-bidding area.

receipt version_id · file_id · sha256

W2Coding edits

Do published NCCI edits block or limit this line? The MUE unit cap and the PTP pair edit, as of the date of service.

receipt version_id · file_id · sha256

W3Documentation

What documentation did the rule in force that day require? The requirement set served from the LCD and the policy article.

receipt version_id · file_id · sha256

Codes and amounts only. The warrant serves HCPCS codes and dollar amounts, never a CPT descriptor. Medicare DME is live; the rest of Medicare and Medicaid follow in Q4 2026, commercial in Q1 2027.

Tools

Five tools. Keyless, free, and paid.

A keyless tool needs no key. A free tool needs a key. A paid tool needs a key and the warrant entitlement, and it is hidden from an unentitled agent's tool list.

server_info()

Server metadata: name, version, and the tool surface the agent can see.

keyless

list_data_sources()

Every external dataset Verzi ingests, with license, update cadence, accuracy classification, and last-loaded state. The provenance catalog behind every claim.

keyless

get_provider(npi)

Full provider dossier by 10-digit NPI: NPPES identity, Open Payments, Physician Utilization, Part D prescribing, OIG exclusion status, and the per-fact attribution.

key · free tier

warrant(hcpcs, as_of, npi, …)

The warrant join for one code, provider, and date of service. One block per warrant (standing, fee, edits, documentation), each with its fact and receipt or an honest gap.

key · paid

warrant_changes(hcpcs, from_dos, to_dos, …)

Did the policy move since a claim's date of service? Diffs the fee, the edits, and the documentation set between two dates. The any_change headline an appeal starts from.

key · paid

Connect

Add the server to your agent.

The server speaks Streamable HTTP at https://mcp.verzi.health/mcp/. Authenticate with your Verzi API key in the X-API-Key header. Keyless tools answer without a key; the free and paid tools read the key.

Claude Code

# add the remote server with your key
claude mcp add --transport http verzi-health \
  https://mcp.verzi.health/mcp/ \
  --header "X-API-Key: vh_live_…"

Cursor · Claude Desktop · mcp.json

{
  "mcpServers": {
    "verzi-health": {
      "url": "https://mcp.verzi.health/mcp/",
      "headers": { "X-API-Key": "vh_live_…" }
    }
  }
}

Then ask in plain language. "Is E0601 supported for this NPI on 2024-01-15 in UT?" The agent calls warrant, and returns the four blocks with their receipts. Full tool and parameter reference lives in the docs.

Pricing

Free current-state. Paid warrant.

The free surface previews the paid answer. The warrant, the as-of history, and the replayable receipt are the paid product.

Free

Current-state tools

Explore the data and the provenance with no key, or a free-tier key.

server_info and list_data_sources · no key
get_provider: the full provider dossier · free-tier key
The source catalog, license, cadence, and accuracy class

Paid

The warrant

The cited, as-of answer with a receipt you can replay against the source bytes.

warrant: four blocks, each with its receipt
warrant_changes: did policy move since the date of service
The as-of version in force, and the sha256 to replay

Give your agent the warranted record.

Get a key, connect the server, and ask your first claim question in minutes.

Get a key Read the docs

Rules data, not PHI. Nothing Verzi serves contains patient information.