4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Open Payments (CMS Physician Data) MCP Server

Bring Transparency
to Claude Desktop

Learn how to connect Open Payments (CMS Physician Data) to Claude Desktop and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get DatasetList DatasetsQuery DatasetSearch PhysiciansSearch Teaching Hospitals

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Open Payments (CMS Physician Data)

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

  1. Subscribe to this server
  2. Enter your Open Payments API Key (App Token)
  3. 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_dataset

Get detailed metadata for a specific dataset

list_datasets

List all available datasets in the Open Payments system

query_dataset

Search records within a specific dataset

search_physicians

Search for specific physicians

search_teaching_hospitals

Search for specific teaching hospitals

Why Claude Desktop?

Claude Desktop is the definitive way to connect Open Payments (CMS Physician Data) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 5 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Open Payments (CMS Physician Data) in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

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 Claude Desktop 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Open Payments (CMS Physician Data) in Claude Desktop

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 Claude Desktop 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.

Open Payments (CMS Physician Data)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Open Payments (CMS Physician Data) for Claude Desktop

Every tool call from Claude Desktop 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.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →