Bring Transparency
to Cursor
Learn how to connect Open Payments (CMS Physician Data) to Cursor 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 Cursor?
Cursor's Agent mode turns Open Payments (CMS Physician Data) into an in-editor superpower. Ask Cursor to generate code using live data from Open Payments (CMS Physician Data) and it fetches, processes, and writes. all in a single agentic loop. 5 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
Open Payments (CMS Physician Data) in Cursor
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 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 Open Payments (CMS Physician Data) in Cursor
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 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
Open Payments (CMS Physician Data) for Cursor
Every tool call from Cursor 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.
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 →
Pipeliner
10 toolsManage sales pipelines and opportunities via Pipeliner CRM — list leads, track deals, and monitor activities directly from any AI agent.
Oracle Vector DB
7 toolsRun vector similarity searches on Oracle 23ai — execute VECTOR_DISTANCE queries, inspect schemas, list vector indexes, and query tables from any AI agent.
Telegram Bot API
10 toolsConnect your AI natively to Telegram. Read user messages, administrate chats, send push notifications, and automate media distribution directly from the prompt.
OpenFDA Alternative
8 toolsAccess FDA drug safety data, device recalls, food enforcement reports and approved drug information.