Remote MCP · Endpoint

Med Bill Check MCP server

No. Med Bill Check answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://goodturn-mcp.pages.dev/medbillcheck/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/medbillcheck
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
44 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Is your US medical bill fair? Compares charges with Medicare rates and drafts a dispute letter.
Listing
From the official MCP registry (active).
Recent checks of Med Bill Check
CheckedResultHandshake
2 hours agoHandshake completed44 ms
2 days agoHandshake completed17 ms
4 days agoHandshake completed34 ms
6 days agoHandshake completed17 ms
8 days agoHandshake completed39 ms
10 days agoHandshake completed20 ms
12 days agoHandshake completed17 ms
13 days agoHandshake completed17 ms
14 days agoHandshake completed16 ms
16 days agoHandshake completed16 ms
18 days agoHandshake completed16 ms
20 days agoHandshake completed19 ms
22 days agoHandshake completed19 ms
23 days agoHandshake completed27 ms

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

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 Med Bill Check and makes no claim about it beyond what these checks measured.