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

Bring Transparency
to Google ADK

Learn how to connect Open Payments (CMS Physician Data) to Google ADK 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 Google ADK?

Google ADK natively supports Open Payments (CMS Physician Data) as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 5 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

  • Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

  • Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Open Payments (CMS Physician Data)

  • Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

  • Seamless integration with Google Cloud services means you can combine Open Payments (CMS Physician Data) tools with BigQuery, Vertex AI, and Cloud Functions

G
See it in action

Open Payments (CMS Physician Data) in Google ADK

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 Google ADK 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 Google ADK

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 Google ADK 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 Google ADK

Every tool call from Google ADK 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 Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

05

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

06

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

07

McpToolset not found

Update: pip install --upgrade google-adk

Explore More MCP Servers

View all →