MCP Uptime
← MCP Reliability Index  /  AI & LLM
C

CMS Medicare Data

com.olyport/cms-medicare
Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment
healthy
status
5
tools exposed
1634ms
connect latency
145853f7a8d7
schema fingerprint

Tools (5)

get_medicare_spending
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:
get_chronic_conditions
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
get_hospital_quality
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 fil
get_hospital_readmissions
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 abbreviat
get_medicare_enrollment
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

Endpoint

https://mcp.olyport.com/cms-medicare/mcp
Category: AI & LLM · Last checked: 2026-07-30T13:05:39Z

Monitor your own MCP server

Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.

Get early access
How we measure →
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.