You can run a Verity MCP Server locally to give AI agents access to Medicare coverage policies, prior authorization information, and medical code lookups. This server model lets you perform code lookups, policy searches, and jurisdiction comparisons through simple MCP calls, enabling automated decision support in your healthcare tooling.

How to use

You interact with the Verity MCP Server by connecting your MCP client to the local or remote server and issuing tool calls that fetch policy data, codes, and prior authorization guidance. Core capabilities include looking up CPT/HCPCS/ICD-10/NDC codes, searching Medicare LCDs and NCDs, checking whether a procedure requires prior authorization, and comparing coverage across MAC jurisdictions. Use these patterns to build workflows that answer questions like what codes are covered for a procedure, whether prior auth is required in a given state, or how coverage differs between jurisdictions.

How to install

{
  "mcpServers": {
    "verity": {
      "type": "stdio",
      "command": "node",
      "args": ["C:\\Users\\tyler\\OneDrive\\Desktop\\verity_mcp\\build\\index.js"],
      "env": {
        "VERITY_API_KEY": "vrt_live_YOUR_API_KEY_HERE"
      }
    }
  }
}

Replace YOUR_API_KEY_HERE with your actual Verity API key and ensure Node.js is installed on your system.

## Configuration and environment

Environment variables you rely on are defined to authenticate and configure the MCP server. The key you must provide is VERITY\_API\_KEY. You may also override the API base URL using VERITY\_API\_BASE if you operate a non-default endpoint.

{ "mcpServers": { "verity": { "type": "stdio", "command": "node", "args": ["C:\Users\tyler\OneDrive\Desktop\verity_mcp\build\index.js"], "env": { "VERITY_API_KEY": "vrt_live_YOUR_API_KEY_HERE", "VERITY_API_BASE": "https://verity.backworkai.com/api/v1" } } } }

## Environment variables

- VERITY\_API\_KEY: Your Verity API key. This starts with vrt\_live\_ or vrt\_test\_. (Required)
- VERITY\_API\_BASE: Optional API base URL. Defaults to https://verity.backworkai.com/api/v1 if not provided.

## Development

Watch mode for development

npm run dev

Build

npm run build

Run the server directly

npm start

## Troubleshooting

If you see a 401 API error, verify that your API key is correct and active. If you encounter missing API key messages, ensure VERITY\_API\_KEY is set in your environment or client configuration. If you hit rate limits, wait briefly and retry or consider upgrading your plan.

## Examples of common workflows

Examples include looking up a code to understand its coverage, checking whether a CPT code requires prior authorization in a particular state, and comparing policy coverage for a device like a continuous glucose monitor across California and Texas.

## Available tools

### lookup\_code

Retrieve medical codes (CPT, HCPCS, ICD-10, NDC) and their basic descriptions and related context.

### search\_policies

Search Medicare policies, including LCDs, NCDs, and Articles, to discover coverage rules.

### get\_policy

Fetch detailed policy information by ID, with optional includes for related data like criteria and codes.

### compare\_policies

Compare coverage across different MAC jurisdictions for a set of codes.

### get\_policy\_changes

Track updates to policies over time, optionally filtered by policy or since a date.

### search\_criteria

Search blocks of coverage criteria to find relevant indications, limitations, and requirements.

### list\_jurisdictions

Retrieve MAC jurisdiction information and covered states.

### check\_prior\_auth

Determine whether specified procedures require prior authorization, optionally by state or diagnosis codes.