Bring Transparency
to LlamaIndex
Learn how to connect Open Payments (CMS Physician Data) to LlamaIndex and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Open Payments (CMS Physician Data) MCP Server?
The Open Payments MCP server provides direct access to the Centers for Medicare & Medicaid Services (CMS) database. This transparency program publishes data about financial relationships between reporting entities (like drug and medical device companies) and covered recipients (physicians and teaching hospitals).
What you can do
- Physician Search — Locate specific healthcare providers using NPI, name, or specialty via
search_physicians. - Hospital Lookup — Find teaching hospitals by name or address using
search_teaching_hospitals. - Dataset Exploration — List all available reporting cycles and payment categories with
list_datasets. - Advanced Querying — Perform deep dives into payment records using SQL-like filters ($where, $select) via
query_dataset. - Metadata Retrieval — Get technical details and column definitions for specific datasets using
get_dataset.
How it works
- Subscribe to this server
- Enter your Open Payments API Key (App Token)
- Start auditing healthcare financial data from Claude, Cursor, or any MCP client
Who is this for?
- Compliance Officers — verify financial disclosures and industry ties for medical staff.
- Journalists & Researchers — analyze trends in industry spending and identify potential conflicts of interest.
- Healthcare Analysts — aggregate payment data to understand market influence and provider relationships.
Built-in capabilities (5)
Get detailed metadata for a specific dataset
List all available datasets in the Open Payments system
Search records within a specific dataset
Search for specific physicians
Search for specific teaching hospitals
Why LlamaIndex?
LlamaIndex agents combine Open Payments (CMS Physician Data) tool responses with indexed documents for comprehensive, grounded answers. Connect 5 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Open Payments (CMS Physician Data) tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Open Payments (CMS Physician Data) tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Open Payments (CMS Physician Data), a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Open Payments (CMS Physician Data) tools were called, what data was returned, and how it influenced the final answer
Open Payments (CMS Physician Data) in LlamaIndex
Open Payments (CMS Physician Data) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Open Payments (CMS Physician Data) to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Open Payments (CMS Physician Data) in LlamaIndex
The Open Payments (CMS Physician Data) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 5 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Open Payments (CMS Physician Data) for LlamaIndex
Every tool call from LlamaIndex to the Open Payments (CMS Physician Data) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I find payments for a specific doctor by their NPI?
Use the search_physicians tool and provide the npi parameter. Your agent will return matching physician records which you can then use to query specific payment datasets.
Can I filter results to only show payments above a certain dollar amount?
Yes, use the query_dataset tool with the where parameter. For example, you can set where to total_amount_of_payment_usdollars > 1000 to filter for high-value transactions.
How do I see what columns are available in a specific dataset?
Use the get_dataset tool with the specific dataset_id. It will return detailed metadata, including column definitions, data types, and update frequency for that specific reporting cycle.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Open Payments (CMS Physician Data) tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
PagBank PagSeguro
9 toolsCreate Pix, Boleto, and Card payment links, and manage transactions via PagBank API.
Funil de Vendas
12 toolsManage CRM opportunities, sales funnels, and activities via Funil de Vendas directly from your AI agent.
IPGeolocation (IP Intelligence & Time)
3 toolsResolve IP addresses via IPGeolocation — get precise location, timezone details, and local astronomy data.
HubSpot CMS Hub
9 toolsManage blog posts, site pages, landing pages, authors, tags, and domains through natural conversation.