Remote MCP · Endpoint

Med Bill Check MCP server

No. Med Bill Check answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes 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
52 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
34 minutes agoHandshake completed52 ms
9 days agoHandshake completed56 ms
10 days agoHandshake completed130 ms
11 days agoHandshake completed85 ms
12 days agoHandshake completed44 ms
14 days agoHandshake completed51 ms
14 days agoHandshake completed58 ms
15 days agoHandshake completed50 ms
17 days agoHandshake completed82 ms
19 days agoHandshake completed30 ms
21 days agoHandshake completed20 ms
24 days agoHandshake completed44 ms
26 days agoHandshake completed17 ms
28 days agoHandshake completed34 ms

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

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.