HealthCare.gov MCP. Search plans, drugs, and provider networks instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
HealthCare.gov MCP Server automates complex ACA health plan research. Use this server to search for available health and dental plans based on household demographics and location.
You can verify if specific medications are covered by a plan, check a provider's in-network status, and list all insurance companies operating in a state, all from your AI client.
What your AI agents can do
Get api metadata
Retrieves metadata about the Marketplace API data.
Get counties by zip
Converts a given ZIP code into its County FIPS code.
Get drug coverage
Checks if a specific medication is covered by a chosen plan.
Checks if a specific medication is covered by a chosen health plan and reports the tier and copay structure.
Searches for doctors, hospitals, or facilities and confirms if they are currently in-network for a user's plan.
Retrieves a list of available health and dental plans using household demographics and a specific location.
Lists all insurance companies that operate in a given state, showing which ones participate in the Marketplace.
Retrieves historical data showing how health plans transition or change coverage between different enrollment years.
Converts a ZIP code into its corresponding County FIPS code, necessary for accurate regional pricing and plan matching.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
HealthCare.gov MCP Server: 11 Tools for Health Research
Use these 11 tools to search for plans, validate drug coverage, and verify provider networks across the entire HealthCare.gov marketplace dataset.
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 HealthCare.gov on Vinkius019d75aeget api metadata
Retrieves metadata about the Marketplace API data.
019d75aeget counties by zip
Converts a given ZIP code into its County FIPS code.
019d75aeget drug coverage
Checks if a specific medication is covered by a chosen plan.
019d75aeget plan crosswalk
Gets information about how a health plan changes between different enrollment years.
019d75aeget plan details
Gets detailed information about a specific health plan.
019d75aeget provider coverage
Verifies if a given healthcare provider is in-network for a specific plan.
019d75aelist issuers
Lists all insurance companies operating in a specified state.
019d75aelist market states
Lists all states served by the Marketplace.
019d75aesearch drugs
Searches the Marketplace drug database for medication names.
019d75aesearch plans
Searches for available health and dental plans using household demographics and location.
019d75aesearch providers
Searches for healthcare providers, such as doctors or facilities.
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 HealthCare.gov, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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 HealthCare.gov. 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 server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Manually checking insurance coverage is a nightmare of tabs and spreadsheets.
Today, confirming a plan's coverage means hopping between the insurer's website, the government portal, and the drug manufacturer's site. You copy a drug name, paste a ZIP code, and cross-reference plan IDs across three different documents. It's slow, and you're always worried about the data being out of date.
With this MCP server, your agent handles the full flow. You ask, 'Does this plan cover this drug for this provider?' The agent runs `get_drug_coverage`, `get_provider_coverage`, and `get_plan_details` internally, giving you one clear answer, not three sets of confusing screenshots.
HealthCare.gov MCP Server: Get precise plan and provider data.
The biggest time sink is the location dependency. You can't just search by ZIP code; you need the County FIPS code. You can't just search by state; you need to know which issuers operate there. Manually finding and mapping these prerequisite data points is what wastes hours.
Now, your AI client handles the prerequisites. You tell it the ZIP code, and it runs `get_counties_by_zip` first. Then, it uses that precise code to search plans or providers. It eliminates the guesswork and the manual data prep.
What you can do with this MCP connector
The HealthCare.gov MCP Server lets your AI client handle the whole mess of ACA health plan research. You'll use this server to search for available health and dental plans based on your household demographics and where you live. It's built to let your agent check if specific medications are covered by a plan, verify if a provider's in-network, and list every insurance company operating in a state.
Finding Plans and Providers
Your agent uses search_plans to pull up a list of available health and dental plans using your household info and location. It lets you check if a given healthcare provider is in-network for a specific plan with get_provider_coverage, and it searches for doctors, hospitals, or facilities with search_providers. You can also check if a specific medication is covered by a chosen plan, and get_drug_coverage reports the tier and copay structure for that drug.
Deep Dive Research
If you need to map out how a plan changes over time, get_plan_crosswalk pulls historical data showing how health plans transition or change coverage between different enrollment years. For regional accuracy, get_counties_by_zip converts a ZIP code into its corresponding County FIPS code, which you need for accurate regional pricing and plan matching.
You can get detailed info on a specific health plan using get_plan_details, and get_api_metadata retrieves metadata about the Marketplace API data.
State and Drug Scope
list_issuers shows all insurance companies operating in a state, letting you know which ones participate in the Marketplace. You can also see all states served by the Marketplace with list_market_states, and you can search the Marketplace drug database for medication names using search_drugs.
019d75ae-e40b-7216-a0cf-bc124d65216d 
How HealthCare.gov MCP Works
- 1 Subscribe to the HealthCare.gov server and provide your API Key from developer.cms.gov.
- 2 Direct your AI client to perform a complex query (e.g., 'Find plans for a family of four in Texas').
- 3 The client uses the exposed tools to gather data points (e.g., calling
list_issuersfor Texas, thensearch_planswith the demographics) and presents the final, synthesized result.
The bottom line is that your AI client manages the data flow, eliminating the need for manual, multi-step research across multiple government websites.
Who Is HealthCare.gov MCP For?
Benefits consultants, healthcare navigators, and policy researchers need this. They deal with the constant pain of juggling disparate data sources—checking if a drug is covered, if a provider takes the plan, and if the plan is even available in that ZIP code. This tool unifies that entire workflow.
Finds plan options and pricing for clients across different regions, ensuring the chosen coverage matches the client's specific demographics and ZIP code.
Automates the verification of provider networks and drug formularies, allowing them to give clients accurate, real-time coverage answers without manual lookups.
Maintains a real-time overview of marketplace availability, tracking issuer competition and plan changes across various states and years.
What Changes When You Connect
- Verifying drug coverage is simple. Use
get_drug_coverageto check if a medication is covered by a specific plan, detailing the tier and copay. - Stop guessing if a doctor takes the plan.
get_provider_coverageconfirms if a provider is in-network for a specific plan, giving you a definitive answer. - You get instant visibility into plan options.
search_plansretrieves available health and dental plans based on household demographics and location. - Knowing the local market is key.
list_issuersshows all insurance companies operating in a state, helping you understand the local payer landscape. - Understand coverage changes over time.
get_plan_crosswalkmonitors how a plan transitions between enrollment years, keeping you updated on policy shifts. - Accurate pricing starts with location.
get_counties_by_zipconverts a ZIP code into its required County FIPS code, preventing regional pricing errors.
Real-World Use Cases
Client needs coverage verification
A benefits consultant needs to know if a client’s preferred medication is covered. They ask their agent to check 'Drug X' against 'Plan Y'. The agent uses get_drug_coverage to return the tier and copay, solving the immediate client concern.
New patient needs a doctor
A healthcare navigator needs to find an in-network specialist for a client in a new area. They prompt the agent to search for providers, and the agent runs search_providers followed by get_provider_coverage to filter out out-of-network options.
Analyzing market shifts
A policy researcher needs to compare coverage options between 2022 and 2024. They ask the agent to monitor plan transitions, and the agent uses get_plan_crosswalk to provide a precise, year-over-year comparison.
Confirming regional pricing
A consultant receives a client ZIP code. Before searching for plans, they ask the agent to validate the location code. The agent runs get_counties_by_zip to get the County FIPS code, ensuring all subsequent plan searches are geographically accurate.
The Tradeoffs
Searching plans first, then checking drugs
The user searches for plans using search_plans, gets a list of plan IDs, and then manually tries to check drug coverage for each one, forgetting to pass the correct plan ID to get_drug_coverage.
→
Assuming coverage from a plan search
The user asks to find plans for a family, runs search_plans, and assumes all returned plans cover a critical drug, without running get_drug_coverage to confirm the specific drug's tier.
→
Using generic location data
The user just provides a general state name and tries to search for plans, missing the specific county requirements. This fails because the system needs a County FIPS code first.
→
Forgetting state limitations
The user tries to list issuers for a state that isn't served by the Marketplace, leading to an empty result and confusion about system capability.
→
When It Fits, When It Doesn't
Use this server if your core need is verifying specific healthcare policy details: Does Plan X cover Drug Y? Is Provider Z in-network for Plan A? You must use this for any query requiring geographical accuracy (always run get_counties_by_zip first). Don't use this if you only need general public data (like state capitals). If your goal is simply to find a list of available plan IDs, you might only need search_plans. But if you need to validate the details of that plan or its coverage, you must use the specific tools like get_plan_details or get_drug_coverage to confirm the data. This server is for verification, not just listing.
Common Questions About HealthCare.gov MCP
How do I check drug coverage using get_drug_coverage? +
You provide the medication name and the specific plan ID. The tool returns whether the drug is covered, which tier it belongs to, and the associated copay amount.
What is the difference between search_providers and get_provider_coverage? +
search_providers finds potential doctors or facilities by name or location. get_provider_coverage takes a specific provider and a plan ID to confirm if they are actually in-network for that plan.
Can I use get_plan_crosswalk to compare plans? +
Yes, get_plan_crosswalk lets you monitor how a plan's coverage changes year-to-year. This is useful for seeing if benefits shifted between enrollment periods.
Do I need to know the state to use search_plans? +
While you can search for plans, the system often needs to validate the location first. You might need to run list_issuers or get_counties_by_zip to ensure the demographics and location inputs are maximally accurate.
How many tools are available in the HealthCare.gov MCP Server? +
This server has 11 tools. They cover everything from searching for providers to validating complex plan details.
How do I use get_counties_by_zip to get FIPS codes? +
It takes a ZIP code as input. The tool returns the corresponding County FIPS code, which is necessary for accurate plan searching.
What information can I get from get_plan_details? +
This tool pulls comprehensive data on a single plan, including its specific coverage levels, enrollment dates, and eligibility requirements.
Do I need to use list_issuers before running search_plans? +
No, you don't. You can run search_plans directly. However, list_issuers is useful if you first want to see all insurance companies active in a state.
How do I obtain a HealthCare.gov API Key? +
You must request a free API key through the CMS Marketplace API portal (developer.cms.gov/marketplace-api). Keys are typically sent via email and must be renewed every 60 days.
Can I check if my doctor is in-network for a specific plan? +
Yes! Use the get_provider_coverage tool by providing the plan ID and the provider ID. The agent will confirm the network status for that specific combination.
What geographic information is required for plan searches? +
Most searches require a 5-digit ZIP code and a 5-digit County FIPS code. You can use the get_counties_by_zip tool to retrieve the FIPS code for any ZIP code.
Is the integration secure for searching health data? +
Absolutely. The integration uses official CMS API keys over HTTPS. Your credentials are encrypted and stored securely within the Vinkius Cloud infrastructure.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.