HHS Open Payments MCP for AI. Audit financial ties in healthcare data.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
HHS Open Payments provides direct access to the HHS Open Payments database for financial transparency in healthcare. It lets users search records for specific physicians or teaching hospitals and analyze payment data made by drug and device companies.
You can list available datasets, download raw data structures (CSV, JSON), run precise queries using SoQL, and inspect metadata about the underlying public health records.
What your AI can do
Download dataset
Downloads a specified Open Payments dataset file in CSV, JSON, or XML format.
Get dataset
Retrieves the metadata and structure details for a specific Open Payments dataset.
List datasets
Lists all available datasets within the Open Payments database.
List and inspect the metadata of all Open Payments datasets.
Fetch detailed information about a specific dataset to understand its column names and format.
Run complex queries on a specified dataset, filtering results using SoQL syntax.
Find specific physicians within the database by name.
Locate records associated with specific teaching hospitals.
Download a specified Open Payments dataset in CSV, JSON, or XML format.
Ask an AI about this
Waiting for input…
HHS Open Payments MCP: 6 Tools
Use these tools to list datasets, query specific records using filters, or download raw payment data from the HHS Open Payments database.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using HHS Open Payments on VinkiusDownload Dataset
Downloads a specified Open Payments dataset file in CSV, JSON, or XML format.
Get Dataset
Retrieves the metadata and structure details for a specific Open Payments dataset.
List Datasets
Lists all available datasets within the Open Payments database.
Query Dataset
Runs targeted queries against a dataset, allowing filtering and sorting using SoQL.
Search Hospitals
Searches the database to find records associated with specific teaching hospitals.
Search Physicians
Finds and retrieves records for specific medical providers by name.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with HHS Open Payments, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by HHS Open Payments. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding financial relationships feels like sifting through government archives.
Right now, checking a single payment record means navigating multiple CMS portals. You have to search for the dataset ID, check its metadata to see if it contains location data, and then manually write complex filters just to narrow down payments by state or year. It's a lot of clicking through tabs and copy-pasting IDs.
With this MCP, you skip the portal mess entirely. You tell your agent exactly what you want—for example, 'Show me all payments over $10k in Florida.' The system handles the dataset discovery, the metadata check, and the filtering logic automatically. You get a clean, structured list of results without touching a government website.
HHS Open Payments: Structured Data Access
You don't have to manually track which dataset holds which type of payment or spend time debugging API calls for schema mismatches. The MCP groups all these functions, from `list_datasets` to the advanced `query_dataset`, into a single access point.
What changes is that you talk directly to your agent in plain English. You don't need to be an expert in Socrata Query Language or dataset IDs; you just ask for the answer.
What your AI can actually do with this
This MCP connects your agent to the HHS Open Payments database, letting you audit financial relationships across the healthcare industry. Instead of browsing complex government portals, you can ask for specific details—like payment amounts or connections between a specialist and a major hospital—and get structured results back immediately. You'll find tools to list all available datasets and download them in CSV, JSON, or XML formats for your reports.
Need to narrow down the scope? You can search specifically for physicians or teaching hospitals by name. For complex analysis, you use advanced querying features that filter records precisely using SoQL. When you connect this MCP via Vinkius, it acts as a single gateway, giving any compatible client access to all these public record tools without needing separate API keys for every function.
019e38a8-3ce6-7120-a0b4-0767adf01998 Here's how it actually works
The bottom line is that you guide your agent through this sequence: discover what's available, check its structure, and then ask it to find exactly what you need.
First, request the list of all available datasets using list_datasets to determine which data pool you need.
Next, either use get_dataset to check the metadata and schema of that dataset or run a focused search for specific entities like hospitals via search_hospitals.
Finally, execute your analysis by running a query using query_dataset, specifying filters (SoQL), or downloading the raw data with download_dataset.
Who is this actually for?
Researchers and compliance officers who have to verify financial ties between medical companies and healthcare professionals. You are the person who needs public record data, but doesn't want to spend hours building complex SQL queries just to find a conflict of interest.
Find financial ties between pharmaceutical companies and local doctors using search_physicians and then checking the associated payments via query_dataset.
Monitor whether reported financial transfers match internal compliance rules by listing all datasets with list_datasets and running targeted queries.
Gather structured payment data on specific hospital types using search_hospitals, then downloading the entire dataset via download_dataset for modeling.
What Changes When You Connect
You bypass manual portal navigation. Instead of clicking through multiple government tabs, you ask your agent to list_datasets and immediately see every available data pool for analysis.
Complex data filtering becomes simple. Forget writing complicated SQL joins; use query_dataset to filter records using SoQL right from your prompt, giving you immediate answers on payment amounts or locations.
Get the raw files when needed. If your team requires the full dataset—say, a CSV of all 2023 payments—you can reliably download it using download_dataset for external reporting.
Focus your search immediately. Need to verify an entity? Use search_physicians or search_hospitals to narrow down millions of records instantly and get the core record details you need, cutting research time from hours to minutes.
Understand the data structure first. Before querying, use get_dataset to inspect the metadata. This ensures your agent knows exactly which columns exist so you don't run a query that fails because of bad syntax.
See it in action
Verifying corporate influence on local care
A journalist needs to know if a major drug company paid multiple providers in one county. They use list_datasets to find the right payments pool, then run query_dataset, filtering by the specific county and payment year. The agent returns a clean list of all implicated doctors.
Compliance review for mergers
A compliance officer must verify that newly acquired hospitals follow reporting standards. They use search_hospitals to find records tied to the new facility, and then get_dataset to check the required data fields before exporting everything via download_dataset.
Investigating a malpractice pattern
A researcher suspects a specific doctor is involved in multiple high-value payments. They use search_physicians to isolate that individual, and then they run a targeted query using query_dataset against the payment dataset for that person's name.
Building a custom data dashboard
A data scientist needs all historical records on payments. They use list_datasets to confirm the correct pool, and then run multiple targeted queries using query_dataset across different time ranges to pull structured results for their model.
The honest tradeoffs
Treating data like a simple search engine
A user asks the agent, 'Show me all payments from Florida.' This is too broad and doesn't specify how to filter or which dataset to use.
You must start by confirming the right data pool using list_datasets. Then you run a precise query with query_dataset, providing both the dataset ID and the necessary filters (e.g., WHERE state = 'FL').
Running queries without knowing schema
A user tries to write a complex query using an outdated column name, causing the agent to fail with an unknown field error.
Before querying, always run get_dataset on the target dataset. This shows you the precise metadata and current column definitions needed for your SoQL statement.
Downloading data without purpose
A user downloads every dataset available via download_dataset without knowing which one contains the most recent or relevant information.
First, use list_datasets to narrow down your options. Then, decide if you need the raw file (download_dataset) or just a few filtered results (use query_dataset).
When It Fits, When It Doesn't
Use this MCP when your goal is financial transparency and public record auditing in healthcare. If you're trying to figure out who paid whom, or how much was exchanged, this is the tool. It’s built around structured data retrieval and entity searching (physicians/hospitals). Don't use it if you need to analyze unstructured text, like transcribing clinical notes, or if your goal involves real-time streaming metrics that require constant updates outside of batch processing. For complex joins across multiple different sources not available in the Open Payments schema, this MCP won't help—you’d need a dedicated data warehouse connection instead. Always verify which dataset you are querying using get_dataset first; it prevents wasted calls and incorrect results.
Questions you might have
How do I find out what data fields are available using HHS Open Payments? +
You use get_dataset to retrieve metadata for a specific pool. This function shows you every column name, its definition, and whether it's a text or numeric field before you write any query.
Can I search for both doctors and hospitals with HHS Open Payments? +
Yes. You use search_physicians to find specific medical providers and search_hospitals to locate teaching facilities, pulling up records for both types of entities.
Is the data from HHS Open Payments real-time? +
The MCP accesses historical datasets. Use list_datasets first to check the update timestamps and determine if a dataset contains the most recent payment years you need.
Do I need an API key for querying data with HHS Open Payments? +
While not mandatory, providing an API Key is recommended. It helps increase your rate limit capacity when running repeated or high-volume queries using query_dataset.
What should I do if I run into rate limits when using `query_dataset`? +
You must implement exponential backoff and retry logic. If your AI client hits a limit, the system will return a specific error code; wait several seconds before re-running the query until it succeeds.
What are the supported file formats when I use `download_dataset`? +
You can request the data in CSV, JSON, or XML. For programmatic processing and reliability within your agent, JSON remains the recommended format for all exports.
How do I write complex filters or combine results using `query_dataset`? +
You use standard Socrata Query Language (SoQL) syntax. You can filter by multiple fields and apply logical operators like AND, OR, and NOT to narrow down your search criteria.
After calling `list_datasets`, how do I figure out which dataset is right for my specific research needs? +
You should use the get_dataset tool next. This retrieves detailed metadata, showing you exactly what columns and payment types each available Open Payments dataset contains.
Can I search for a specific doctor by name to see their financial records? +
Yes! Use the search_physicians tool with the doctor's name. The agent will return matching profiles and their associated payment data from the Open Payments database.
How do I filter data for a specific state or payment amount? +
You can use the query_dataset tool and provide a SoQL filter in the where parameter (e.g., recipient_state = 'NY' or total_amount_of_payment_usdollars > 1000).
What formats can I use to download the datasets? +
The download_dataset tool supports 'csv', 'json', and 'xml' formats. JSON is generally recommended for programmatic access and AI analysis.
We've already built the connector for HHS Open Payments. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.