CMS Medicare Data MCP server
com.olyport/cms-medicareolyport.comstreamable-httpv1.1.0Scanned
Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment
5 tools: 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CMS Medicare Data MCP server can do
The CMS Medicare Data MCP server is published by olyport.com, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
get_chronic_conditionsGet prevalence of chronic conditions among Medicare beneficiaries.No findings
Why it is in this group
- The name "get_chronic_conditions" says "get": a word for reading.
Description, as the server wrote it 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_qualityGet hospital quality star ratings and general information.No findings
Why it is in this group
- The name "get_hospital_quality" says "get": a word for reading.
Description, as the server wrote it 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_readmissionsGet 30-day hospital readmission rates by hospital.No findings
Why it is in this group
- The name "get_hospital_readmissions" says "get": a word for reading.
Description, as the server wrote it 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_enrollmentGet Medicare enrollment data by state and county.No findings
Why it is in this group
- The name "get_medicare_enrollment" says "get": a word for reading.
Description, as the server wrote it 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_spendingGet Medicare spending per beneficiary by geographic area.No findings
Why it is in this group
- The name "get_medicare_spending" says "get": a word for reading.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cms-medicare https://mcp.olyport.com/cms-medicare/mcpclaude mcp add --transport http cms-medicare https://mcp.olyport.com/cms-medicare/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cms-medicare__get_medicare_spending",
"mcp__cms-medicare__get_chronic_conditions",
"mcp__cms-medicare__get_hospital_quality",
"mcp__cms-medicare__get_hospital_readmissions",
"mcp__cms-medicare__get_medicare_enrollment"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cms-medicare. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.olyport/cms-medicare/verify?hash=f8a61252f9cecbcc80f43745f974ef5828858986fac67bd6b0e16996946bd02a" | jq -e '.changed == false'Pinned hash f8a61252f9ce, from Nov 17, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.olyport/cms-medicare/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.olyport/cms-medicare)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
CMS Medicare Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CMS Medicare Data MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the CMS Medicare Data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CMS Medicare Data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CMS Medicare Data MCP server have?
- 5 tools: 5 read. get_medicare_spending, get_chronic_conditions, get_hospital_quality, get_hospital_readmissions and get_medicare_enrollment.
Does the CMS Medicare Data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CMS Medicare Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CMS Medicare Data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.