Compatible with every major AI agent and IDE
What is the HHS Open Payments MCP Server?
Connect to the HHS Open Payments database to explore financial transparency in healthcare. This server allows you to query datasets, search for specific physicians or teaching hospitals, and analyze payments made by drug and device companies.
What you can do
- Dataset Discovery — List all available Open Payments datasets and inspect their metadata, including column definitions and update timestamps.
- Physician & Hospital Search — Search for specific healthcare providers or teaching hospitals by name to find their associated records.
- Advanced Querying — Use Socrata Query Language (SoQL) to filter, sort, and limit data for precise financial analysis.
- Data Export — Download specific datasets in CSV, JSON, or XML formats for external processing or reporting.
- Metadata Inspection — Fetch detailed information about specific datasets to understand the underlying data structure.
How it works
- Subscribe to this server
- Enter your HHS/Socrata API Key (optional but recommended for higher rate limits)
- Start auditing healthcare financial data directly from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Researchers & Journalists — Uncover financial ties between the medical industry and healthcare professionals for investigative reporting.
- Compliance Officers — Monitor and verify the accuracy of reported financial transfers within healthcare organizations.
- Healthcare Consumers — Check for potential conflicts of interest or financial relationships of their medical providers.
Built-in capabilities (6)
JSON is recommended for programmatic access. Download a specific Open Payments dataset
Get metadata for a specific Open Payments dataset
List all available Open Payments datasets
Query specific records within a dataset using SoQL
Search for specific teaching hospitals
Search for specific physicians
Why Cursor?
Cursor's Agent mode turns HHS Open Payments into an in-editor superpower. Ask Cursor to generate code using live data from HHS Open Payments and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
HHS Open Payments in Cursor
HHS Open Payments and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect HHS Open Payments to Cursor 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 HHS Open Payments in Cursor
The HHS Open Payments 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 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
HHS Open Payments for Cursor
Every tool call from Cursor to the HHS Open Payments MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
OpenCost (K8s Cost)
6 toolsMonitor and analyze Kubernetes infrastructure costs — query workload allocations, backing assets, and cloud billing directly from your AI agent.

ECB Interest Rates — Monetary Policy Rates & Banking
5 toolsECB key policy rates: the Main Refinancing Operations rate (MRO), Deposit Facility Rate (DFR), Marginal Lending Facility, all three rates combined, and MFI bank lending/deposit rates showing monetary policy transmission across the eurozone.

Geometry Calculator
3 toolsCompute exact Euclidean distances, 2D areas, and 3D volumes completely local. A zero-latency geometry engine for autonomous AI agents.

Jira Cloud
10 toolsManage projects, search issues, and track tasks via Jira Cloud API.
