Remote MCP · Endpoint

Medicare Fee Schedule Rates MCP server

No. Medicare Fee Schedule Rates answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://s2reason.com/mcp

The last check completed an MCP handshake.

Registry name
com.s2reason/medicare-fee-schedule
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
691 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Medicare Physician Fee Schedule amounts by code, date and locality, traced to archived CMS files.
Listing
From the official MCP registry (active).
Recent checks of Medicare Fee Schedule Rates
CheckedResultHandshake
39 minutes agoHandshake completed691 ms
3 days agoHandshake completed2.31 s
13 days agoHandshake completed139 ms
13 days agoHandshake completed87 ms
15 days agoHandshake completed818 ms
16 days agoHandshake completed705 ms
17 days agoHandshake completed925 ms
18 days agoHandshake completed763 ms
18 days agoHandshake completed791 ms
20 days agoHandshake completed1.46 s
22 days agoHandshake completed997 ms
25 days agoHandshake completed769 ms
27 days agoHandshake completed1.40 s
29 days agoHandshake completed951 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 22 responding of 22.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Medicare Fee Schedule Rates and makes no claim about it beyond what these checks measured.