CMS Medicare Data MCP server

• get_chronic_conditionsFree

  Get prevalence of chronic conditions among Medicare beneficiaries. Returns state-level data on 21 chronic conditions including diabetes, heart failure, COPD, depression, Alzheimer's, and more. Useful for understanding disease burden by geography. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). condition: Chronic condition name to filter by (e.g. 'diabetes', 'heart failure', 'COPD', 'depression'). year: Year of data (e.g. 2022). limit: Maximum number of records to return (default 50, max 1000).

• get_hospital_qualityFree

  Get hospital quality star ratings and general information. Returns hospital quality data including overall star ratings, location details, and hospital type. Filter by state or city. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). city: City name to filter by (e.g. 'Chicago', 'Houston'). limit: Maximum number of records to return (default 50, max 1000).

• get_hospital_readmissionsFree

  Get 30-day hospital readmission rates by hospital. Returns hospital-level readmission data including excess readmission ratios and predicted/expected readmission rates for conditions like heart attack, heart failure, and pneumonia. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). hospital_name: Hospital name or partial name to search for. limit: Maximum number of records to return (default 50, max 1000).

• get_medicare_enrollmentFree

  Get Medicare enrollment data by state and county. Returns enrollment counts including total beneficiaries, Original Medicare vs Medicare Advantage enrollment, and Part D enrollment. Useful for understanding Medicare population by geography. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). year: Year of enrollment data (e.g. 2022). limit: Maximum number of records to return (default 50, max 1000).

• get_medicare_spendingFree

  Get Medicare spending per beneficiary by geographic area. Returns geographic variation in Medicare spending including per-capita costs and total spending amounts. Filter by state, county, or year. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county: County name to filter by (e.g. 'Los Angeles'). year: Year of spending data (e.g. 2022). limit: Maximum number of records to return (default 50, max 1000).

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 57ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

69/100

higher than 32% of 48,243 servers

Tools

5

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

102 ms

faster than 83% of 30,027 servers

CMS Medicare Data: common questions

Is CMS Medicare Data MCP server safe?

With care: it is graded C, so read the findings first (69/100). Read the CMS Medicare Data safety report

How do I install CMS Medicare Data?

It runs remotely at mcp.olyport.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does CMS Medicare Data need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is CMS Medicare Data maintained?

The latest release is v1.1.0.

Is CMS Medicare Data up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does CMS Medicare Data compare with other MCP servers?

safety score 69/100 (higher than 32% of 48,243 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.