MCP & the Data API

Connect Vlada to the tools you already use.

Add one secure connection. Sign in once. Ask a healthcare question in plain English, or call a governed tool directly, and get the answer with its sources attached.

$5 of free queries to start · every answer traced to its source · more credit on request

connect · vlada
// add one secure connection
$ claude mcp add --transport http vlada
https://mcp.vladahealth.com/mcp
// Claude opens a sign-in window, then ask
/mcp · sign in or sign up · ask
Claude Code · ChatGPT · Cursor · any MCP client
01
Connect

From connection to your first answer in minutes.

1

Add Vlada

Add one secure MCP connection in the tool where you want to use it.

  • Claude Code
  • ChatGPT
  • Cursor
  • Another MCP client
  • Your own application
2

Sign in

Vlada opens a secure browser sign-in. Your account determines:

  • Which organization you belong to
  • Which healthcare Worlds you can use
  • Which tools are available
  • Which data you may access
3

Ask or build

In an AI client, ask in plain English. In an application, call a tool directly.

Which Connecticut hospitals have the lowest commercial rates for CPT 70553, and how do those compare with Medicare?

Every result includes the answer and the evidence behind it.

02
Set up your client

One connection, your tool of choice.

Pick your client for the exact setup. Only the selected client's instructions appear, so you are never reading four guides at once.

Connect Vlada to Claude Code

  1. 1
    Create your API key at vladahealth.com/account. It is shown once — copy it.
  2. 2
    Copy and run this in your terminal, pasting your key into the header.
    terminal
    $ claude mcp add --transport http vlada https://mcp.vladahealth.com/mcp --header "Authorization: Bearer <your-api-key>"
  3. 3
    Open Claude Code, run /mcp, and confirm Vlada shows connected.
  4. 4
    Ask a first question to confirm your tools.
    Then ask

    Use Vlada. List the healthcare tools available to my organization. Do not call a tool yet.

Claude Code supports remote HTTP MCP servers with a per-server --header. Your key scopes the tools your organization is entitled to.

Claude Code MCP guide
03
Why it is simple

The connection is simple because the hard work is already done.

Vlada has already collected, organized, connected, and governed the public healthcare record. You do not need to rebuild that infrastructure before asking a useful question.

Without Vlada

To answer one healthcare question, a team may need to:

  • 01Find the correct public source
  • 02Download and process enormous files
  • 03Understand a new schema
  • 04Resolve providers, facilities, payers, and codes
  • 05Choose the correct historical release
  • 06Join incompatible datasets
  • 07Apply healthcare payment methodology
  • 08Validate the result
  • 09Preserve the evidence
  • 10Build and maintain the pipeline
With Vlada

The healthcare data work is already done. One connection makes it usable.

  • 1ConnectOne secure MCP or API connection.
  • 2AskA question in plain English, or a direct tool call.
  • 3InspectThe answer and its receipts, together.
04
One connection, two ways to use it

Ask naturally, or call directly.

MCP and the Data API use the same healthcare data, identity system, methodologies, and evidence model.

MCPfor AI tools and agents
Which hospitals in this market have the lowest negotiated prices for outpatient MRI?

The AI can

  • Understand the question
  • Choose the right Vlada capability
  • Call the tool
  • Interpret the structured result
  • Show the answer with its evidence
Data APIfor applications and workflows
Application
Vlada API
structured healthcare result
evidence metadata

Use it for

Product backendsPrice lookupProvider searchScheduled monitoringBatch analysisCustomer-facing apps
05
Your first source-traced answer

The answer, and the evidence behind it.

Ask naturally

What is the commercial benchmark for CPT 70553 in Connecticut, and what evidence supports it?

or call the tool
benchmark_code({ payer: "cigna", code: "70553", state: "CT" })
get back
{
value: { median_rate: 300.21, p90_rate: 953.03, rate_count: 881 },
scope: { payer: "cigna", code: "70553", state: "CT" },
provenance: { source: "idx_rate_lookup", vintage: "2026-05", response_hash: "…" },
methodology: {},
limitations: [ … ]
}

Example structure. Available fields and values depend on the question, your access, and current source coverage.

The receipt
Answer
$300.21 median
Source
Commercial negotiated-rate index
Vintage
May 2026
Method
Median of comparable rates in the selected segment
Trust state
Validated
Limitations
Returned with the result
06
What you can ask

Plain-English questions, typed and sourced answers.

Ask in natural language; the agent picks the right capability and returns a structured answer with its evidence.

Prices
  • What does an insurer pay for a service?
  • What does a hospital post?
  • How does a price compare with Medicare?
Providers
  • Who is this provider?
  • Where do they practice?
  • Which facilities belong to this health system?
Medicare & health plans
  • What would Medicare pay?
  • Which plans are gaining enrollment?
  • How do benefits or Stars compare?
Drugs
  • What public prices and payment references exist?
  • How does access vary by plan?
Employer claims
  • Where does paid spending exceed compatible public references?
Custom analysis
  • Run a bounded query across the healthcare data included in my access.
View all tools and schemas →
07
The connected record

Eight healthcare Worlds through one connection.

Price Transparency
Hospital-posted and payer-negotiated prices
Medicare FFS
Payments, utilization, and public benchmarks
Medicare Advantage & Part D
Enrollment, benefits, Stars, and formularies
ACA Marketplace
Plans, premiums, issuers, and continuity
Providers & Facilities
Identity, ownership, affiliations, and markets
Quality & Outcomes
Provider, facility, and plan performance
Drugs, Biologics & Devices
Identity, price, payment, access, safety, and supply
Medicaid
State rates, managed care, enrollment, and drugs

Identity · Codes · Geography · Policy · Time · Provenance

Explore the Worlds →
08
Coverage and limitations

Live coverage, and the limits stated plainly.

These are current, measured counts, not marketing rounding. Methodologies are kept separate, so a fee schedule is never blended with a percentage of charges, and each answer returns its own limitations.

5,167
hospitals with posted prices
53 states + territories
8.96B
insurer negotiated rates
42 payers, 56 states
9.4M
provider identities (NPIs)
Type 1 + Type 2, resolved
3.38B
payer-specific hospital rates
line-of-business classified

Coverage as of 2026-07-14.

09
Governed by default

Built for production, not just a demo.

The same secure substrate that runs the Employer Agent. Access is authenticated, scoped, bounded, and auditable.

OAuth sign-in

Every connection authenticates through a secure browser sign-in. No shared keys pasted into config files.

Organization access

Your account determines the Worlds, tools, and data you are permitted to use. Access is scoped, not global.

Bounded execution

Custom queries are read-only and resource-bounded, with a separate async lane for heavy pulls. No write path, no runaway jobs.

Audit trail

Every answer carries a content hash and resolves to the public source file behind it, so requests and results are replayable and reviewable.

Build on it

One connection. The public healthcare record, usable.

Create your free account to connect over MCP, or talk to us about the Data API and production integrations.

Prefer a terminal? Copy the connect command instead — either door lands in the same account.