Medicare Pricing logo

Medicare Pricing

Queries CMS Medicare fee schedules, lab rates, DMEPOS pricing, NCCI edits, OPPS rates, and FQHC payment data.

Install Medicare Pricing

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "medicare-pricing": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-medicare-pricing"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Medicare Pricing MCP server exposes CMS payment and billing-edit data for physician services, laboratory tests, DMEPOS, hospital outpatient procedures, FQHC visits, and NCCI rules. Its tools resolve geographic locality, state, schedule year, quarter, release, modifiers, and edit vintages so responses include the context behind each amount. Use it to benchmark reimbursement, identify applicable billing codes, check unit limits or code-pair edits, and investigate branded laboratory tests. The integration is unofficial, uses CMS data files and selected NCBI Genetic Testing Registry data, and requires no API key or account.

Use cases

  • Benchmark physician reimbursement by CPT code and Medicare locality
  • Look up CLFS payment for a laboratory test or branded assay
  • Compare rural and non-rural DMEPOS rates by state
  • Check NCCI unit limits and code-pair bundling rules
  • Estimate FQHC base payment or hospital outpatient reimbursement

Key features

  • Locality-adjusted physician fee-schedule payments
  • National laboratory and branded-test rate lookup
  • State-based DMEPOS pricing with rural and non-rural amounts
  • OPPS and FQHC payment-rate queries
  • NCCI MUE and procedure-to-procedure edit checks
  • Schedule vintage and dataset coverage reporting

Tools9

What Medicare Pricing lets your agent do. Expand a tool for its parameters.

Verified live~2.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 45d

What it can do

From the 9 tools this server returned when we ran it.

Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age29 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-medicare-pricing (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.7kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed9Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Medicare Pricing works

What Medicare Pricing does

Medicare Pricing answers what Medicare pays and how CMS applies billing edits. It covers physician fee-schedule payments, national laboratory rates, DMEPOS amounts, hospital outpatient prospective payment rates, FQHC per-visit base rates, NCCI medically unlikely edits, and procedure-to-procedure code relationships. A separate lookup resolves branded molecular and genomic tests to billing codes, performing laboratories, CLFS rates, and related MolDX coverage documents.

The returned context is part of the result, not an afterthought. Physician payments identify the fee-schedule year, resolved Medicare locality, RVU components, facility and non-facility amounts, global period, and payment status. Laboratory results identify the schedule year and quarter. DMEPOS results distinguish rural from non-rural state pricing and report the applicable year, release, and modifier. NCCI responses include their quarterly or loaded edit vintage.

How it works

The integration reads CMS-published downloadable files rather than calling a CMS pricing API. Physician pricing uses the Physician Fee Schedule relative value files; laboratory pricing uses the Clinical Laboratory Fee Schedule; DMEPOS uses its quarterly fee schedule; and hospital outpatient results use OPPS Addendum B. NCCI tools use CMS edit data, while FQHC PPS values come from a maintained annual table based on CMS transmittals.

Branded test lookup checks CMS’s ADLT list first, then a maintained table for selected non-ADLT branded tests, and finally live NCBI Genetic Testing Registry records where laboratories have registered a code. It also queries keyless CMS Coverage API reports for active LCDs and billing articles associated with the test category.

Tools and capabilities

  • medicare_physician_payment calculates locality-adjusted physician payments and returns work, practice-expense, and malpractice RVUs.
  • medicare_lab_rate returns the national CLFS amount for a laboratory HCPCS or CPT code.
  • medicare_lab_test_lookup maps supported branded tests, laboratories, or codes to billing and coverage information.
  • medicare_dmepos_rate prices HCPCS Level II equipment, supplies, prosthetics, and orthotics by state and rural status.
  • medicare_opps_rate returns OPPS status indicators, APC data, relative weight, national payment, copay, and pass-through details.
  • medicare_code_units_limit returns NCCI MUE limits, adjudication indicators, and rationales for practitioner, outpatient hospital, or DME settings.
  • check_code_pair and explain_ncci_edit inspect PTP edits and modifier indicators.
  • medicare_fqhc_pps_rate returns the national FQHC PPS base rate by year, before the local GAF adjustment.
  • medicare_pricing_coverage reports loaded schedule vintages, dataset sizes, localities, and PTP coverage information.

Setup and configuration

Authentication is not required: the server uses no API key and no account. Queries can reference HCPCS or CPT codes, branded test names, laboratories, states, localities, years, quarters, releases, settings, and applicable DMEPOS modifiers. For FQHC requests, omit the year to retrieve the newest loaded value and historical rows, or provide a year for a single result.

Limitations and notes

Payment figures are schedule amounts, not guarantees of claim payment. Physician rates vary by Medicare locality, while laboratory rates are national and DMEPOS rates are state-based. The FQHC tool reports only the national base rate; it does not calculate the FQHC-specific Geographic Adjustment Factor.

Branded-test matching depends on the maintained CMS and MAAA tables plus live NCBI GTR registrations. An unresolved brand returns a not-found result with the sources checked. CMS coverage documents may include active LCDs and billing articles, while retired documents require an explicit request.

Schedule data changes by year or quarter, and NCCI results are tied to a stated edit vintage. Check medicare_pricing_coverage before relying on a rate for a particular reporting period. The project is an independent, unofficial integration and is not affiliated with CMS or another upstream provider.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Medicare Pricing

Medicare Pricing is an MCP server that connects AI agents to CMS Medicare pricing data and selected NCBI genetic-test records. Its main tools query physician, laboratory, DMEPOS, OPPS, and FQHC rates, resolve branded lab tests, and check NCCI unit and procedure-pair edits. It requires no API key or account.

No, Medicare Pricing requires neither an API key nor an account. The server uses downloadable CMS data files and selected keyless coverage reports, with NCBI Genetic Testing Registry data used for part of branded laboratory-test resolution.

It adjusts physician fee-schedule values using the Medicare locality rather than only the state. Results include the resolved locality and year, work, practice-expense, and malpractice RVUs, plus facility and non-facility payment amounts.

Yes, `check_code_pair` evaluates the CMS NCCI procedure-to-procedure edit for two HCPCS or CPT codes. It returns the modifier indicator and loaded setting or vintage; `explain_ncci_edit` lists recorded edit relationships for one code.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMedicare Pricing AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/medicare-pricing?style=directory)](https://allmcps.com/mcp/medicare-pricing)
HTML Embed
<a href="https://allmcps.com/mcp/medicare-pricing"><img src="https://allmcps.com/api/badge/medicare-pricing?style=directory" alt="Medicare Pricing on AllMCPs" /></a>