Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CMS Medicare Data

REMOTE · MCP.OLYPORT.COM

Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment

Available components

0 this week 76 Trust /100

Last scanned (15 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 702 tokens (~140/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.olyport.com/cms-medicare/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.olyport.com CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 54d0df51fa6c4f014f3cea8d4e2cde78ed1
SANs: mcp.olyport.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.olyport.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
olyport.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.olyport.com/cms-medicare/mcp Verified 200
http (plaintext) http://mcp.olyport.com/cms-medicare/mcp HTTPS enforced 308 https://mcp.olyport.com/cms-medicare/mcp
MCP tools · 5 exposed · ~702 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_chronic_conditions ~168

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).

NameTypeReqDescription
conditionstring––
limitinteger––
statestring––
yearinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_hospital_quality ~123

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).

NameTypeReqDescription
citystring––
limitinteger––
statestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_hospital_readmissions ~133

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).

NameTypeReqDescription
hospital_namestring––
limitinteger––
statestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_medicare_enrollment ~129

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).

NameTypeReqDescription
limitinteger––
statestring––
yearinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_medicare_spending ~149

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).

NameTypeReqDescription
countystring––
limitinteger––
statestring––
yearinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the CMS Medicare Data MCP server?

CMS Medicare Data is a hosted endpoint at https://mcp.olyport.com/cms-medicare/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.olyport.com

# add to Claude Code
claude mcp add --transport http com-olyport-cms-medicare 'https://mcp.olyport.com/cms-medicare/mcp'
Common questions

What is the CMS Medicare Data MCP server?

CMS Medicare Data is an MCP server listed in the public MCP registry as com.olyport/cms-medicare. Medicare spending, chronic conditions, hospital quality, readmissions, and enrollment. This page covers its hosted endpoint (https://mcp.olyport.com/cms-medicare/mcp).

Is the CMS Medicare Data MCP server safe to use?

CMS Medicare Data scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CMS Medicare Data MCP server expose?

CMS Medicare Data exposes 5 tools: get_medicare_spending, get_chronic_conditions, get_hospital_quality, get_hospital_readmissions, get_medicare_enrollment. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

Does the CMS Medicare Data MCP server require authentication?

No. We connected to CMS Medicare Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CMS Medicare Data MCP server still maintained?

CMS Medicare Data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the CMS Medicare Data MCP server?

VerifyMCP ran 12 checks on CMS Medicare Data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CMS Medicare Data: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.