Bring Financial Transparency
to CrewAI
Learn how to connect HHS Open Payments to CrewAI and start using 6 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 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 CrewAI?
When paired with CrewAI, HHS Open Payments becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HHS Open Payments tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
HHS Open Payments in CrewAI
HHS Open Payments and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect HHS Open Payments to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Open-Meteo Full Access
15 toolsThe ultimate weather Mega-Server: 15 tools covering forecast, historical (84 years), marine, air quality, pollen, climate projections (to 2100), flood, geocoding, and elevation — all in one zero-auth integration.
HighLevel
11 toolsAutomate CRM and marketing via HighLevel — manage contacts, opportunities, and calendars directly from any AI agent.
Odoo Accounting
7 toolsList invoices, bills, payments, journal entries, and chart of accounts — Odoo Accounting through natural conversation.
DocuSeal
12 toolsAutomate document signing workflows via DocuSeal — manage templates, send signature requests, and track signers directly from any AI agent.