# Medicare Fee Schedule Rates (remote · s2reason.com)

Medicare Physician Fee Schedule amounts by code, date and locality, traced to archived CMS files.

- Trust score: 87/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `s2reason.com`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason.md), [page](https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason)

## Channel facts

- Endpoint: `https://s2reason.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 688 tokens (~344/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Medicare Fee Schedule Rates MCP server?

Medicare Fee Schedule Rates is a hosted endpoint at https://s2reason.com/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.

### Claude

```bash
claude mcp add --transport http com-s2reason-medicare-fee-schedule 'https://s2reason.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-s2reason-medicare-fee-schedule": {
      "url": "https://s2reason.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-s2reason-medicare-fee-schedule": {
      "type": "http",
      "url": "https://s2reason.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-s2reason-medicare-fee-schedule]
url = "https://s2reason.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-s2reason-medicare-fee-schedule": {
      "type": "remote",
      "url": "https://s2reason.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-s2reason-medicare-fee-schedule --url 'https://s2reason.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-s2reason-medicare-fee-schedule:
    url: "https://s2reason.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-s2reason-medicare-fee-schedule": {
      "Transport": "http",
      "Url": "https://s2reason.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-s2reason-medicare-fee-schedule -t streamable-http -u 'https://s2reason.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-s2reason-medicare-fee-schedule": {
      "type": "http",
      "url": "https://s2reason.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 87, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `medicare_get_physician_fee` (~497 tokens)

Medicare physician fee lookup

Use this when you need what Medicare's Physician Fee Schedule allows for a CPT or HCPCS code on a given date of service, for the nation or for one state or locality, in the office or facility setting. It takes up to 25 lines (code, modifier, date of service) and returns one answer per line, in order: CMS's allowed amount (national figure, plus the state range or one locality's figure when a state is given), the CMS release in force on that date, its source files with SHA-256 checksums, and the release catalog URL. It covers dates of service from Jan 1, 2023 through Dec 31, 2026; each date is priced under the quarterly CMS release in force that day, and a date outside that span gets a reason instead of a figure. A code with no national rate on this schedule (bundled, carrier-priced, laboratory, drug, anesthesia, ambulance, supplies, or absent from that release) returns a result_kind and a reason, not an error, and a malformed line returns an error for that line only. Do not use it for hospital outpatient or inpatient facility payments, ambulatory surgery center fees, Medicaid, commercial or workers' compensation rates, CPT code descriptions, or opinions on whether a charge is reasonable. It is read-only; amounts are Medicare-allowed amounts per unit, before sequestration and multiple-procedure reductions.

Input parameters:

- `detail` (string): Optional, applies to every line. concise (default) returns the national figure and the state range. detailed lists every locality in the state, with the geographic indexes used, and needs state.
- `lines` (array, required): One to 25 service lines to price. The answers come back in this order.
- `locality` (string): Optional, applies to every line, needs state. CMS locality number inside that state. Leave it out to get the state's range. Example: 01.
- `setting` (string): Optional, applies to every line. Which setting the headline figure reports: office (non-facility) or facility (hospital). Both settings are always in the figures. Leave it out for the setting CMS sho…
- `state` (string): Optional, applies to every line. Two-letter key or full name of a state, DC, Puerto Rico or the Virgin Islands. Leave it out for the national figure only. Example: NJ.

Output parameters:

- `ama_notice` (string|null)
- `coverage` (object)
- `notice` (string)
- `recipe_formula` (object)
- `release_catalog_url` (string)
- `releases` (object)
- `results` (array)
- `schema` (string)

### `medicare_list_fee_releases` (~191 tokens)

Medicare fee schedule release list

Use this when you need to know which CMS Medicare Physician Fee Schedule releases the archive holds, with their effective dates, CMS source files, SHA-256 checksums and any gaps in coverage, before or instead of looking up a fee. It takes no input and returns every release, newest first (id, label, effective and end dates, the CMS document that fixed the dates, source files, the hosted data bundle), plus the coverage summary and the release catalog URL. Coverage runs from Jan 1, 2023 through Dec 31, 2026, and the list changes only when a new CMS release is archived. Do not use it to get a fee amount (use medicare_get_physician_fee), or for other Medicare schedules such as hospital outpatient, ambulatory surgery center, laboratory, ambulance or DMEPOS, or for Medicaid or commercial rates. It is read-only.

Output parameters:

- `coverage` (object)
- `release_catalog_url` (string)
- `releases` (array)
- `schema` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason#diagnostics

## Score history

- 2026-11-06: 87
- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-07: 73

## Common questions

### What is the Medicare Fee Schedule Rates MCP server?

Medicare Fee Schedule Rates is an MCP server listed in the public MCP registry as com.s2reason/medicare-fee-schedule. Medicare Physician Fee Schedule amounts by code, date and locality, traced to archived CMS files. This page covers its hosted endpoint (https://s2reason.com/mcp).

### Is the Medicare Fee Schedule Rates MCP server safe to use?

Medicare Fee Schedule Rates scores 87 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 Medicare Fee Schedule Rates MCP server expose?

Medicare Fee Schedule Rates exposes 2 tools: medicare_get_physician_fee, medicare_list_fee_releases. Their descriptions and schemas cost roughly 688 tokens of context every time the server is loaded.

### Does the Medicare Fee Schedule Rates MCP server require authentication?

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

### Is the Medicare Fee Schedule Rates MCP server still maintained?

Medicare Fee Schedule Rates is still listed as active in the MCP registry. We last reached this channel on 6 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 Medicare Fee Schedule Rates MCP server?

VerifyMCP ran 13 checks on Medicare Fee Schedule Rates, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://s2reason.com/mcp
- Website: https://s2reason.com/medicare-rate-connector
- Changelog RSS feed: https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason.json
- HTML version of this page: https://verifymcp.io/servers/com-s2reason-medicare-fee-schedule/s2reason