Medicare Fee Schedule Rates
REMOTE · S2REASON.COM
Medicare Physician Fee Schedule amounts by code, date and locality, traced to archived CMS files.
Available components
Last scanned (6 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://s2reason.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=s2reason.com | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 71b087cc0d61ef4d0ed65e18d06324fb |
| SANs: s2reason.com, camillatest.s2reason.com, *.camillatest.s2reason.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of s2reason.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| s2reason.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=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://s2reason.com/mcp | Verified | 200 | |
| http (plaintext) | http://s2reason.com/mcp | HTTPS enforced | 301 | https://s2reason.com/mcp |
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 →
medicare_get_physician_fee Medicare physician fee lookup ~497
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| ama_notice | string|null | yes | – |
| coverage | object | yes | – |
| notice | string | yes | – |
| recipe_formula | object | yes | – |
| release_catalog_url | string | yes | – |
| releases | object | yes | – |
| results | array | yes | – |
| schema | string | yes | – |
No examples provided.
medicare_list_fee_releases Medicare fee schedule release list ~191
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | object | yes | – |
| release_catalog_url | string | yes | – |
| releases | array | yes | – |
| schema | string | yes | – |
No examples provided.
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.
remote · s2reason.com
claude mcp add --transport http com-s2reason-medicare-fee-schedule 'https://s2reason.com/mcp'
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 86 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 5 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.